diff --git a/_attributes/attributes-openshift-dedicated.adoc b/_attributes/attributes-openshift-dedicated.adoc
index 9df2229e772f..413b12f97fd7 100644
--- a/_attributes/attributes-openshift-dedicated.adoc
+++ b/_attributes/attributes-openshift-dedicated.adoc
@@ -61,4 +61,5 @@
 :egress-zero: egress zero
 :egress-zero-title: {product-title} clusters with {egress-zero}
 :classic-short: {rosa-classic-short}
-:rosa-cli-first: pass:quotes[Red Hat OpenShift Service on AWS CLI (`rosa`)]
+:rosa-cli-first: pass:quotes[ROSA command-line interface (CLI) (`rosa`)]
+:rosa-cli: ROSA CLI
\ No newline at end of file
diff --git a/modules/setting-higher-pid-limit-on-existing-cluster.adoc b/modules/setting-higher-pid-limit-on-existing-cluster.adoc
index 39e6b4b0d11a..4be35953c843 100644
--- a/modules/setting-higher-pid-limit-on-existing-cluster.adoc
+++ b/modules/setting-higher-pid-limit-on-existing-cluster.adoc
@@ -16,7 +16,7 @@ Changing the `podPidsLimit` on an existing cluster will trigger non-control plan
 .Prerequisites
 
 * You have a {product-title} cluster.
-* You have installed the ROSA CLI (`rosa`).
+* You have installed the {rosa-cli-first}.
 * You have installed the OpenShift CLI (`oc`).
 * You have logged in to your Red{nbsp}Hat account by using the ROSA CLI.
 
@@ -24,7 +24,7 @@ Changing the `podPidsLimit` on an existing cluster will trigger non-control plan
 . Create or edit the `KubeletConfig` object to change the PID limit.
 +
 --
-** If this is the first time you are changing the default PID limit, create the `KubeletConfig` object and set the `--pod-pids-limit` value by running the following command: 
+** If this is the first time you are changing the default PID limit, create the `KubeletConfig` object and set the `--pod-pids-limit` value by running the following command:
 +
 [source,terminal]
 ----