Merge pull request #66730 from mburke5678/ocm-fix-hard-link

mburke5678 · web-flow · commit c15e70be981e · 2023-10-23T12:45:11.000-04:00
Updated OSD link to Support book
diff --git a/modules/ocm-overview-tab.adoc b/modules/ocm-overview-tab.adoc
@@ -26,5 +26,5 @@ The **Overview** tab provides information about how your cluster was configured:
 * **Nodes** shows the actual and desired nodes on the cluster. These numbers might not match due to cluster scaling.
 * **Network** field shows the address and prefixes for network connectivity.
 * **Resource usage** section of the tab displays the resources in use with a graph.
-* **Advisor recommendations** section gives insight in relation to security, performance, availability, and stablility. This section requires the use of remote health functionality. See link:https://docs.openshift.com/container-platform/4.9/support/remote_health_monitoring/using-insights-to-identify-issues-with-your-cluster.html[Using Insights to identify issues with your cluster].
+* **Advisor recommendations** section gives insight in relation to security, performance, availability, and stablility. This section requires the use of remote health functionality. See xref:../support/remote_health_monitoring/using-insights-to-identify-issues-with-your-cluster.adoc#using-insights-to-identify-issues-with-your-cluster[Using Insights to identify issues with your cluster].
 * **Cluster history** section shows everything that has been done with the cluster including creation and when a new version is identified.
diff --git a/modules/osd-aws-privatelink-firewall-prerequisites.adoc b/modules/osd-aws-privatelink-firewall-prerequisites.adoc
@@ -168,8 +168,7 @@ CDN host names, such as `cdn01.quay.io`, are covered when you add a wildcard ent
 |Required for managed OpenShift-specific telemetry.
 |===
 +
-Managed clusters require enabling telemetry to allow Red Hat to react more quickly to problems, better support the customers, and better understand how product upgrades impact clusters.
-See link:https://docs.openshift.com/container-platform/4.9/support/remote_health_monitoring/about-remote-health-monitoring.html[About remote health monitoring] for more information about how remote health monitoring data is used by Red Hat.
+Managed clusters require enabling telemetry to allow Red Hat to react more quickly to problems, better support the customers, and better understand how product upgrades impact clusters. See xref:../support/remote_health_monitoring/about-remote-health-monitoring.adoc#about-remote-health-monitoring[About remote health monitoring] for more information about how remote health monitoring data is used by Red Hat.
 
 . Allowlist the following Amazon Web Services (AWS) API URls:
 +

Original file line number	Diff line number	Diff line change
@@ -168,8 +168,7 @@ CDN host names, such as `cdn01.quay.io`, are covered when you add a wildcard ent
`168`	`168`	`\|Required for managed OpenShift-specific telemetry.`
`169`	`169`	`\|===`
`170`	`170`	`+`
`171`		`-Managed clusters require enabling telemetry to allow Red Hat to react more quickly to problems, better support the customers, and better understand how product upgrades impact clusters.`
`172`		`-See link:https://docs.openshift.com/container-platform/4.9/support/remote_health_monitoring/about-remote-health-monitoring.html[About remote health monitoring] for more information about how remote health monitoring data is used by Red Hat.`
	`171`	`+Managed clusters require enabling telemetry to allow Red Hat to react more quickly to problems, better support the customers, and better understand how product upgrades impact clusters. See xref:../support/remote_health_monitoring/about-remote-health-monitoring.adoc#about-remote-health-monitoring[About remote health monitoring] for more information about how remote health monitoring data is used by Red Hat.`
`173`	`172`
`174`	`173`	`. Allowlist the following Amazon Web Services (AWS) API URls:`
`175`	`174`	`+`