OSDOCS#10543: Replace terms with new attributes

Author: xenolinux

_attributes/common-attributes.adoc

@@ -322,7 +322,5 @@ endif::[]
 :cap-vsphere-short: Cluster API Provider vSphere
 
 // Hosted control planes related attributes
-:mce-first: multicluster engine for Kubernetes operator (MCE)
-:mce-short: MCE
 :hcp-capital: Hosted control planes
 :hcp: hosted control planes

architecture/control-plane.adoc

@@ -78,7 +78,7 @@ include::modules/hosted-control-planes-overview.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
-* 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[Hosted control planes]
+* 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}]
 
 include::modules/hosted-control-planes-concepts-personas.adoc[leveloffset=+2]
 include::modules/hosted-control-planes-version-support.adoc[leveloffset=+2]

architecture/mce-overview-ocp.adoc

@@ -1,12 +1,12 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="mce-overview-ocp"]
-= About multicluster engine for Kubernetes operator
 include::_attributes/common-attributes.adoc[]
+= About multicluster engine for Kubernetes operator
 :context: mce-overview-ocp
 
 toc::[]
 
-One of the challenges of scaling Kubernetes environments is managing the lifecycle of a growing fleet. To meet that challenge, you can use multicluster engine for Kubernetes operator (MCE). The operator delivers full lifecycle capabilities for managed {product-title} clusters and partial lifecycle management for other Kubernetes distributions. It is available in two ways:
+One of the challenges of scaling Kubernetes environments is managing the lifecycle of a growing fleet. To meet that challenge, you can use the multicluster engine for Kubernetes operator. The operator delivers full lifecycle capabilities for managed {product-title} clusters and partial lifecycle management for other Kubernetes distributions. It is available in two ways:
 
 * As a standalone operator that you install as part of your {product-title} or {oke} subscription
 * As part of link:https://access.redhat.com/products/red-hat-advanced-cluster-management-for-kubernetes[Red Hat Advanced Cluster Management for Kubernetes]
@@ -16,7 +16,7 @@ One of the challenges of scaling Kubernetes environments is managing the lifecyc
 
 When you enable multicluster engine on {product-title}, you gain the following capabilities:
 
-* xref:../architecture/control-plane.adoc#hosted-control-planes-overview_control-plane[Hosted control planes], which is a feature that is based on the HyperShift project. With a centralized hosted control plane, you can operate {product-title} clusters in a hyperscale manner.
+* xref:../architecture/control-plane.adoc#hosted-control-planes-overview_control-plane[{hcp-capital}], which is a feature that is based on the HyperShift project. With a centralized hosted control plane, you can operate {product-title} clusters in a hyperscale manner.
 * Hive, which provisions self-managed {product-title} clusters to the hub and completes the initial configurations for those clusters.
 * klusterlet agent, which registers managed clusters to the hub.
 * Infrastructure Operator, which manages the deployment of the Assisted Service to orchestrate on-premise bare metal and vSphere installations of {product-title}, such as {sno} on bare metal. The Infrastructure Operator includes xref:../edge_computing/ztp-deploying-far-edge-clusters-at-scale.adoc#ztp-challenges-of-far-edge-deployments_ztp-deploying-far-edge-clusters-at-scale[{ztp-first}], which fully automates cluster creation on bare metal and vSphere provisioning with GitOps workflows to manage deployments and configuration changes.

hosted_control_planes/hcp-authentication-authorization.adoc

@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="hcp-authentication-authorization"]
-= Authentication and authorization for hosted control planes
 include::_attributes/common-attributes.adoc[]
+= Authentication and authorization for {hcp}
 :context: hcp-authentication-authorization
 
 toc::[]

hosted_control_planes/hcp-backup-restore-dr.adoc

@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="hcp-backup-restore-dr"]
-= Backup, restore, and disaster recovery for hosted control planes
 include::_attributes/common-attributes.adoc[]
+= Backup, restore, and disaster recovery for {hcp}
 :context: hcp-backup-restore-dr
 
 toc::[]
@@ -19,11 +19,11 @@ include::modules/hosted-cluster-single-node-recovery.adoc[leveloffset=+2]
 [id="hcp-backup-restore"]
 == Backing up and restoring etcd on a hosted cluster on {aws-short}
 
-If you use hosted control planes for {product-title}, the process to back up and restore etcd is different from xref:../backup_and_restore/control_plane_backup_and_restore/backing-up-etcd.adoc#backing-up-etcd-data_backup-etcd[the usual etcd backup process].
+If you use {hcp} for {product-title}, the process to back up and restore etcd is different from xref:../backup_and_restore/control_plane_backup_and_restore/backing-up-etcd.adoc#backing-up-etcd-data_backup-etcd[the usual etcd backup process].
 
-The following procedures are specific to hosted control planes on {aws-short}.
+The following procedures are specific to {hcp} on {aws-short}.
 
