edit

Author: Michael Burke

modules/mco-update-boot-images-plat-none.adoc

@@ -7,7 +7,9 @@
 = Manually updating the boot image on a platform none or external cluster
 
 [role="_abstract"]
-For `platform: None` and `platform: External` clusters, {product-title} does not manage node provisioning or {op-system-first} boot images. These clusters do not use Machine API machine sets. 
+For `platform: None` and `platform: External` clusters, 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 these clusters, {product-title} does not manage node provisioning or {op-system-first} boot images. These clusters do not use Machine API machine sets. 
 
 [NOTE]
 ====
@@ -30,7 +32,7 @@ For user-provisioned infrastructure clusters, you manage boot images as part of
 For the full procedure, see "Adding compute machines to bare metal".
 
 {rh-rhacm}-managed clusters::
-For clusters managed by {rh-rhacm}, the boot image used to generate the discovery ISO image is controlled by the `Spec.OSImageVersion` parameter in the `InfraEnv` object on the hub cluster. After an {product-title} upgrade, you need to update the existing `InfraEnv` to add or update `spec.osImageVersion` field, specifying the {product-title} version of the new boot image.  
+For clusters managed by {rh-rhacm}, the boot image used to generate the discovery ISO image is controlled by the `Spec.OSImageVersion` parameter in the `InfraEnv` object on the hub cluster. After an {product-title} upgrade, you need to update the existing `InfraEnv` object to add or update `spec.osImageVersion` field, specifying the {product-title} version of the new boot image.  
 
 
 External provider clusters::