Incorporated Lindsey's comments

Author: pabel-rh

modules/observe/proc-admin-enabling-metrics-ocp-operator.adoc

@@ -25,32 +25,33 @@ Currently, the {product} Operator does not support creating a `ServiceMonitor` c
 apiVersion: monitoring.coreos.com/v1
 kind: ServiceMonitor
 metadata:
-  name: developer-hub-service-monitor <1>
-  namespace: {my-product-namespace} <2>
+  name: <developer-hub-service-monitor-name> <1>
+  namespace: <rhdh-namespace-name> <2>
   labels:
     app.kubernetes.io/instance: <rhdh-cr-name> <3>
     app.kubernetes.io/name: {product-custom-resource-type}
 spec:
   namespaceSelector:
     matchNames:
-      - {my-product-namespace} <4>
+      - <rhdh-namespace-name> <4>
   selector:
     matchLabels:
-      app.kubernetes.io/instance: developer-hub <5>
-      app.kubernetes.io/name: {product-custom-resource-type}
+      app.kubernetes.io/instance: <deployment-name> <5>
+      app.kubernetes.io/name: <rhdh-cr-type> <6>
   endpoints:
   - port: http-metrics
     path: '/metrics'
 ----
 <1> The name of your `ServiceMonitor` resource, for example, `developer-hub-service-monitor`.
-<2> The namespace where your `ServiceMonitor` will live.
-<3> The label name identifying the `ServiceMonitor` CR instance.
-<4> The namespace where your {product-very-short} instance is installed.
-<5> The name of your {product-very-short} deployment. 
-[NOTE]
+<2> The namespace where your `ServiceMonitor` will live, for example, `{my-product-namespace}`.
+<3> The label name identifying the `ServiceMonitor` CR instance, for example, `{my-product-cr-name}`.
+<4> The namespace where your {product-very-short} instance is installed, for example, `{my-product-namespace}`.
+<5> The name of your {product-very-short} deployment, for example, `developer-hub`.
+<6> The type of custom resource that you want to use, for example, `{product-custom-resource-type}`.
 +
+[NOTE]
 ====
-`spec.selector.matchLabels` configuration must match the labels of your {product-very-short} installation. To confirm the label names, go to Project > Services and verify the labels for `backstage-developer-hub`.
+`spec.selector.matchLabels` configuration must match the labels of your {product-very-short} installation.
 ==== 
 
 . Apply the `ServiceMonitor` CR by running the following command:
@@ -64,4 +65,4 @@ oc apply -f <filename>
 
 . From the *Developer* perspective in the {ocp-short} web console, select the *Observe* view.
 . Click the *Metrics* tab to view metrics for {product} pods.
-. From the OpenShift Console in the Developer view, click **Project > Services** and verify the labels for `backstage-developer-hub`.
+. From the OpenShift Console in the Developer view, click **Project > Services** and verify the labels for `backstage-developer-hub`.