proofread

Author: Michael Burke

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

@@ -35,19 +35,17 @@ Boot image updates are not required for Agent-based Installer clusters. The boot
 
 .Procedure
 
-. Determine if the boot image in your cluster needs to be updated:
-
-.. Check whether your cluster is using the legacy boot image provisioning path by running the following command:
+. Check whether your cluster is using the legacy boot image provisioning path by running the following command:
 +
 [source,terminal]
 ----
 $ oc get provisioning provisioning-configuration \
   -o jsonpath='{.spec.provisioningOSDownloadURL}'
 ----
 +
-* If the output is non-empty, your cluster is running a {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 below to migrate to the current provisioning path.
+* 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 empty, your 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 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 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.
 
 . Clear the legacy image fields and enable the `install_coreos` deployment method:
 
@@ -68,7 +66,7 @@ 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.
 
 .Verification