-:FeatureName: Hosted control planes on the {aws-short} platform
+:FeatureName: {hcp-capital} on the {aws-short} platform
 include::snippets/technology-preview.adoc[]
 
 // Backing up etcd on a hosted cluster
@@ -40,7 +40,7 @@ include::modules/hosted-cluster-etcd-backup-restore-on-prem.adoc[leveloffset=+1]
 
 In a situation where you need disaster recovery (DR) for a hosted cluster, you can recover a hosted cluster to the same region within {aws-short}. For example, you need DR when the upgrade of a management cluster fails and the hosted cluster is in a read-only state.
 
-:FeatureName: Hosted control planes
+:FeatureName: {hcp-capital}
 include::snippets/technology-preview.adoc[]
 
 The DR process involves three main steps:

hosted_control_planes/hcp-getting-started.adoc

@@ -1,12 +1,12 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="hcp-getting-started"]
-= Getting started with hosted control planes
 include::_attributes/common-attributes.adoc[]
+= Getting started with {hcp}
 :context: hcp-getting-started
 
 toc::[]
 
-To get started with hosted control planes for {product-title}, you first configure your hosted cluster on the provider that you want to use. Then, you complete a few management tasks.
+To get started with {hcp} for {product-title}, you first configure your hosted cluster on the provider that you want to use. Then, you complete a few management tasks.
 
 You can view the procedures by selecting from one of the following providers:
 
@@ -24,7 +24,7 @@ You can view the procedures by selecting from one of the following providers:
 ** Scale the `NodePool` object for the hosted cluster
 ** Handle ingress traffic for the hosted cluster
 ** Enable node auto-scaling for the hosted cluster
-* link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#configure-hosted-disconnected[Configuring hosted control planes in a disconnected environment]
+* link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#configure-hosted-disconnected[Configuring {hcp} in a disconnected environment]
 
 * To destroy a hosted cluster on bare metal, follow the instructions in link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#hypershift-cluster-destroy-bm[Destroying a hosted cluster on bare metal].
 * If you want to disable the hosted control plane feature, see link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#disable-hosted-control-planes[Disabling the hosted control plane feature].
@@ -36,28 +36,28 @@ You can view the procedures by selecting from one of the following providers:
 * link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#hosted-install-cli[Installing the hosted control plane command line interface]
 * link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#hosted-cluster-workload-distributing[Distributing hosted cluster workloads]
 * link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#hosted-control-planes-manage-kubevirt[Managing hosted control plane clusters on OpenShift Virtualization]: Create {product-title} clusters with worker nodes that are hosted by KubeVirt virtual machines.
-* link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#configure-hosted-disconnected[Configuring hosted control planes in a disconnected environment]
+* link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#configure-hosted-disconnected[Configuring {hcp} in a disconnected environment]
 
 * To destroy a hosted cluster is on {VirtProductName}, follow the instructions in link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#hypershift-cluster-destroy-kubevirt[Destroying a hosted cluster on OpenShift Virtualization].
 * If you want to disable the hosted control plane feature, see link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#disable-hosted-control-planes[Disabling the hosted control plane feature].
 
 [id="hcp-getting-started-aws"]
 == {aws-first}
 
-:FeatureName: Hosted control planes on the {aws-short} platform
+:FeatureName: {hcp-capital} on the {aws-short} platform
 include::snippets/technology-preview.adoc[]
 
 * link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#hosting-cluster-aws-infra-reqs[AWS infrastructure requirements]: Review the infrastructure requirements to create a hosted cluster on {aws-short}.
 * link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#hosting-service-cluster-configure-aws[Configuring hosted control plane clusters on AWS (Technology Preview)]: The tasks to configure hosted control plane clusters on {aws-short} include creating the {aws-short} S3 OIDC secret, creating a routable public zone, enabling external DNS, enabling {aws-short} PrivateLink, and deploying a hosted cluster.
-* xref:../networking/hardware_networks/configuring-sriov-operator.adoc#sriov-operator-hosted-control-planes_configuring-sriov-operator[Deploying the SR-IOV Operator for hosted control planes]: After you configure and deploy your hosting service cluster, you can create a subscription to the Single Root I/O Virtualization (SR-IOV) Operator on a hosted cluster. The SR-IOV pod runs on worker machines rather than the control plane.
+* xref:../networking/hardware_networks/configuring-sriov-operator.adoc#sriov-operator-hosted-control-planes_configuring-sriov-operator[Deploying the SR-IOV Operator for {hcp}]: After you configure and deploy your hosting service cluster, you can create a subscription to the Single Root I/O Virtualization (SR-IOV) Operator on a hosted cluster. The SR-IOV pod runs on worker machines rather than the control plane.
 
 * To destroy a hosted cluster on AWS, follow the instructions in link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#hypershift-cluster-destroy-aws[Destroying a hosted cluster on AWS].
 * If you want to disable the hosted control plane feature, see link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#disable-hosted-control-planes[Disabling the hosted control plane feature].
 
 [id="hcp-getting-started-ibmz"]
 == {ibm-z-title}
 
