Merge pull request #61151 from smunje1/OSDOCS-5727

OSDOCS-5727

Author: jeana-redhat

adding_service_cluster/adding-service.adoc

@@ -14,7 +14,7 @@ cluster by using {cluster-manager-first}.
 
 ifdef::openshift-rosa[]
 == Prerequisites
-* For the Amazon CloudWatch service, you must first install the `cluster-logging-operator` using the `rosa` CLI.
+* For the Amazon CloudWatch service, you must first install the `cluster-logging-operator` using the ROSA CLI (`rosa`).
 endif::[]
 
 include::modules/adding-service-existing.adoc[leveloffset=+1]

adding_service_cluster/rosa-available-services.adoc

@@ -7,7 +7,7 @@ include::_attributes/attributes-openshift-dedicated.adoc[]
 
 You can add services to your existing {product-title} (ROSA) cluster using the xref:../adding_service_cluster/adding-service.adoc#adding-service[{cluster-manager-first} console].
 
-These services can also be installed xref:../rosa_cli/rosa-manage-objects-cli.adoc#rosa-managing-objects-cli[using the `rosa` CLI].
+These services can also be installed xref:../rosa_cli/rosa-manage-objects-cli.adoc#rosa-managing-objects-cli[using the ROSA CLI (`rosa`)].
 
 
 include::modules/aws-cloudwatch.adoc[leveloffset=+1]

modules/automatic-network-verification-bypassing.adoc

@@ -24,7 +24,7 @@ endif::openshift-rosa[]
 When you install a cluster into an existing VPC by using {cluster-manager-first}, you can bypass the automatic verification by selecting *Bypass network verification* on the *Virtual Private Cloud (VPC) subnet settings* page.
 
 ifdef::openshift-rosa[]
-.Bypassing automatic network verification by using the ROSA CLI
+.Bypassing automatic network verification by using the ROSA CLI (`rosa`)
 
 When you install a cluster into an existing VPC by using the `rosa create cluster` command, you can bypass the automatic verification by including the `--bypass-network-verify --force` arguments. The following example bypasses the network verification before creating a cluster:
 

modules/aws-cloudwatch.adoc

@@ -6,4 +6,4 @@
 
 = Amazon CloudWatch
 
-Amazon CloudWatch forwards logs from {product-title} (ROSA) to the AWS console for viewing. You must first install the ROSA `cluster-logging-operator` using the `rosa` CLI before installing the Amazon CloudWatch service through {cluster-manager-first} console.
+Amazon CloudWatch forwards logs from {product-title} (ROSA) to the AWS console for viewing. You must first install the ROSA `cluster-logging-operator` using the ROSA CLI (`rosa`) before installing the Amazon CloudWatch service through {cluster-manager-first} console.

modules/configmap-removing-ca.adoc

@@ -6,12 +6,12 @@
 [id="configmap-removing-ca_{context}"]
 = Removing certificate authorities on a {product-title} cluster
 
-You can remove certificate authorities (CA) from your cluster with the `rosa` CLI tool.
+You can remove certificate authorities (CA) from your cluster with the {product-title} (ROSA) CLI, `rosa`.
 
 .Prerequisites
 
 * You must have cluster administrator privileges.
-* You have installed the `rosa` CLI tool.
+* You have installed the ROSA CLI (`rosa`).
 * Your cluster has certificate authorities added.
 
 .Procedure

modules/creating-a-machine-pool-cli.adoc

@@ -10,8 +10,8 @@ You can create additional machine pools for your {product-title} (ROSA) cluster
 
 .Prerequisites
 
-* You installed and configured the latest AWS (`aws`), ROSA (`rosa`), and OpenShift (`oc`) CLIs on your workstation.
-* You logged in to your Red Hat account by using the `rosa` CLI.
+* You installed and configured the latest {product-title} (ROSA) CLI, `rosa`, on your workstation.
+* You logged in to your Red Hat account using the ROSA CLI (`rosa`).
 * You created a ROSA cluster.
 
 .Procedure

modules/creating-a-machine-pool.adoc

@@ -5,4 +5,5 @@
 :_content-type: CONCEPT
 [id="creating_a_machine_pool_{context}"]
 = Creating a machine pool
+
 A default machine pool is created when you install a {product-title} (ROSA) cluster. After installation, you can create additional machine pools for your cluster by using {cluster-manager} or the ROSA CLI (`rosa`).

modules/nw-rosa-proxy-remove-cli.adoc

@@ -6,12 +6,12 @@
 [id="nw-rosa-proxy-remove-cli_{context}"]
 = Removing the cluster-wide proxy using CLI
 
-You must use the `rosa` CLI to remove the proxy's address from your cluster.
+You must use the {product-title} (ROSA) CLI, `rosa`, to remove the proxy's address from your cluster.
 
 .Prerequisites
 
 * You must have cluster administrator privileges.
-* You have installed the {product-title} `rosa` CLI tool.
+* You have installed the ROSA CLI (`rosa`).
 
 .Procedure
 

modules/rosa-about.adoc

@@ -6,7 +6,7 @@
 
 :_content-type: CONCEPT
 [id="rosa-about_{context}"]
-= About the rosa CLI
+= About the {product-title} (ROSA) CLI, `rosa`
 
 
 Use the `rosa` command-line utility for {product-title} (ROSA) to create, update, manage, and delete {product-title} clusters and resources.

modules/rosa-accessing-your-cluster.adoc

@@ -54,7 +54,7 @@ Any optional fields can be left empty and a default will be selected.
 +
 [NOTE]
 ====
-The fields in the *Register a new OAuth application* GitHub form are automatically filled with the required values through the URL that is defined by the `rosa` CLI tool.
+The fields in the *Register a new OAuth application* GitHub form are automatically filled with the required values through the URL that is defined by the {product-title} (ROSA) CLI, `rosa`.
 ====
 .. Use the information from the GitHub application you created and continue the prompts. Enter the following values:
 +