No Jira: Fixing links in HCP docs

hosted_control_planes/hcp-troubleshooting.adoc

@@ -9,6 +9,12 @@ toc::[]
 If you encounter issues with {hcp}, see the following information to guide you through troubleshooting.
 
 include::modules/hosted-control-planes-troubleshooting.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../hosted_control_planes/hcp-prepare/hcp-cli.adoc[Installing the {hcp} command-line interface]
+
 include::modules/hcp-must-gather-dc.adoc[leveloffset=+1]
 
 [role="_additional-resources"]

hosted_control_planes/hcp_high_availability/hcp-backup-restore-aws.adoc

@@ -8,9 +8,6 @@ toc::[]
 
 You can back up and restore etcd on a hosted cluster on {aws-first} to fix failures.
 
-:FeatureName: Hosted control planes on the {aws-short} platform
-include::snippets/technology-preview.adoc[]
-
 include::modules/backup-etcd-hosted-cluster.adoc[leveloffset=+1]
 
 include::modules/restoring-etcd-snapshot-hosted-cluster.adoc[leveloffset=+1]

hosted_control_planes/hcp_high_availability/hcp-disaster-recovery-aws.adoc

@@ -8,9 +8,6 @@ toc::[]
 
 You can recover a hosted cluster to the same region within {aws-first}. For example, you need disaster recovery when the upgrade of a management cluster fails and the hosted cluster is in a read-only state.
 
-:FeatureName: Hosted control planes
-include::snippets/technology-preview.adoc[]
-
 The disaster recovery process involves the following steps:
 
 . Backing up the hosted cluster on the source management cluster

modules/hosted-control-planes-troubleshooting.adoc

@@ -29,7 +29,7 @@ Although the output does not contain any secret objects from the cluster, it can
 
 * You need the `name` value for the `HostedCluster` resource and the namespace where the CR is deployed.
 
-* You must have the `hcp` command line interface installed. For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.9/html/clusters/cluster_mce_overview#hosted-install-cli[Installing the {hcp} command line interface].
+* You must have the `hcp` command-line interface installed. For more information, see "Installing the {hcp} command-line interface".
 
 * You must have the OpenShift CLI (`oc`) installed.
 

modules/sriov-operator-hosted-control-planes.adoc

@@ -7,15 +7,12 @@
 [id="sriov-operator-hosted-control-planes_{context}"]
 = Deploying the SR-IOV Operator for {hcp}
 
-:FeatureName: {hcp-capital} on the AWS platform
-include::snippets/technology-preview.adoc[]
-
 [role="_abstract"]
 After you configure and deploy your hosting service cluster, you can create a subscription to the SR-IOV Operator on a hosted cluster. The SR-IOV pod runs on worker machines rather than the control plane.
 
 .Prerequisites
 
-You must configure and deploy the hosted cluster on AWS. For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.9/html/clusters/cluster_mce_overview#hosting-service-cluster-configure-aws[Configuring the hosting cluster on AWS (Technology Preview)].
+You must configure and deploy the hosted cluster on AWS.
 
 .Procedure
 
@@ -78,4 +75,4 @@ sriov-network-operator.{product-version}.0-202211021237   SR-IOV Network Operato
 [source,terminal]
 ----
 $ oc get pods -n openshift-sriov-network-operator
-----
+----

scalability_and_performance/using-node-tuning-operator.adoc

@@ -29,5 +29,4 @@ include::modules/advanced-node-tuning-hosted-cluster.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
-
-For more information about {hcp}, see link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.9/html/clusters/cluster_mce_overview#hosted-control-planes-intro[{hcp-capital}].
+* xref:../hosted_control_planes/index.adoc#hosted-control-planes-overview[{hcp-capital} overview]