OSDOCS-17511:Resolved Vale errors in the OSD Upgrading book.

modules/osd-lifecycle-policy.adoc

@@ -7,6 +7,7 @@
 [id="osd-lifecycle-policy_{context}"]
 = Life cycle policies and planning
 
+[role="_abstract"]
 To plan an upgrade, review the _{product-title} update life cycle_ guide in the "Additional resources" section. The life cycle page includes release definitions, support and upgrade requirements, installation policy information, and life cycle dates.
 
 You can use update channels to decide which Red Hat OpenShift Container Platform minor version to update your clusters to. {product-title} supports updates only through the `stable` channel. To learn more about OpenShift update channels and releases, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/updating_clusters/understanding-openshift-updates-1#understanding-update-channels-releases[Understanding update channels and releases].

modules/upgrade-auto.adoc

@@ -8,7 +8,7 @@
 
 = Scheduling recurring upgrades for your cluster
 
-
+[role="_abstract"]
 You can use {cluster-manager} to schedule recurring, automatic upgrades for z-stream patch versions for your {product-title} cluster. Based on upstream changes, there might be times when no updates are released. Therefore, no upgrade occurs for that week.
 
 .Procedure
@@ -36,4 +36,5 @@ Before upgrading a Workload Identity Federation (WIF)-enabled {product-title} on
 
 . To cancel a recurring upgrade policy, switch the upgrade method to individual from the *Upgrade Settings* tab. Click *Save*.
 
-On the *Upgrade settings* tab, the *Upgrade status* box indicates that an upgrade is scheduled. The date and time of the next scheduled update is listed.
+.Verification
+* On the *Upgrade settings* tab, the *Upgrade status* box indicates that an upgrade is scheduled. The date and time of the next scheduled update is listed.

modules/upgrade-manual.adoc

@@ -8,10 +8,9 @@
 
 = Scheduling individual upgrades for your cluster
 
-
+[role="_abstract"]
 You can use {cluster-manager} to manually upgrade your {product-title} cluster one time.
 
-
 .Procedure
 
 . From {cluster-manager-url}, select your cluster from the clusters list.
@@ -46,9 +45,11 @@ Before upgrading a Workload Identity Federation (WIF)-enabled {product-title} on
 
 . Optional: Set a grace period for *Node draining* by selecting a designated amount of time from the drop down list. A *1 hour* grace period is set by default.
 
-From the *Overview* tab, next to the cluster version, the UI notates that the upgrade has been scheduled. Click *View details* to view the upgrade details. If you need to cancel the scheduled upgrade, you can click *Cancel this upgrade* from the *View Details* pop-up.
+.Verification
 
-The same upgrade details are available on the *Upgrade settings* tab under the *Upgrade status* box. If you need to cancel the scheduled upgrade, you can click *Cancel this upgrade* from the *Upgrade status* box.
+* From the *Overview* tab, next to the cluster version, the UI notates that the upgrade has been scheduled.
+** Click *View details* to view the upgrade details. If you need to cancel the scheduled upgrade, you can click *Cancel this upgrade* from the *View Details* pop-up.
+** The same upgrade details are available on the *Upgrade settings* tab under the *Upgrade status* box. If you need to cancel the scheduled upgrade, you can click *Cancel this upgrade* from the *Upgrade status* box.
 
 [WARNING]
 ====

modules/upgrade.adoc

@@ -7,6 +7,7 @@
 [id="upgrade_{context}"]
 = Understanding {product-title} cluster upgrades
 
+[role="_abstract"]
 When upgrades are made available for your {product-title} cluster, you can upgrade to the newest version through {cluster-manager-first} or {cluster-manager} CLI. You can set your upgrade policies on existing clusters or during cluster creation, and upgrades can be scheduled to occur automatically or manually.
 
 [IMPORTANT]

upgrading/osd-upgrades.adoc

@@ -2,6 +2,7 @@
 [id="osd-upgrades"]
 = {product-title} cluster upgrades
 :context: osd-upgrades
+
 include::_attributes/attributes-openshift-dedicated.adoc[]
 
 toc::[]
@@ -15,16 +16,16 @@ include::modules/osd-lifecycle-policy.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
-* For more information about the {product-title} life cycle policy, see xref:../osd_architecture/osd_policy/osd-life-cycle.adoc#osd-life-cycle_life-cycle-overview[{product-title} update life cycle].
+* xref:../osd_architecture/osd_policy/osd-life-cycle.adoc#osd-life-cycle_life-cycle-overview[{product-title} update life cycle]
 
 include::modules/upgrade.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
-* For more information about the service log and adding cluster notification contacts, see xref:../osd_cluster_admin/osd-cluster-notifications.adoc#managed-cluster-notification-view-hcc_osd-cluster-notifications[Accessing cluster notifications in {hybrid-console}].
+* xref:../osd_cluster_admin/osd-cluster-notifications.adoc#managed-cluster-notification-view-hcc_osd-cluster-notifications[Accessing cluster notifications in {hybrid-console}]
 
-* For more information on how to update a WIF configuration, see xref:../osd_gcp_clusters/creating-a-gcp-cluster-with-workload-identity-federation.adoc#wif-configuration-update_osd-creating-a-cluster-on-gcp-with-workload-identity-federation[Updating a WIF configuration].
+* xref:../osd_gcp_clusters/creating-a-gcp-cluster-with-workload-identity-federation.adoc#wif-configuration-update_osd-creating-a-cluster-on-gcp-with-workload-identity-federation[Updating a WIF configuration]
 
 include::modules/upgrade-auto.adoc[leveloffset=+1]
 include::modules/upgrade-manual.adoc[leveloffset=+1]