Update user-guide-v1beta2.adoc

Author: kabicin

doc/user-guide-v1beta2.adoc

@@ -445,7 +445,11 @@ Once a `RuntimeComponent` application is exposed as a Provisioned Service, a ser
 
 Runtime Component Operator can create a `ServiceMonitor` resource to integrate with `Prometheus Operator`.
 
-_This feature does not support integration with Knative Service. Prometheus Operator is required to use ServiceMonitor._
+**For users on Red Hat OpenShift Container Platform v4.6+**. Before using the feature, you must install `Prometheus Operator` by following our link:++https://github.com/OpenLiberty/open-liberty-operator/blob/main/doc/openshift-monitoring.adoc#application-monitoring-on-rhocp-46++[Application Monitoring on RHOCP 4.6+] guide. Configure the `RuntimeComponent` CR instance with the basic or advanced monitoring specification below, then view Prometheus Metrics through the OpenShift UI as "Administrator" under the `Observe` > `Metrics` tab. 
+
+_The community version of Prometheus Operator is not supported for users on Red Hat OpenShift Container Platform._ 
+
+_This feature does not support integration with Knative Service._
 
 ==== Basic monitoring specification
 
@@ -466,7 +470,7 @@ spec:
 
 ==== Advanced monitoring specification
 
-For advanced scenarios, it is possible to set many `ServicerMonitor` settings such as authentication secret using link:++https://github.com/coreos/prometheus-operator/blob/main/Documentation/api.md#endpoint++[Prometheus Endpoint]
+For advanced scenarios, it is possible to set many `ServiceMonitor` settings such as authentication secret using link:++https://github.com/coreos/prometheus-operator/blob/main/Documentation/api.md#endpoint++[Prometheus Endpoint]. Ensure that the `basicAuth` secrets (i.e. `metrics-secret`) are created and visible to Runtime Component Operator. 
 
 [source,yaml]
 ----