stolostron/backlog#26070--post GA changes that had to wait bc of build

Author: swopebe

clusters/hosted_control_planes/configure_hosted.adoc

@@ -314,4 +314,4 @@ api-int.example.krnl.es.    IN A 192.168.122.22
 *.apps.example.krnl.es. IN A 192.168.122.23
 ----
 
-You can now deploy the SR-IOV Operator. See link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.12/html/networking/hardware-networks#sriov-operator-hosted-control-planes_configuring-sriov-operator[Deploying the SR-IOV Operator for hosted control planes] to learn more about deploying the SR-IOV Operator.
+You can now deploy the SR-IOV Operator. See link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.12/html/networking/hardware-networks#sriov-operator-hosted-control-planes_configuring-sriov-operator[Deploying the SR-IOV Operator for hosted control planes] to learn more about deploying the SR-IOV Operator.

clusters/hosted_control_planes/create_hosted.adoc

@@ -237,7 +237,6 @@ export HOSTED_CLUSTER_NAME="example"
 export HOSTED_CONTROL_PLANE_NAMESPACE="${CLUSTERS_NAMESPACE}-${HOSTED_CLUSTER_NAME}"
 export BASEDOMAIN="krnl.es"
 export PULL_SECRET_FILE=$PWD/pull-secret
-export OCP_RELEASE=4.12z-x86_64
 export MACHINE_CIDR=192.168.122.0/24
 # Typically the namespace is created by the hypershift-operator 
 # but agent cluster creation generates a capi-provider role that
@@ -250,7 +249,6 @@ hypershift create cluster agent \
     --agent-namespace=${HOSTED_CONTROL_PLANE_NAMESPACE} \
     --base-domain=${BASEDOMAIN} \
     --api-server-address=api.${HOSTED_CLUSTER_NAME}.${BASEDOMAIN} \
-    --release-image=quay.io/openshift-release-dev/ocp-release:${OCP_RELEASE}
 ----
 
 . After a few moments, verify that your hosted control plane pods are up and running:
@@ -352,7 +350,7 @@ e57a637f-745b-496e-971d-1abbf03341ba             true       auto-assign
 
 * To add agents by using Metal3, follow these instructions:
 
-. Use the Assisted Service and Hive to create the custom ISO and the Baremetal Operator to perform the installation.
+. Use the Assisted Service to create the custom ISO and the Baremetal Operator to perform the installation.
 +
 **Important:** Because the `BaremetalHost` objects are created outside the baremetal-operator namespace, you must configure the Operator to watch all namespaces.
 +

clusters/hosted_control_planes/hosted_intro.adoc

@@ -2,7 +2,6 @@
 = Hosted control planes for {ocp} (Technology Preview)
 
 With {mce} 2.2, you can deploy {ocp} clusters by using two different control plane configurations: standalone or hosted control planes. The standalone configuration uses dedicated virtual machines or physical machines to host the {ocp-short} control plane. With hosted control planes for {ocp-short}, you create control planes as pods on a hosting cluster without the need for dedicated physical machines for each control plane.
-c687f37 (initial updates to add agent provider docs to hosted control planes docs)
 
 Hosted control planes for {ocp-short} are available as a Technology Preview feature on Amazon Web Services (AWS) and on bare metal or virtual environments. You can host the control planes on {ocp} version 4.10.7 and later.