reorder/remove steps in Logging topics

modules/cluster-logging-deploy-console.adoc

@@ -18,22 +18,27 @@ You can install the {clo} by using the {product-title} web console.
 . In the {product-title} web console, click *Operators* -> *OperatorHub*.
 . Type `OpenShift Logging` in the *Filter by keyword* box.
 . Choose  *Red Hat OpenShift Logging* from the list of available Operators, and click *Install*.
-. Ensure that *A specific namespace on the cluster* is selected under *Installation mode*.
-. Ensure that *Operator recommended namespace* is *openshift-logging* under *Installed Namespace*.
-. Select *Enable operator recommended cluster monitoring on this namespace*.
+ifdef::openshift-rosa[]
+. In the *role ARN* text field, type "no_role_arn". Although the specific ARN for the cluster is not required, the *role ARN* text field must be populated to continue the installation process.
 +
-This option sets the `openshift.io/cluster-monitoring: "true"` label in the `Namespace` object. You must select this option to ensure that cluster monitoring scrapes the `openshift-logging` namespace.
-
+[NOTE]
+====
+The *role ARN* text field is only applicable for ROSA clusters with STS.
+====
++
+endif::[]
 . Select *stable-5.y* as the *Update channel*.
 +
 --
 include::snippets/logging-stable-updates-snip.adoc[]
 --
-
++
+. Select a *Version*.
+. Ensure that *A specific namespace on the cluster* is selected under *Installation mode*.
+. Ensure that *Operator recommended namespace* is *openshift-logging* under *Installed Namespace*.
 . Select an *Update approval*.
 ** The *Automatic* strategy allows Operator Lifecycle Manager (OLM) to automatically update the Operator when a new version is available.
 ** The *Manual* strategy requires a user with appropriate credentials to approve the Operator update.
-
 . Select *Enable* or *Disable* for the *Console plugin*.
 . Click *Install*.