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._
+Monitoring can be leveraged by users on Red Hat OpenShift Container Platform only. 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] guide. 
+
+_This feature does not support integration with Knative Service and the community edition of Prometheus Operator._
+
+_Prometheus Operator is required to use ServiceMonitor._
 
 ==== 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]
 
 [source,yaml]
 ----
@@ -492,6 +496,8 @@ spec:
         insecureSkipVerify: true
 ----
 
+Runtime Component Operator will not create/update the `ServiceMonitor` if the `basicAuth` secrets are not defined. 
+
 === Knative support
 
 Runtime Component Operator can deploy serverless applications with link:++https://knative.dev/docs/++[Knative] on a Kubernetes cluster. To achieve this, the operator creates a link:++https://github.com/knative/serving/blob/main/docs/spec/spec.md#service++[Knative `Service`] resource which manages the whole life cycle of a workload.