edits per lahinson

Author: Michael Burke

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

@@ -1,18 +1,18 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="machine-config-pin-preload-images-about"]
-= About pinning and preloading images
+= About pre-loading and pinning images
 include::_attributes/common-attributes.adoc[]
 :context: machine-config-operator
 
 toc::[]
 
-Slow, unreliable connection to an image registry can interfere with operations that require pulling images, such as updating a cluster or deploying an application. This can include clusters that have low bandwidth, clusters with unreliable internet connectivity, or clusters in a disconnected environment. 
+A slow, unreliable connection to an image registry can interfere with operations that require pulling images, such as updating a cluster or deploying an application. This can include clusters that have low bandwidth, clusters with unreliable internet connectivity, or clusters in a disconnected environment. 
 
-For example, a cluster update might require pulling more than one hundred images. Failure to pull those images could cause retries that can interfere with the update process and might cause the update to fail. One way to prevent this is to _preload_ the required images by pulling them in advance, before they are actually needed. Then, by _pinning_ them to a machine config pool, you ensure that the images are available when needed. Pinning and preloading images can provide a more consistent update, which is important when scheduling updates into maintenance windows.
+For example, a cluster update might require pulling more than one hundred images. Failure to pull those images could cause retries that can interfere with the update process and might cause the update to fail. One way to prevent this is to _pre-load_ the required images by pulling them in advance, before they are actually needed. Then, by _pinning_ them to a machine config pool, you ensure that the images are available when needed. Pre-loading and pinning images can provide a more consistent update, which is important when scheduling updates into maintenance windows.
 
-Pinning and preloading images also ensures that the images are available when deploying applications, which allows you to deploy in a predictable time. Another benefit to pinning and preloading images is that image garbage collection does not remove the pinned images.
+Pre-loading and pinning images also ensures that the images are available when deploying applications, so that you can deploy in a predictable time. Another benefit to pre-loading and pinning images is that image garbage collection does not remove the pinned images.
 
-You can pin and preload images by using a a `PinnedImageSet` custom resource (CR) as described in the following section. Pinned images are stored on the nodes in the `/etc/crio/crio.conf.d/50-pinned-images` file. The contents of the file appear similar to the following example:
+You can pre-load and pin images by using a a `PinnedImageSet` custom resource (CR), as described in _Pre-loading and pinning images_. Pinned images are stored on the nodes in the `/etc/crio/crio.conf.d/50-pinned-images` file. The contents of the file appear similar to the following example:
 
 [source,terminal]
 ----

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

@@ -4,9 +4,9 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="machine-config-pin-preload-images_{context}"]
-= Pinning and preloading images
+= Pre-loading and pinning images
 
-You can pin and preload images by using a `PinnedImageSet` custom resource (CR). The pinned image set defines the list of images to preload and the machine config pool to which the images should be pinned. 
+You can pre-load and pin images by using a `PinnedImageSet` custom resource (CR). The pinned image set defines the list of images to pre-load and the machine config pool to which the images should be pinned. 
 
 The images are stored in the the `/etc/crio/crio.conf.d/50-pinned-images` file on the nodes. 
 
@@ -32,7 +32,7 @@ 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.
-`pinnedImages`:: Specifies a list of one or more images to preload.
+`pinnedImages`:: Specifies a list of one or more images to pre-load.
 --
 
 . Create the `PinnedImageSet` object by running the following command:
@@ -138,4 +138,7 @@ $ cat /etc/crio/crio.conf.d/50-pinned-images
   [crio.image]
     pinned_images = ["quay.io/openshift-release-dev/ocp-release@sha256:4198606580b69c8335ad7ae531c3a74e51aee25db5faaf368234e8c8dae5cbea", "quay.io/openshift-release-dev/ocp-release@sha256:513cf1028aa1a021fa73d0601427a0fbcf6d212b88aaf9d76d4e4841a061e44e", "quay.io/openshift-release-dev/ocp-release@sha256:61eae2d261e54d1b8a0e05f6b5326228b00468364563745eed88460af04f909b"] <1>
 ----
-<1> Specifies the images that have been pulled and pinned for the affected machine config pool.
++
+where:
++
+`pinnedImages`:: Specifies the images that have been pulled and pinned for the affected machine config pool.