fixing all errors and warnings for OSDD upgrading

bringing in the vale file

remove line from  vale file

xref was already in additional resorces under life cycle module so removing

Author: fmcdonal

modules/.vale.ini

@@ -44,4 +44,4 @@ Vale.Avoid = YES
 [asciidoctor]
 temp-ifdef = YES
 temp-ifndef = NO
-temp-ifeval = temp
+temp-ifeval = temp

modules/osd-lifecycle-policy.adoc

@@ -10,4 +10,4 @@
 [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].
+You can use update channels to decide which Red Hat {OCP} 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

@@ -19,7 +19,7 @@ You can use {cluster-manager} to schedule recurring, automatic upgrades for z-st
 
 . To schedule recurring upgrades, select *Recurring updates*.
 
-. Provide an administrator’s acknowledgment and click *Approve and continue*. {cluster-manager} does not start scheduled y-stream updates for minor versions without receiving an administrator’s acknowledgment.
+. Provide an administrator's acknowledgment and click *Approve and continue*. {cluster-manager} does not start scheduled y-stream updates for minor versions without receiving an administrator's acknowledgment.
 +
 [IMPORTANT]
 ====

modules/upgrade-manual.adoc

@@ -53,5 +53,5 @@ Before upgrading a Workload Identity Federation (WIF)-enabled {product-title} on
 
 [WARNING]
 ====
-In the event that a CVE or other critical issue to {product-title} is found, all clusters are upgraded within 48 hours of the fix being released. You are notified when the fix is available and informed that the cluster will be automatically upgraded at your latest preferred start time before the 48 hour window closes. You can also upgrade manually at any time before the recurring upgrade starts.
+If a Common Vulnerabilities and Exposures (CVE) or other critical issue to {product-title} is found, all clusters are upgraded within 48 hours of the fix being released. You are notified when the fix is available and informed that the cluster will be automatically upgraded at your latest preferred start time before the 48 hour window closes. You can also upgrade manually at any time before the recurring upgrade starts.
 ====

modules/upgrade.adoc

@@ -21,7 +21,7 @@ You can also set a grace period for how long `PodDisruptionBudget` protected wor
 
 [NOTE]
 ====
-All Kubernetes objects and PVs in each {product-title} cluster are backed up as part of the {product-title} service. Application and application data backups are not a part of the {product-title} service. Ensure you have a backup policy in place for your applications and application data prior to scheduling upgrades.
+All Kubernetes objects and Persistent Volumes (PVs) in each {product-title} cluster are backed up as part of the {product-title} service. Application and application data backups are not a part of the {product-title} service. Ensure you have a backup policy in place for your applications and application data before scheduling upgrades.
 ====
 
 [NOTE]
@@ -34,7 +34,7 @@ When following a scheduled upgrade policy, there might be a delay of an hour or
 
 Upgrades can be scheduled to occur automatically on a day and time specified by the cluster owner or administrator. Upgrades occur on a weekly basis, unless an upgrade is unavailable for that week.
 
-If you select recurring updates for your cluster, you must provide an administrator’s acknowledgment. {cluster-manager} does not start scheduled y-stream updates for minor versions without receiving an administrator’s acknowledgment.
+If you select recurring updates for your cluster, you must provide an administrator's acknowledgment. {cluster-manager} does not start scheduled y-stream updates for minor versions without receiving an administrator's acknowledgment.
 
 [NOTE]
 ====
@@ -44,9 +44,9 @@ Recurring upgrade policies are optional and if they are not set, the upgrade pol
 [id="upgrade-manual_upgrades_{context}"]
 == Individual upgrades
 
-If you opt for individual upgrades, you are responsible for updating your cluster. If you select an update version that requires approval, you must provide an administrator’s acknowledgment.
+If you opt for individual upgrades, you are responsible for updating your cluster. If you select an update version that requires approval, you must provide an administrator's acknowledgment.
 
-If your cluster version becomes outdated, it will transition to a limited support status. For more information on OpenShift life cycle policies, see xref:../osd_architecture/osd_policy/osd-life-cycle.adoc#osd-life-cycle[{product-title} update life cycle].
+If your cluster version becomes outdated, it changes to a limited support status.
 
 [id="upgrade-notifications_{context}"]
 == Upgrade notifications
@@ -71,7 +71,7 @@ For recurring upgrades, you will also receive email notifications before the upg
 
 [id="wif-upgrades_{context}"]
 == Cluster upgrades with Workload Identity Federation (WIF)
-Before upgrading an {product-title} on {GCP} cluster with WIF authentication type to a newer y-stream version, you must update the WIF configuration to that version as well. Failure to do so before attempting to upgrade the cluster version will result in an error.
+Before upgrading an {product-title} on {GCP} cluster with WIF authentication type to a newer y-stream version, you must update the WIF configuration to that version. Failure to do so before attempting to upgrade the cluster version will result in an error.
 For more information on how to update a WIF configuration, see the  _Additional resources_ section.
 
 [NOTE]