updated verification for prometheus int

Author: MGoedtel

articles/azure-monitor/insights/container-insights-prometheus-integration.md

@@ -217,7 +217,7 @@ Errors related to applying configuration changes are also available for review.
 
 - From the **KubeMonAgentEvents** table in your Log Analytics workspace. Data is sent every hour with *Warning* severity for scrape errors and *Error* severity for configuration errors. If there are no errors, the entry in the table will have data with severity *Info*, which reports no errors. The **Tags** property contains more information about the pod and container ID on which the error occurred and also the first occurrence, last occurrence, and count in the last hour.
 
-- With Azure Red Hat OpenShift, by checking the omsagent logs in `ContainerLog` table if log collection of openshift-azure-logging is enabled.
+- For Azure Red Hat OpenShift, check the omsagent logs by searching the `ContainerLog` table to verify if log collection of openshift-azure-logging is enabled.
 
 Errors prevent omsagent from parsing the file, causing it to restart and use the default configuration. After you correct the error(s) in ConfigMap on clusters other than Azure Red Hat OpenShift, save the yaml file and apply the updated ConfigMaps by running the command: `kubectl apply -f <configmap_yaml_file.yaml`.