edits per djoshy

Author: Michael Burke

modules/mco-update-boot-images-ibm-bare-metal.adoc

@@ -7,16 +7,16 @@
 = Manually updating the boot image on a bare-metal cluster
 
 [role="_abstract"]
-For a bare-metal cluster, you can manually update the boot image for your cluster by configuring your machine sets to use the latest {product-title} image as the boot image to help ensure any new nodes can scale up properly.
+For a bare-metal cluster that was installed with {product-title} version 4.9 or earlier, you need to configure how the cluster provisions new nodes in order to update the boot images used with those nodes. Using an up-to-date boot image ensures that any new nodes can scale up properly.
 
 [NOTE]
 ====
 The standard boot image management feature is not supported for bare-metal clusters.
 ====
 
-If your bare-metal cluster is running a {product-title} version 4.10 or later, boot images are kept current by the Cluster Version Operator (CVO) and are not at risk of skew. Skew enforcement is disabled for this cluster by default. You do not need to manually update the boot image. No further action on your part is required to maintain the boot image versioning.
+If your bare-metal cluster was installed with {product-title} version 4.10 or later, boot images are kept current by the Cluster Version Operator (CVO) and are not at risk of skew. Skew enforcement is disabled for the cluster by default. No further action on your part is required to maintain the boot image versioning.
 
-If your bare-metal cluster is running a {product-title} version 4.9 or earlier, the cluster is still using the legacy qcow2-based provisioning path. Boot images in clusters on this path are not managed by the CVO and could be significantly out of date. Follow the steps below to migrate the cluster to the `machine-os-images` provisioning path, which was introduced in {product-title} 4.10. This migration also updates the boot image to the latest {op-system-first} version.
+If your bare-metal cluster was installed with {product-title} version 4.9 or earlier, the cluster is using the legacy qcow2-based provisioning method. Boot images in these clusters are not managed by the CVO and could be significantly out of date. Follow the steps below to migrate the cluster to use the `machine-os-images` provisioning method, which was introduced in {product-title} 4.10. This migration ensures that the cluster always uses the release version as the boot image when a scale-up is taking place.
 
 The following procedure enables the `install_coreos` deployment method and disables the qcow2 image cache. With these changes, the Cluster Baremetal Operator (CBO) will use the `machine-os-images` container from the release payload for new node provisioning. The cluster will have no skew risk, the same as a cluster at version 4.10 or later. Skew enforcement is automatically disabled after the migration is complete.
 
@@ -43,9 +43,9 @@ $ oc get provisioning provisioning-configuration \
   -o jsonpath='{.spec.provisioningOSDownloadURL}'
 ----
 +
-* If the output is non-empty, your cluster is running an {product-title} version 4.9 or earlier. Boot images are not managed by the the Cluster Version Operator (CVO) and could be significantly out of date. Follow the steps in this procedure to migrate to the current provisioning path.
+* If the output is non-empty, your cluster was installed with {product-title} version 4.9 or earlier. Boot images are not managed by the the Cluster Version Operator (CVO) and could be significantly out of date. Follow the steps in this procedure to migrate to the current provisioning path.
 +
-* If the output is empty, your cluster is running an {product-title} version 4.10 or later. Boot images are kept current by the Cluster Version Operator (CVO) and are not at risk of skew. Skew enforcement should be disabled for this cluster. No further action on your part is required to maintain the boot image versioning.
+* If the output is empty, your cluster was installed with {product-title} version 4.10 or later. Boot images are kept current by the Cluster Version Operator (CVO) and are not at risk of skew. Skew enforcement should be disabled for this cluster. No further action on your part is required to maintain the boot image versioning.
 
 . Clear the legacy image fields and enable the `install_coreos` deployment method:
 
@@ -66,7 +66,9 @@ Replace `<machineset_name>` with the name of your machine set.
 $ oc patch provisioning provisioning-configuration --type=merge -p '{"spec":{"provisioningOSDownloadURL":""}}'
 ----
 +
-This process updates the boot image to match the current cluster version.
+This process migrates the cluster to the `machine-os-images` provisioning method, which ensure that the latest boot image is used for scaling nodes.
+
+
 
 .Verification