Edits per djoshy

Author: Michael Burke

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

@@ -9,7 +9,7 @@
 [role="_abstract"]
 You can manually update the boot image for your {gcp-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.
 
-The following procedure, which includes steps to create environment variables that facilitate running the required commands, shows how to identify the correct boot image to use as the new boot image and how to modify your compute machine sets to use that image.
+The following procedure, which includes steps to create environment variables that facilitate running the required commands, shows how to identify the correct boot image to use as the new boot image and how to modify your machine sets to use that image.
 
 ifndef::openshift-dedicated[]
 The process differs for clusters that use a default {op-system-first} image, clusters that use a custom {op-system-first} image from the {gcp-short} Marketplace, and user-provisioned infrastructure clusters. The following procedure helps determine which type of cluster you have.
@@ -89,7 +89,7 @@ $ export BOOT_DISK_INDEX=0
 ----
 
 ifndef::openshift-dedicated[]
-. Determine if your cluster uses a default {op-system} image or a custom {op-system} image from the {gcp-short} Marketplace, or is a user-provisioned infrastructure cluster:
+. Determine if your cluster uses a default {op-system} image or a GCP Marketplace {op-system} image from the {gcp-short} Marketplace, or is a user-provisioned infrastructure cluster:
 
 .. Obtain the name of the current boot image and set the name as an environment variable by running the following command:
 +
@@ -120,13 +120,13 @@ projects/rhcos-cloud/global/images/rhcos-9-6-20251023-0-gcp-x86-64
 |===
 | Current image prefix | Variant
 | `projects/rhcos-cloud/global/images/` | Default
-| `projects/redhat-marketplace-public/global/images/` | Custom {op-system} image
+| `projects/redhat-marketplace-public/global/images/` | GCP Marketplace {op-system} image
 | No machine set present/custom prefix | User-provisioned infrastructure
 |===
 +
 Default {op-system} clusters use images from the `rhcos-cloud` project in the `rhcos-<version>-<platform>-<arch>` format.
 +
-Custom {op-system} clusters use images from the `redhat-marketplace-public` project in the `redhat-coreos-<offering>-<version>-<arch>-<date>` format.
+GCP Marketplace {op-system} clusters use images from the `redhat-marketplace-public` project in the `redhat-coreos-<offering>-<version>-<arch>-<date>` format.
 +
 [NOTE]
 ====
@@ -136,7 +136,7 @@ The following images are the latest {gcp-short} Marketplace images for the {prod
 {opp}:: `redhat-coreos-opp-413-x86-64-202305021736`
 {oke}:: `redhat-coreos-oke-413-x86-64-202305021736`
 
-{gcp-short} does not publish Marketplace images for {product-title} later than these {product-title} 4.13 images. If the current boot image in your cluster matches one of the listed images, no further action is necessary.
+Red Hat has not published Marketplace images for {product-title} later than these {product-title} 4.13 images. If the current boot image in your cluster matches one of the listed images, no further action is necessary.
 ====
 endif::openshift-dedicated[]
 ifndef::openshift-dedicated[]
@@ -206,7 +206,7 @@ $ openshift-install coreos print-stream-json | jq -r ".architectures.\"${ARCH}\"
 +
 Make note of the {op-system} version for later use.
 
-* For a cluster that uses a custom {op-system} image that is earlier than the 4.13 images listed above, perform the following steps:
+* For a cluster that uses a GCP Marketplace {op-system} image that is earlier than the 4.13 images listed above, perform the following steps:
 
 .. Set an environment variable with the name of the new boot image by running the following command:
 +