-:FeatureName: Hosted control planes on the {ibm-z-title} platform
+:FeatureName: {hcp-capital} on the {ibm-z-title} platform
 include::snippets/technology-preview.adoc[]
 
 * link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#hosted-install-cli[Installing the hosted control plane command line interface]
@@ -66,16 +66,16 @@ include::snippets/technology-preview.adoc[]
 [id="hcp-getting-started-ibmpower"]
 == {ibm-power-title}
 
-:FeatureName: Hosted control planes on the {ibm-power-title} platform
+:FeatureName: {hcp-capital} on the {ibm-power-title} platform
 include::snippets/technology-preview.adoc[]
 
 * link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#hosted-install-cli[Installing the hosted control plane command line interface]
-* link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#config-hosted-service-ibmpower[Configuring the hosting cluster on a 64-bit x86 OpenShift Container Platform cluster to create hosted control planes for IBM Power compute nodes (Technology Preview)]
+* link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#config-hosted-service-ibmpower[Configuring the hosting cluster on a 64-bit x86 OpenShift Container Platform cluster to create {hcp} for IBM Power compute nodes (Technology Preview)]
 
 [id="hcp-getting-started-non-bm-agent"]
 == Non bare metal agent machines
 
-:FeatureName: Hosted control planes clusters using non bare metal agent machines
+:FeatureName: {hcp-capital} clusters using non bare metal agent machines
 include::snippets/technology-preview.adoc[]
 
 * link:https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/clusters/cluster_mce_overview#hosted-install-cli[Installing the hosted control plane command line interface]

hosted_control_planes/hcp-observability.adoc

@@ -1,12 +1,12 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="hcp-observability"]
-= Hosted control planes Observability
 include::_attributes/common-attributes.adoc[]
+= {hcp-capital} Observability
 :context: hcp-observability
 
 toc::[]
 
-You can gather metrics for hosted control planes by configuring metrics sets. The HyperShift Operator can create or delete monitoring dashboards in the management cluster for each hosted cluster that it manages.
+You can gather metrics for {hcp} by configuring metrics sets. The HyperShift Operator can create or delete monitoring dashboards in the management cluster for each hosted cluster that it manages.
 
 //using service-level DNS for control plane services
 include::modules/hosted-control-planes-metrics-sets.adoc[leveloffset=+1]

hosted_control_planes/hcp-troubleshooting.adoc

@@ -1,12 +1,12 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="hcp-troubleshooting"]
-= Troubleshooting hosted control planes
 include::_attributes/common-attributes.adoc[]
+= Troubleshooting {hcp}
 :context: hcp-troubleshooting
 
 toc::[]
 
-If you encounter issues with hosted control planes, see the following information to guide you through troubleshooting.
+If you encounter issues with {hcp}, see the following information to guide you through troubleshooting.
 
 include::modules/hosted-control-planes-troubleshooting.adoc[leveloffset=+1]
 

hosted_control_planes/hcp-updating.adoc

@@ -1,12 +1,12 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="hcp-updating"]
-= Updating hosted control planes
 include::_attributes/common-attributes.adoc[]
+= Updating {hcp}
 :context: hcp-updating
 
 toc::[]
 
-Updates for hosted control planes involve updating the hosted cluster and the node pools. For a cluster to remain fully operational during an update process, you must meet the requirements of the link:https://kubernetes.io/releases/version-skew-policy/[Kubernetes version skew policy] while completing the control plane and node updates.
+Updates for {hcp} involve updating the hosted cluster and the node pools. For a cluster to remain fully operational during an update process, you must meet the requirements of the link:https://kubernetes.io/releases/version-skew-policy/[Kubernetes version skew policy] while completing the control plane and node updates.
 
 // Updates for the hosted cluster
 include::modules/hcp-updates-hosted-cluster.adoc[leveloffset=+1]

hosted_control_planes/index.adoc

@@ -1,10 +1,10 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="hcp-overview"]
-= Hosted control planes overview
 include::_attributes/common-attributes.adoc[]
+= {hcp-capital} overview
 :context: hcp-overview
 
-You can deploy {product-title} 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 control plane. With hosted control planes for {product-title}, you create control planes as pods on a hosting cluster without the need for dedicated virtual or physical machines for each control plane.
+You can deploy {product-title} clusters by using two different control plane configurations: standalone or {hcp}. The standalone configuration uses dedicated virtual machines or physical machines to host the control plane. With {hcp} for {product-title}, you create control planes as pods on a hosting cluster without the need for dedicated virtual or physical machines for each control plane.
 
 toc::[]
 
@@ -13,7 +13,7 @@ include::modules/hosted-control-planes-overview.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-* 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[Hosted control planes]
+* 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}]
 
 include::modules/hosted-control-planes-concepts-personas.adoc[leveloffset=+1]
 include::modules/hosted-control-planes-version-support.adoc[leveloffset=+1]