OSDOCS-14434: Changed the ROSA name variables.

Author: EricPonvelle

_attributes/attributes-openshift-dedicated.adoc

@@ -27,6 +27,15 @@
 :sts-first: Security Token Service (STS)
 :sts-full: Security Token Service
 :sts-short: STS
+// ROSA specific
+:hcp: hosted control planes
+:rosa-first: Red Hat OpenShift Service on AWS (ROSA) with {hcp} (HCP)
+:rosa-short: ROSA with HCP
+:rosa-classic-first: {product-title} (ROSA) (classic architecture)
+:rosa-classic: Red Hat OpenShift Service on AWS (classic architecture)
+:rosa-classic-short: ROSA (classic)
+:classic: {rosa-classic}
+:classic-short: {rosa-classic-short}
 //logging
 :logging-title: logging for Red Hat OpenShift
 :logging-title-uc: Logging for Red Hat OpenShift
@@ -49,11 +58,6 @@
 //Formerly known as CodeReady Containers and CodeReady Workspaces
 :openshift-local-productname: Red Hat OpenShift Local
 :openshift-dev-spaces-productname: Red Hat OpenShift Dev Spaces
-:hcp: hosted control planes
-:hcp-title: ROSA with HCP
-:hcp-title-first: {product-title} (ROSA) with {hcp} (HCP)
-:rosa-classic: ROSA (classic architecture)
-:rosa-classic-first: {product-title} (ROSA) (classic architecture)
 :egress-lockdown: {hcp-title} clusters with zero egress
 //ROSA CLI variables
 :zero-egress: zero egress

_distro_map.yml

@@ -196,7 +196,7 @@ openshift-aro:
       name: '4'
       dir: aro/4
 openshift-rosa:
-  name: Red Hat OpenShift Service on AWS
+  name: Red Hat OpenShift Service on AWS (classic architecture)
   author: OpenShift Documentation Project <[email protected]>
   site: commercial
   site_name: Documentation

modules/rosa-hcp-architecture.adoc

@@ -5,21 +5,21 @@
 [id="rosa-hcp-architecture_{context}"]
 = ROSA with HCP architecture
 
-In {hcp-title-first}, the ROSA service hosts a highly-available, single-tenant OpenShift control plane. The hosted control plane is deployed across 3 availability zones with 2 API server instances and 3 etcd instances. 
+In {rosa-first}, the ROSA service hosts a highly-available, single-tenant OpenShift control plane. The hosted control plane is deployed across 3 availability zones with 2 API server instances and 3 etcd instances. 
 
 You can create a ROSA with HCP cluster with or without an internet-facing API server. Private API servers are only accessible from your VPC subnets. You access the hosted control plane through an AWS PrivateLink endpoint. 
 
 The worker nodes are deployed in your AWS account and run on your VPC private subnets. You can add additional private subnets from one or more availability zones to ensure high availability. Worker nodes are shared by OpenShift components and applications. OpenShift components such as the ingress controller, image registry, and monitoring are deployed on the worker nodes hosted on your VPC.
 
-.ROSA with HCP architecture
-image::544_OpenShift_ROSA-HCP_architecture-model.png[ROSA with HCP architecture]
+.{rosa-short} architecture
+image::544_OpenShift_ROSA-HCP_architecture-model.png[{rosa-short} architecture]
 
 [id="rosa-hcp-network-architecture_{context}"]
-== ROSA with HCP architecture on public and private networks
-With ROSA with HCP, you can create your clusters on public or private networks. The following images depict the architecture of both public and private networks.
+== {rosa-short} architecture on public and private networks
+With {rosa-short}, you can create your clusters on public or private networks. The following images depict the architecture of both public and private networks.
 
-.ROSA with HCP deployed on a public network
-image::544_OpenShift_ROSA-HCP-and-ROSA-Classic-public.png[ROSA with HCP deployed on a public network]
+.{rosa-short} deployed on a public network
+image::544_OpenShift_ROSA-HCP-and-ROSA-Classic-public.png[{rosa-short} deployed on a public network]
 
-.ROSA with HCP deployed on a private network
-image::544_OpenShift_ROSA-HCP-and-ROSA-Classic-private.png[ROSA with HCP deployed on a private network]
+.{rosa-short} deployed on a private network
+image::544_OpenShift_ROSA-HCP-and-ROSA-Classic-private.png[{rosa-short} deployed on a private network]

rosa_architecture/about-hcp.adoc

@@ -90,7 +90,7 @@ Each machine pool in a {product-title} cluster upgrades independently. Because t
 
 The following image depicts how machine pools work within ROSA and {rosa-classic} clusters:
 
-image::hcp-rosa-machine-pools.png[Machine pools on ROSA classic and {hcp-tilte} clusters]
+image::hcp-rosa-machine-pools.png[Machine pools on {rosa-classic-short} and {rosa-short} clusters]
 
 [NOTE]
 ====