Build Fixes: Build fixes for main

Author: EricPonvelle

getting_started/openshift-overview.adoc

@@ -100,7 +100,7 @@ be reviewed by cluster administrators and xref:../operators/admin/olm-adding-ope
 
 * **xref:../scalability_and_performance/scaling-cluster-monitoring-operator.adoc#scaling-cluster-monitoring-operator[Scale] and xref:../scalability_and_performance/using-node-tuning-operator.adoc#using-node-tuning-operator[tune] clusters**: Set cluster limits, tune nodes, scale cluster monitoring, and optimize networking, storage, and routes for your environment.
 
-* **xref:../updating/installing-update-service.adoc#installing-update-service[Understanding the OpenShift Update Service]**: Learn about installing and managing a local OpenShift Update Service for recommending {product-title} updates in restricted network environments.
+* **xref:../updating/updating-restricted-network-cluster.adoc#update-service-overview_updating-restricted-network-cluster[Understanding the OpenShift Update Service]**: Learn about installing and managing a local OpenShift Update Service for recommending {product-title} updates in restricted network environments.
 
 * **xref:../monitoring/monitoring-overview.adoc#monitoring-overview[Monitor clusters]**:
 Learn to  xref:../monitoring/configuring-the-monitoring-stack.adoc#configuring-the-monitoring-stack[configure the monitoring stack].

modules/upgrade-49-acknowledgement.adoc

@@ -8,7 +8,7 @@
 [id="upgrade-49-acknowledgement_{context}"]
 = Administrator acknowledgment when upgrading to OpenShift 4.9
 
-{product-title} 4.9 uses Kubernetes 1.22, which removed a link:https://docs.openshift.com/container-platform/4.9/release_notes/ocp-4-9-release-notes.html#ocp-4-9-removed-kube-1-22-apis[significant number of deprecated `v1beta1` APIs].
+{product-title} 4.9 uses Kubernetes 1.22, which removed a significant number of deprecated `v1beta1` APIs.
 
 {product-title} 4.8.14 introduced a requirement that an administrator must provide a manual acknowledgment before the cluster can be upgraded from {product-title} 4.8 to 4.9. This is to help prevent issues after upgrading to {product-title} 4.9, where APIs that have been removed are still in use by workloads, tools, or other components running on or interacting with the cluster. Administrators must evaluate their cluster for any APIs in use that will be removed and migrate the affected components to use the appropriate new API version. After this is done, the administrator can provide the administrator acknowledgment.
 

upgrading/osd-upgrading-cluster-prepare.adoc

@@ -25,7 +25,7 @@ include::modules/osd-update-preparing-list.adoc[leveloffset=+1]
 There are several methods to help administrators identify where APIs that will be removed are in use. However, {product-title} cannot identify all instances, especially workloads that are idle or external tools that are used. It is the responsibility of the administrator to properly evaluate all workloads and other integrations for instances of removed APIs.
 
 // Reviewing alerts to identify uses of removed APIs
-include::modules/osd-update-preparing-evaluate-alerts.adoc[leveloffset=+1]
+include::modules/osd-update-preparing-evaluate-alerts.adoc[leveloffset=+2]
 
 // Using APIRequestCount to identify uses of removed APIs
 include::modules/osd-update-preparing-evaluate-apirequestcount.adoc[leveloffset=+2]