OBSDOCS-1800: Small fixes for 'Enabling a separate Alertmanager instance for user-defined alert routing'

Author: eromanova97

modules/monitoring-enabling-a-separate-alertmanager-instance-for-user-defined-alert-routing.adoc

@@ -24,7 +24,7 @@ ifndef::openshift-rosa,openshift-dedicated[]
 * You have access to the cluster as a user with the `cluster-admin` cluster role.
 * You have enabled monitoring for user-defined projects.
 endif::[]
-* You have installed the OpenShift CLI (`oc`).
+* You have installed the {oc-first}.
 
 .Procedure
 
@@ -47,8 +47,8 @@ metadata:
 data:
   config.yaml: |
     alertmanager:
-      enabled: true <1>
-      enableAlertmanagerConfig: true <2>
+      enabled: true # <1>
+      enableAlertmanagerConfig: true # <2>
 ----
 <1> Set the `enabled` value to `true` to enable a dedicated instance of the Alertmanager for user-defined projects in a cluster. Set the value to `false` or omit the key entirely to disable the Alertmanager for user-defined projects.
 If you set this value to `false` or if the key is omitted, user-defined alerts are routed to the default platform Alertmanager instance.
@@ -63,7 +63,7 @@ ifndef::openshift-dedicated,openshift-rosa[]
 +
 [source,terminal]
 ----
-# oc -n openshift-user-workload-monitoring get alertmanager
+$ oc -n openshift-user-workload-monitoring get alertmanager
 ----
 +
 .Example output
@@ -81,7 +81,7 @@ ifdef::openshift-dedicated,openshift-rosa[]
 +
 [source,terminal]
 ----
-# oc -n openshift-user-workload-monitoring get pods
+$ oc -n openshift-user-workload-monitoring get pods
 ----
 +
 .Example output