edits for DITA improvement, callouts

Author: abrennan89

modules/nw-sr-iov-network-node-configuration-examples.adoc

@@ -8,7 +8,6 @@
 
 The following example describes the configuration for an InfiniBand device:
 
-.Example configuration for an InfiniBand device
 [source,yaml]
 ----
 apiVersion: sriovnetwork.openshift.io/v1
@@ -33,7 +32,6 @@ spec:
 
 The following example describes the configuration for an SR-IOV network device in a {rh-openstack} virtual machine:
 
-.Example configuration for an SR-IOV device in a virtual machine
 [source,yaml]
 ----
 apiVersion: sriovnetwork.openshift.io/v1
@@ -45,13 +43,12 @@ spec:
   resourceName: <sriov_resource_name>
   nodeSelector:
     feature.node.kubernetes.io/network-sriov.capable: "true"
-  numVfs: 1 <1>
+  numVfs: 1
   nicSelector:
     vendor: "<vendor_code>"
     deviceID: "<device_id>"
-    netFilter: "openstack/NetworkID:ea24bd04-8674-4f69-b0ee-fa0b3bd20509" <2>
+    netFilter: "openstack/NetworkID:ea24bd04-8674-4f69-b0ee-fa0b3bd20509"
 # ...
 ----
-<1> When configuring the node network policy for a virtual machine, the `numVfs` parameter is always set to `1`.
-<2> When the virtual machine is deployed on {rh-openstack}, the `netFilter` parameter must refer to a network ID. Valid values for `netFilter` are available from an `SriovNetworkNodeState` object.
-
+* When configuring the node network policy for a virtual machine, the `numVfs` parameter is always set to `1`.
+* When the virtual machine is deployed on {rh-openstack}, the `netFilter` parameter must refer to a network ID. Valid values for `netFilter` are available from an `SriovNetworkNodeState` object.

modules/nw-sriov-device-discovery.adoc

@@ -4,11 +4,11 @@
 // * virt/vm_networking/virt-connecting-vm-to-sriov.adoc
 
 :_mod-docs-content-type: REFERENCE
-[id="discover-sr-iov-devices_{context}"]
+[id="nw-sriov-device-discovery_{context}"]
 = Automated discovery of SR-IOV network devices
 
 The SR-IOV Network Operator searches your cluster for SR-IOV capable network devices on worker nodes.
-The Operator creates and updates a SriovNetworkNodeState custom resource (CR) for each worker node that provides a compatible SR-IOV network device.
+The Operator creates and updates a `SriovNetworkNodeState` custom resource (CR) for each worker node that provides a compatible SR-IOV network device.
 
 The CR is assigned the same name as the worker node.
 The `status.interfaces` list provides information about the network devices on a node.
@@ -19,18 +19,14 @@ Do not modify a `SriovNetworkNodeState` object.
 The Operator creates and manages these resources automatically.
 ====
 
-[id="example-sriovnetworknodestate_{context}"]
-== Example SriovNetworkNodeState object
-
 The following YAML is an example of a `SriovNetworkNodeState` object created by the SR-IOV Network Operator:
 
-.An SriovNetworkNodeState object
 [source,yaml]
 ----
 apiVersion: sriovnetwork.openshift.io/v1
 kind: SriovNetworkNodeState
 metadata:
-  name: node-25 <1>
+  name: node-25
   namespace: openshift-sriov-network-operator
   ownerReferences:
   - apiVersion: sriovnetwork.openshift.io/v1
@@ -41,7 +37,7 @@ metadata:
 spec:
   dpConfigVersion: "39824"
 status:
-  interfaces: <2>
+  interfaces:
   - deviceID: "1017"
     driver: mlx5_core
     mtu: 1500
@@ -79,5 +75,5 @@ status:
     vendor: "8086"
   syncStatus: Succeeded
 ----
-<1> The value of the `name` field is the same as the name of the worker node.
-<2> The `interfaces` stanza includes a list of all of the SR-IOV devices discovered by the Operator on the worker node.
+* The value of the `name` field is the same as the name of the worker node.
+* The `interfaces` stanza includes a list of all of the SR-IOV devices discovered by the Operator on the worker node.

modules/nw-sriov-networknodepolicy-object.adoc

@@ -6,7 +6,8 @@
 [id="nw-sriov-networknodepolicy-object_{context}"]
 = SR-IOV network node configuration object
 
-You specify the SR-IOV network device configuration for a node by creating an SR-IOV network node policy. The API object for the policy is part of the `sriovnetwork.openshift.io` API group.
+[role="_abstract"]
+You can specify the SR-IOV network device configuration for a node by creating an SR-IOV network node policy. The API object for the policy is part of the `sriovnetwork.openshift.io` API group.
 
 The following YAML describes an SR-IOV network node policy: