Merge pull request #69680 from abrennan89/OBSDOCS603

OBSDOCS-603: Update attributes in upgrading docs

Author: abrennan89

logging/cluster-logging-upgrading.adoc

@@ -1,8 +1,8 @@
 :_mod-docs-content-type: ASSEMBLY
 :context: cluster-logging-upgrading
+include::_attributes/common-attributes.adoc[]
 [id="cluster-logging-upgrading"]
 = Updating Logging
-include::_attributes/common-attributes.adoc[]
 
 toc::[]
 

modules/cluster-logging-upgrading-elasticsearch.adoc

@@ -3,19 +3,19 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="cluster-logging-upgrading-elasticsearch_{context}"]
-= Updating the OpenShift Elasticsearch Operator
+= Updating the {es-op}
 
-To update the OpenShift Elasticsearch Operator to the current version, you must modify the subscription.
+To update the {es-op} to the current version, you must modify the subscription.
 
 include::snippets/logging-elastic-dep-snip.adoc[]
 
 .Prerequisites
 
-* If you are using Elasticsearch as the default log store, and Kibana as the UI, update the OpenShift Elasticsearch Operator before you update the Cluster Logging Operator.
+* If you are using Elasticsearch as the default log store, and Kibana as the UI, update the {es-op} before you update the {clo}.
 +
 [IMPORTANT]
 ====
-If you update the Operators in the wrong order, Kibana does not update and the Kibana custom resource (CR) is not created. To fix this issue, delete the Red Hat OpenShift Logging Operator pod. When the Red Hat OpenShift Logging Operator pod redeploys, it creates the Kibana CR and Kibana becomes available again.
+If you update the Operators in the wrong order, Kibana does not update and the Kibana custom resource (CR) is not created. To fix this issue, delete the {clo} pod. When the {clo} pod redeploys, it creates the Kibana CR and Kibana becomes available again.
 ====
 
 * The Logging status is healthy:
@@ -43,7 +43,7 @@ endif::[]
 
 . In the *Change Subscription Update Channel* window, select *stable-5.y* and click *Save*. Note the `elasticsearch-operator.v5.y.z` version.
 
-. Wait for a few seconds, then click *Operators* -> *Installed Operators*. Verify that the OpenShift Elasticsearch Operator version matches the latest `elasticsearch-operator.v5.y.z` version.
+. Wait for a few seconds, then click *Operators* -> *Installed Operators*. Verify that the {es-op} version matches the latest `elasticsearch-operator.v5.y.z` version.
 
 . On the *Operators* -> *Installed Operators* page, wait for the *Status* field to report *Succeeded*.
 

modules/logging-operator-upgrading-all-ns.adoc

@@ -4,10 +4,10 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="logging-operator-upgrading-all-ns_{context}"]
-= Upgrading the Cluster Logging Operator to watch all namespaces
+= Upgrading the {clo} to watch all namespaces
 
-In logging 5.7 and older versions, the Cluster Logging Operator only watches the `openshift-logging` namespace.
-If you want the Cluster Logging Operator to watch all namespaces on your cluster, you must redeploy the Operator. You can complete the following procedure to redeploy the Operator without deleting your logging components.
+In logging 5.7 and older versions, the {clo} only watches the `openshift-logging` namespace.
+If you want the {clo} to watch all namespaces on your cluster, you must redeploy the Operator. You can complete the following procedure to redeploy the Operator without deleting your logging components.
 
 .Prerequisites
 
@@ -37,7 +37,7 @@ $ oc -n openshift-logging delete operatorgroup <operator_group_name>
 $ oc delete clusterserviceversion cluster-logging.<version>
 ----
 
-. Redeploy the Cluster Logging Operator by following the "Installing Logging" documentation.
+. Redeploy the {clo} by following the "Installing Logging" documentation.
 
 .Verification
 

modules/logging-upgrading-clo.adoc

@@ -4,13 +4,13 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="logging-upgrading-clo_{context}"]
-= Updating the Cluster Logging Operator
+= Updating the {clo}
 
-To update the Cluster Logging Operator to a new major release version, you must modify the update channel for the Operator subscription.
+To update the {clo} to a new major release version, you must modify the update channel for the Operator subscription.
 
 .Prerequisites
 
-* You have installed the Red Hat OpenShift Logging Operator.
+* You have installed the {clo}.
 * You have administrator permissions.
 * You have access to the {product-title} web console and are viewing the *Administrator* perspective.
 
@@ -28,6 +28,6 @@ To update the Cluster Logging Operator to a new major release version, you must
 
 .Verification
 
-. Wait for a few seconds, then click *Operators* -> *Installed Operators*. Verify that the Red Hat OpenShift Logging Operator version matches the latest `cluster-logging.v5.y.z` version.
+. Wait for a few seconds, then click *Operators* -> *Installed Operators*. Verify that the {clo} version matches the latest `cluster-logging.v5.y.z` version.
 
 . On the *Operators* -> *Installed Operators* page, wait for the *Status* field to report *Succeeded*.

modules/logging-upgrading-loki.adoc

@@ -4,13 +4,13 @@
 
 :_mod-docs-content-type: PROCEDURE
 [id="logging-upgrading-loki_{context}"]
-= Updating the Loki Operator
+= Updating the {loki-op}
 
-To update the Loki Operator to a new major release version, you must modify the update channel for the Operator subscription.
+To update the {loki-op} to a new major release version, you must modify the update channel for the Operator subscription.
 
 .Prerequisites
 
-* You have installed the Loki Operator.
+* You have installed the {loki-op}.
 * You have administrator permissions.
 * You have access to the {product-title} web console and are viewing the *Administrator* perspective.
 
@@ -28,6 +28,6 @@ To update the Loki Operator to a new major release version, you must modify the
 
 .Verification
 
-. Wait for a few seconds, then click *Operators* -> *Installed Operators*. Verify that the Loki Operator version matches the latest `loki-operator.v5.y.z` version.
+. Wait for a few seconds, then click *Operators* -> *Installed Operators*. Verify that the {loki-op} version matches the latest `loki-operator.v5.y.z` version.
 
 . On the *Operators* -> *Installed Operators* page, wait for the *Status* field to report *Succeeded*.