proofread

Author: Michael Burke

machine_configuration/mco-update-boot-images.adoc

@@ -31,15 +31,3 @@ include::modules/mco-update-boot-images-openstack.adoc[leveloffset=+2]
 * xref:../installing/installing_aws/ipi/ipi-aws-preparing-to-install.adoc#installation-obtaining-installer_ipi-aws-preparing-to-install[Obtaining the installation program]
 
 include::modules/mco-update-boot-images-disable.adoc[leveloffset=+1]
-
-include::modules/mco-update-boot-skew-mgmt-about.adoc[leveloffset=+1]
-
-include::modules/mco-update-boot-skew-mgmt-configuring.adoc[leveloffset=+2]
-
-[role="_additional-resources"]
-[id="additional-resources_{context}"]
-== Additional resources
-
-* [Manually updating the boot image forthcoming after https://github.com/openshift/openshift-docs/pull/108014 merges]
-
-* xref:../machine_configuration/mco-update-boot-skew-mgmt.adoc#mco-update-boot-skew-mgmt[Boot image skew enforcement]

modules/mco-update-boot-skew-mgmt-about.adoc

@@ -3,13 +3,13 @@
 // * machine-configuration/mco-update-boot-skew-mgmt.adoc
 
 :_mod-docs-content-type: CONCEPT
-[id="mco-update-boot-skew-mgmt-about.adoc_{context}"]
+[id="mco-update-boot-skew-mgmt-about_{context}"]
 = About boot image skew enforcement
 
 [role="_abstract"]
-Using boot image skew enforcement you can ensure that the boot images in a cluster are up-to-date with the {product-title} and {op-system} version being used in the cluster. Making sure that your boot images are current can help you avoid the problems associated with running older images.
+Using boot image skew enforcement, you can ensure that the boot images in a cluster are up-to-date with the {product-title} and {op-system} version being used in the cluster. Making sure that your boot images are current can help you avoid the problems associated with running older images.
 
-When boot image skew enforcement is active in a cluster, the Machine Config Operator (MCO) examines the boot image version reported in the `MachineConfiguration` object to determine if that boot image is appropriate for the cluster. If the boot image version is too old, the Operator reports that _boot image version skew_ is detected and blocks cluster updates until you manually update the boot image or set boot image skew enforcement to the `None` mode, as described in this section. 
+When boot image skew enforcement is active in a cluster, the Machine Config Operator (MCO) examines the boot image version reported in the `MachineConfiguration` object to determine if that boot image is appropriate for the cluster. If the boot image version is too old, the Operator reports that _boot image version skew_ is detected and blocks cluster updates until you manually update the boot image or disable boot image skew enforcement by setting the `None` mode, as described in this section. 
 
 The limit for boot image version skew is set within the MCO and cannot be modified.
 
@@ -21,7 +21,7 @@ include::snippets/technology-preview.adoc[]
 Boot image skew enforcement operates in one of the following modes:
 
 Automatic:: 
-In automatic mode, when the cluster is updated from one {product-title} version to the next, with boot image management also enabled, the MCO automatically updates the boot image version in the `MachineConfiguration` object and tests the boot image version for skew. Boot image management must be enabled in the node to use the automatic mode. 
+When set to `Automatic`, if the cluster is updated from one {product-title} version to the next, with boot image management also enabled, the MCO automatically updates the boot image version in the `MachineConfiguration` object and tests the boot image version for skew. 
 +
 [NOTE]
 ====
@@ -52,9 +52,8 @@ status:
 +
 The MCO examines the boot image reported in the `ocpVersion` parameter to determine if the cluster is violating the boot image version skew limits.
 
-Manual:: In manual mode, when the boot image version is updated, a cluster administrator is responsible to manually update the `MachneConfiguration` object with the {op-system} version of the boot image or the {product-title} associated with the boot image. The MCO then tests the boot image version for skew.
-+
-For information on boot image management, see "Boot image management".
+Manual:: 
+When set to `Manual`, if the boot image version is updated, a cluster administrator is responsible to manually update the `MachneConfiguration` object with the {op-system} version of the new boot image or the {product-title} version associated with the new boot image. The MCO then tests the boot image version for skew.
 +
 .Example `MachineConfiguration` object with skew enforcement based on an {op-system} version
 [source,yaml]
@@ -102,10 +101,10 @@ status:
     mode: Manual
 ----
 +
-The MCO examines the boot image reported in the `rhcosVersion` or `ocpVersion` parameters to determine if the cluster is violating the boot image version skew limits.
+The MCO examines the boot image reported in the `rhcosVersion` or `ocpVersion` parameter to determine if the cluster is violating the boot image version skew limits.
 
 None:: 
-In None mode, boot image management is disabled. When disabled, the MCO does not monitor for boot image skew and does not report if new nodes are provisioned with older boot images that could introduce compatibility issues. This can affect the cluster's ability to scale. 
+When set to `None`, boot image skew enforcement is disabled. When disabled, the MCO does not monitor for boot image skew and does not report if new nodes are provisioned with older boot images that could introduce compatibility issues. 
 +
 .Example `MachineConfiguration` object with skew enforcement disabled
 [source,yaml]

modules/mco-update-boot-skew-mgmt-configuring.adoc

@@ -3,15 +3,15 @@
 // * machine-configuration/mco-update-boot-skew-mgmt.adoc
 
 :_mod-docs-content-type: PROCEDURE
-[id="mco-update-boot-skew-mgmt-configuring.adoc_{context}"]
+[id="mco-update-boot-skew-mgmt-configuring_{context}"]
 = Configuring boot image skew enforcement
 
 [role="_abstract"]
-You can configure the current boot image skew enforcement mode that the Machine Config Operator (MCO) uses. By configuring the boot image skew enforcement level, you specify the current boot image version used in the cluster, which the MCO uses to determine boot image skew compliance in your cluster.
+You can configure the current boot image skew enforcement mode that the Machine Config Operator (MCO) uses. By configuring the boot image skew enforcement mode, you can determine if the boot image boot image version in the `MachineConfiguration` object is updated automatically or manaully. 
 
-Alternatively, you can disable boot image skew enforcement by setting the `mode` to `None`. When disabled, the MCO does not monitor for boot image skew and older boot images could be used, possibly introducing compatibility issues on new nodes.
+Alternatively, you can disable boot image skew enforcement by setting the `mode` to `None`. When disabled, the MCO does not monitor for boot image skew, and older boot images could be used, possibly introducing compatibility issues on new nodes.
 
-In {product-title} 4.22, the automatic mode is available only for {aws-short}, {gcp-short}, {azure-short}, and {vmw-short} clusters and is the default for these platforms. All other platforms default to manual mode. If you modify a cluster from automatic mode to manual or none, you can revert a cluster to automatic mode only by removing the `bootImageSkewEnforcement` stanza from the `MachineConfiguration` object.
+In {product-title} 4.22, the automatic mode is available only for {aws-short}, {gcp-short}, {azure-short}, and {vmw-short} clusters and is the default for these platforms. All other platforms default to manual mode. If you modify a cluster from automatic to manual or none, you can revert a cluster to automatic mode only by removing the `bootImageSkewEnforcement` stanza from the `MachineConfiguration` object.
 
 .Prerequisites
 
@@ -53,22 +53,21 @@ spec:
     mode: Manual
     manual:
       mode: RHCOSVersion
-      rhcosVersion: 9.0.20251023-0
+      rhcosVersion: 9.6.20251023-0
 # ...
 ----
 where:
 
-`spec.bootImageSkewEnforcement.mode`:: Specifies the boot image management mode, one of the following values:
+`spec.bootImageSkewEnforcement.mode`:: Specifies the boot image enforcement mode, one of the following values:
 +
 --
-* `Manual`. The cluster admin is responsible to manually configure the boot image version based on the `ocpVersion` or `rhcosVersion` parameter. You must specify the `spec.bootImageSkewEnforcement.manual` parameters.
-* `None`. Boot image management is disabled. You do not need to specify the `spec.bootImageSkewEnforcement.manual` parameters.
+* `Manual`. Specifies that boot image skew management is in manual mode.  You must specify the `spec.bootImageSkewEnforcement.manual` parameters.
+* `None`. Specifies that boot image skew management is disabled. You do not need to specify the `spec.bootImageSkewEnforcement.manual` parameters.
 --
-+
-`spec.bootImageSkewEnforcement.manual`:: For the `Manual` mode, specifies that the minimum boot image is based on the specific {product-title} or {op-system} version. This example configures an {op-system} version. You must include the following parameters:
+
+`spec.bootImageSkewEnforcement.manual.mode`:: Specifies the version you want to represent the current boot image, either `OCPVersion` or `RHCOSVersion`. You must include the following parameters:
 +
 --
-* `spec.bootImageSkewEnforcement.manual.mode`. Specifies the version you want to represent the current boot image, either `OCPVersion` or `RHCOSVersion`. You must include one of the following parameters:
 ** For `RHCOSVersion`, use `spec.bootImageSkewEnforcement.manual.rhcosVersion` to specify the {op-system} version that is being used as a boot image in the `[major].[minor].[datestamp(YYYYMMDD)]-[buildnumber]` or `[major].[minor].[timestamp(YYYYMMDDHHmm)]-[buildnumber]` format. This field must be between 14 and 21 characters long.
-** For `OCPVersion`, use `spec.bootImageSkewEnforcement.manual.ocpVersion` to  specify the {product-title} version associated with the boot image that is being used in the `x.y.z` format. This field must be between 5 and 10 characters long.
+** For `OCPVersion`, use `spec.bootImageSkewEnforcement.manual.ocpVersion` to specify the {product-title} version associated with the boot image that is being used in the `x.y.z` format. This field must be between 5 and 10 characters long.
 --

modules/mco-update-boot-skew-mgmt-updating.adoc

@@ -8,7 +8,7 @@
 = Updating the boot image skew enforcement version
 
 [role="_abstract"]
-If you a running boot image skew enforcement in the manual mode, you must manually update the boot image version in the `MachineConfiguration` object each time you update the boot image. With the boot image updated in the `MachineConfiguration` object, the Machine Config Operator (MCO) can properly perform boot image skew enforcement to keep your node up-to-date. 
+If you running boot image skew enforcement in the manual mode, you must manually update the boot image version in the `MachineConfiguration` object each time you update the boot image in your cluster. With the boot image updated in the `MachineConfiguration` object, the Machine Config Operator (MCO) can properly perform boot image skew enforcement to ensure that your nodes are up-to-date. 
 
 .Prerequisites
 
@@ -76,7 +76,7 @@ spec:
     mode: Manual
     manual:
       mode: OCPVersion
-      ocpVersion: 4.22.1
+      ocpVersion: 4.22.0
 # ...
 status:
   bootImageSkewEnforcementStatus: