Fix format issues

Author: Michael Burke

machine_configuration/machine-config-pin-preload-images-about.adoc

@@ -8,7 +8,7 @@ toc::[]
 
 Slow and unreliable connections to an image registry can interfere with operations that require pulling images, such as updating a cluster or deploying an application. This can be helpful in cluster with low bandwidth, unreliable internet connectivity, or in a disconnected environment. 
 
-For example, an cluster update might require pulling more than one hundred images. Failure to pull those images causes retries that can interfere with the upgrade process and might cause the update fail. One way to improve that is to _preloand_ the required images by pulling them in advance, before they are actually needed. Then, ensuring that the images are available when needed by _pinning_ them to a machine config pool. Pinning and preloading images can provide a more consistent upgrade, which is important when scheduling upgrades into maintenance windows.
+For example, an cluster update might require pulling more than one hundred images. Failure to pull those images causes retries that can interfere with the upgrade process and might cause the update fail. One way to improve that is to _preload_ the required images by pulling them in advance, before they are actually needed. Then, ensuring that the images are available when needed by _pinning_ them to a machine config pool. Pinning and preloading images can provide a more consistent upgrade, which is important when scheduling upgrades into maintenance windows.
 
 Pinning and preloading images can benefit a cluster that has a low bandwidth or an unreliable connection to an image registry server when deploying applications, ensuring that the images are available and application will successfully deploy in a predictable time.
 
@@ -59,8 +59,11 @@ status:
 ----
 
 
-include::modules/machine-config-pin-preload-images-configuring.adoc[leveloffset=+1]
+include::modules/machine-config-pin-preload-images.adoc[leveloffset=+1]
 
+////
+Add link to machine config nodes when available
 [role="_additional-resources"]
 .Additional resources
 * xref:
+////

modules/machine-config-pin-preload-images.adoc

@@ -27,10 +27,15 @@ spec:
   - name: quay.io/openshifttest/busybox@sha256:0415f56ccc05526
   - name: quay.io/openshifttest/alpine@sha256:be92b18a369e989a
 ----
-<1> Optional: A node selector to specify the machine config pool to pin the images to. If not specified, the images are pinned to all nodes in the cluster.
-<2> A list of one or more images to preload.
++
+where:
++
+--
+`labels`:: Specifies an optional node selector to specify the machine config pool to pin the images to. If not specified, the images are pinned to all nodes in the cluster. the relative path to the downloaded ISO file, for example, `rhcos-live.iso`.
+`pinnedImages`:: Specifies a list of one or more images to preload.
+--
 
-.. Create the `PinnedImageSet` object by running the following command:
+. Create the `PinnedImageSet` object by running the following command:
 +
 [source,terminal]
 ----
@@ -39,7 +44,7 @@ $ oc create -f <file_name>.yaml
 
 .Verification
 
-. Check that the pinned image set is reported in the machine config node object for the affected machine config pool by running the following command:
+* Check that the pinned image set is reported in the machine config node object for the affected machine config pool by running the following command:
 +
 [source,terminal]
 ----
@@ -74,7 +79,7 @@ status
 It can take a few moments for the object to be fully updated.
 ====
 
-. Check that the pinned image file is created and contains the correct images. The contents of the file appear similar to the following example:
+* Check that the pinned image file is created and contains the correct images. The contents of the file appear similar to the following example:
 
 .. Start a debug session for a node by running the following command:
 +
@@ -96,7 +101,7 @@ sh-5.1# chroot /host
 ----
 $ cat /etc/crio/crio.conf.d/<pinned_image_set_name>
 ----
-
++
 .Example command
 [source,terminal]
 ----
@@ -115,8 +120,7 @@ pinned_images=[
 ]
 ----
 
-. Verify that the that pin and pull was successful by checking the `PinnedImageSet` object status:
-+
+* Verify that the that pin and pull was successful by checking the `PinnedImageSet` object status:
 +
 [source,terminal]
 ----