proofread

Author: Michael Burke

modules/mco-update-boot-images-vsphere.adoc

@@ -9,11 +9,11 @@
 [role="_abstract"]
 You can manually update the boot image for your {vmw-first} cluster by configuring your machine sets to use the latest {product-title} image as the boot image to ensure that new nodes can scale up properly.
 
-vSphere boot images use a template you create by uploading the OVA image to the VMware vCenter. The template image is used by all machine sets as the boot image. The following procedure shows how to identify the correct boot image to use as the new boot image, how to create the template from the image in vCenter, and how to modify your compute machine sets to use that template image.
+vSphere boot images use a template that you create by uploading a {op-system-first} OVA image to the VMware vCenter. The template image is used by all machine sets as the boot image. The following procedure shows how to identify the correct boot image to use as the new boot image, how to create the template from the image in vCenter, and how to modify your compute machine sets to use that template image.
 
 [NOTE]
 ====
-For clusters that use a default {op-system-first} image, you can configure the cluster to automatically update the boot image each time the cluster is updated. If you are using the following procedure, ensure that automatic boot image updates are disabled and skew enforcement is in manual mode. For more information, see "Boot image management" and "Boot image skew enforcement".
+For clusters that use a default {op-system} image, you can configure the cluster to automatically update the boot image each time the cluster is updated. If you are using the following procedure, ensure that automatic boot image updates are disabled and skew enforcement is in manual mode. For more information, see "Boot image management" and "Boot image skew enforcement".
 ====
 
 .Prerequisites
@@ -28,6 +28,8 @@ For clusters that use a default {op-system-first} image, you can configure the c
 
 * You have downloaded the latest version of the {product-title} installation program, openshift-install, from the {cluster-manager-url}. For more information, see "Obtaining the installation program."
 
+// The vSphere steps are copied from installation-vsphere-machines.adoc and tweaked based on the KB; last two steps from KB
+
 .Procedure
 
 . Obtain the latest boot image to use as the new boot image:
@@ -57,7 +59,6 @@ $ openshift-install coreos print-stream-json | jq '.architectures.x86_64.artifac
 
 .. Use the URL in the `location` field to download the image.
 
-//Copied from installation-vsphere-machines.adoc; last two steps from KB
 . In the vSphere Client, create a template for the OVA image:
 .. From the *Hosts and Clusters* tab, right-click your cluster name and select *Deploy OVF Template*.
 .. On the *Select an OVF* tab, specify the name of the {op-system} OVA file that you downloaded.
@@ -71,7 +72,7 @@ $ openshift-install coreos print-stream-json | jq '.architectures.x86_64.artifac
 .. When creating the OVF template, do not specify values on the *Customize template* tab or configure the template any further.
 .. On the *Ready to complete* tab, verify your settings and click *Finish*.
 +
-The vSphere Client uploads the boot image and creates the OVF template. This can take a few minutes depending on network speeds. You can keep track of this process in the task tab under _Deploy OVF template_.
+The vSphere Client uploads the boot image to create the OVF template. This can take a few minutes depending on network speeds. You can keep track of this process in the task tab under _Deploy OVF template_.
 .. After the upload is complete, click the new virtual machine and click *Template* -> *Convert to template* -> *Yes*.
 +
 You now have a VM template based on the new boot image, which you can use to update the machineset objects.