Merge pull request #91919 from bergerhoffer/updating-cli

Sweep to update 'command line tool/interface' to 'command-line tool/i…

Author: bergerhoffer

_unused_topics/pod-using-a-different-service-account.adoc

@@ -9,7 +9,7 @@ You can run a pod with a service account other than the default:
 
 .Prerequisites
 
-* Install the `oc` command line interface.
+* Install the `oc` command-line interface.
 * Configure a service account.
 * Create a DeploymentConfig.
 

applications/index.adoc

@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-Using {product-title}, you can create, edit, delete, and manage applications using the web console or command line interface (CLI).
+Using {product-title}, you can create, edit, delete, and manage applications using the web console or command-line interface (CLI).
 
 [id="working-on-a-project"]
 == Working on a project

backup_and_restore/application_backup_and_restore/aws-sts/oadp-aws-sts.adoc

@@ -14,7 +14,7 @@ You configure {aws-short} for Velero, create a default `Secret`, and then instal
 
 To install the OADP Operator in a restricted network environment, you must first disable the default OperatorHub sources and mirror the Operator catalog. See xref:../../../disconnected/using-olm.adoc#olm-restricted-networks[Using Operator Lifecycle Manager in disconnected environments] for details.
 
-You can install {oadp-short} on an AWS {sts-first} (AWS STS) cluster manually. Amazon {aws-short} provides {aws-short} STS as a web service that enables you to request temporary, limited-privilege credentials for users. You use STS to provide trusted users with temporary access to resources via API calls, your {aws-short} console, or the {aws-short} command line interface (CLI).
+You can install {oadp-short} on an AWS {sts-first} (AWS STS) cluster manually. Amazon {aws-short} provides {aws-short} STS as a web service that enables you to request temporary, limited-privilege credentials for users. You use STS to provide trusted users with temporary access to resources via API calls, your {aws-short} console, or the {aws-short} command-line interface (CLI).
 
 Before installing {oadp-first}, you must set up role and policy credentials for {oadp-short} so that it can use the {aws-full} API.
 

cicd/jenkins/images-other-jenkins-agent.adoc

@@ -12,7 +12,7 @@ The Base image for Jenkins agents does the following:
 
 * Pulls in both the required tools, headless Java, the Jenkins JNLP client, and the useful ones, including `git`, `tar`, `zip`, and `nss`, among others.
 * Establishes the JNLP agent as the entry point.
-* Includes the `oc` client tool for invoking command line operations from within Jenkins jobs.
+* Includes the `oc` client tool for invoking command-line operations from within Jenkins jobs.
 * Provides Dockerfiles for both Red Hat Enterprise Linux (RHEL) and `localdev` images.
 
 [IMPORTANT]

cli_reference/rosa_cli/rosa-cli-permission-examples.adoc

@@ -5,7 +5,7 @@ include::_attributes/attributes-openshift-dedicated.adoc[]
 :context: rosa-cli-permission-examples
 toc::[]
 
-You can create roles with permissions that adhere to the principal of least privilege, in which the users assigned the roles have no other permissions assigned to them outside the scope of the specific action they need to perform. These policies contain only the minimum required permissions needed to perform specific actions by using the {product-title} (ROSA) command line interface (CLI).
+You can create roles with permissions that adhere to the principal of least privilege, in which the users assigned the roles have no other permissions assigned to them outside the scope of the specific action they need to perform. These policies contain only the minimum required permissions needed to perform specific actions by using the {product-title} (ROSA) command-line interface (CLI).
 
 [IMPORTANT]
 ====

cloud_experts_tutorials/cloud-experts-deploying-application/cloud-experts-deploying-application-integrating-aws.adoc

@@ -78,7 +78,7 @@ image:cloud-experts-deployment-integrating-ack-install.png[]
 
 . Run one of the following scripts to create the AWS IAM role for the ACK controller and assign the S3 policy:
 ** Automatically download the link:https://www.rosaworkshop.io/ostoy/resources/setup-s3-ack-controller.sh[setup-s3-ack-controller.sh] script, which automates the process for you.
-** Run the following script in your command line interface (CLI):
+** Run the following script in your command-line interface (CLI):
 +
 [source,terminal]
 ----

cloud_experts_tutorials/cloud-experts-deploying-application/cloud-experts-deploying-application-logging.adoc

@@ -111,7 +111,7 @@ image:cloud-experts-deploying-application-logging-ostoy-stdout.png[]
 image:cloud-experts-deploying-application-logging-ostoy-stderr.png[]
 
 == Viewing the application logs by using the `oc` command
-. Enter the following command in the command line interface (CLI) to retrieve the name of your frontend pod:
+. Enter the following command in the command-line interface (CLI) to retrieve the name of your frontend pod:
 +
 [source,terminal]
 ----

cloud_experts_tutorials/cloud-experts-deploying-application/cloud-experts-deploying-application-s2i-deployments.adoc

@@ -25,7 +25,7 @@ image::ostoy-cli-login.png[CLI Login]
 +
 .. Copy the command under "Log in with this token".
 +
-.. Log in to the command line interface (CLI) by running the copied command in your terminal. You should see something similar to the following:
+.. Log in to the command-line interface (CLI) by running the copied command in your terminal. You should see something similar to the following:
 +
 [source,terminal]
 ----

cloud_experts_tutorials/cloud-experts-getting-started/cloud-experts-getting-started-accessing.adoc

@@ -9,7 +9,7 @@ toc::[]
 //rosaworkshop.io content metadata
 //Brought into ROSA product docs 2023-11-30
 
-You can connect to your cluster using the command line interface (CLI) or the {hybrid-console} user interface (UI).
+You can connect to your cluster using the command-line interface (CLI) or the {hybrid-console} user interface (UI).
 
 == Accessing your cluster using the CLI
 

cloud_experts_tutorials/cloud-experts-getting-started/cloud-experts-getting-started-admin-rights.adoc

@@ -9,7 +9,7 @@ toc::[]
 //rosaworkshop.io content metadata
 //Brought into ROSA product docs 2023-11-30
 
-Administration (admin) privileges are not automatically granted to users that you add to your cluster. If you want to grant admin-level privileges to certain users, you will need to manually grant them to each user. You can grant admin privileges from either the ROSA command line interface (CLI) or the Red{nbsp}Hat OpenShift Cluster Manager web user interface (UI).
+Administration (admin) privileges are not automatically granted to users that you add to your cluster. If you want to grant admin-level privileges to certain users, you will need to manually grant them to each user. You can grant admin privileges from either the ROSA command-line interface (CLI) or the Red{nbsp}Hat OpenShift Cluster Manager web user interface (UI).
 
 Red{nbsp}Hat offers two types of admin privileges: