[DOC] OSSM-5357 Openshift Userworkload Monitoring integration documentation bug

Author: gwynnemonahan

modules/ossm-integrating-with-user-workload-monitoring.adoc

@@ -56,6 +56,7 @@ spec:
   external_services:
     istio:
       url_service_version: 'http://istiod-basic.istio-system:15014/version'
+      config_map_name: istio-basic # <1>
     prometheus:
       auth:
         token: secret:thanos-querier-web-token:token
@@ -68,6 +69,7 @@ spec:
       url: https://thanos-querier.openshift-monitoring.svc.cluster.local:9091
   version: v1.65
 ----
+<1> Set the `ServiceMeshControlPlane` name prefixed with `istio-`.
 
 . Configure the SMCP for external Prometheus:
 +
@@ -158,7 +160,7 @@ spec:
       replacement: "basic-istio-system" # <2>
       targetLabel: mesh_id
 ----
-<1> Since {product-title} monitoring ignores the `namespaceSelector` spec in `ServiceMonitor` and `PodMonitor` objects, you must apply the `PodMonitor` object in all mesh namespaces, including the control plane namespace.
+<1> Create  this `ServiceMonitor` object in the Istio control plane namespace because it monitors the Istiod service. In this example, the namespace is `istio-system`.
 <2> The string `"basic-istio-system"` is a combination of the SMCP name and its namespace, but any label can be used as long as it is unique for every mesh using user workload monitoring in the cluster. The `spec.prometheus.query_scope` of the Kiali resource configured in Step 2 needs to match this value.
 +
 [NOTE]