Update mongodb-opentelemetry.md

Author: JV0812

docs/integrations/databases/opentelemetry/mongodb-opentelemetry.md

@@ -33,7 +33,7 @@ Following are the [Fields](/docs/manage/fields/) which will be created as part o
 
 - **`db.cluster.name`**. User configured. Enter a name to identify this MongoDb cluster. This cluster name will be shown in the Sumo Logic dashboards.
 - **`db.system`**. Has fixed value of **mongodb**.
-- **`deployment.environment`**. User configured. This is the deployment environment where the Mongodb cluster resides. For example: dev, prod or qa.
+- **`deployment.environment`**. User configured. This is the deployment environment where the Mongodb cluster resides. For example: dev, prod, or qa.
 - **`sumo.datasource`**. has a fixed value of **mongodb**.
 * **`db.node.name`**. Has the value of host name of the machine which is being monitored.
 
@@ -242,7 +242,7 @@ deployment.environment=* db.cluster.name=* sumo.datasource=mongodb  | json "log
 | count by component
 ```
 
-## Viewing MongoDB dashboards
+## Viewing the MongoDB dashboards
 
 import ViewDashboards from '../../../reuse/apps/view-dashboards.md';
 
@@ -262,11 +262,7 @@ Use this dashboard to:
 
 ### Errors and Warnings
 
-The **MongoDB - Errors and Warnings** dashboard shows errors and warnings by the MongoDB component.
-
-Use this dashboard to:
-
-- Determine components producing multiple errors or warnings.
+The **MongoDB - Errors and Warnings** dashboard shows errors and warnings by the MongoDB component. Use this dashboard to determine the components producing multiple errors or warnings.
 
 <img src='https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/MongoDB-OpenTelemetry/MongoDB-Errors-and-Warnings.png' alt="Access" />
 
@@ -356,14 +352,14 @@ import CreateMonitors from '../../../reuse/apps/create-monitors.md';
 | Name | Description | Alert Condition | Recover Condition |
 |:--|:--|:--|:--|
 | `MongoDB - Instance Down` | This alert is triggered when we detect that the MongoDB instance is down. | Missing Data | Data Found |
-| `MongoDB - Replication Error` | This alert is triggered when we detect errors in MongoDB replication operations. | Count `>` 0 | Count `<=` 0 |
-| `MongoDB - Replication Heartbeat Error` | This alert is triggered when we detect that the MongoDB Replication Heartbeat request has errors, which indicates replication is not working as expected. | Count `>` 0 | Count `<=` 0 |
-| `MongoDB - Secondary Node Replication Failure` | This alert is triggered when we detect that a MongoDB secondary node is out of sync for replication. | Count `>` 0 | Count `<=` 0 |
-| `MongoDB - Sharding Balancer Failure` | This alert is triggered when we detect that data balancing failed on a MongoDB Cluster with 1 mongos instance and 3 mongod instances. | Count `>` 0 | Count `<=` 0 |
-| `MongoDB - Sharding Chunk Split Failure` | This alert is triggered when we detect that a MongoDB chunk not been split during sharding. | Count `>` 0 | Count `<=` 0 |
-| `MongoDB - Sharding Error` | This alert is triggered when we detect errors in MongoDB sharding operations. | Count `>` 0 | Count `<=` 0 |
-| `MongoDB - Sharding Warning` | This alert is triggered when we detect warnings in MongoDB sharding operations. | Count `>` 0 | Count `<=` 0 |
-| `MongoDB - Slow Queries` | This alert is triggered when we detect that a MongoDB cluster is executing slow queries. | Count `>` 0 | Count `<=` 0 |
-| `MongoDB - Too Many Connections` | This alert is triggered when we detect a given MongoDB server has too many connections (over 80% of capacity). | Count `>=` 80 | Count `<` 80 |
-| `MongoDB - Too Many Cursors Open` | This alert is triggered when we detect that there are too many cursors (>10K) opened by MongoDB. | Count `>=` 10000 | Count `<` 10000 |
-| `MongoDB - Too Many Cursors Timeouts` | This alert is triggered when we detect that there are too many cursors (100) timing out on a MongoDB server within a 5 minute time interval. | Count `>=` 100 | Count `<` 100 |
+| `MongoDB - Replication Error` | This alert is triggered when we detect errors in MongoDB replication operations. | Count > 0 | Count < = 0 |
+| `MongoDB - Replication Heartbeat Error` | This alert is triggered when we detect that the MongoDB Replication Heartbeat request has errors, which indicates replication is not working as expected. | Count > 0 | Count < = 0 |
+| `MongoDB - Secondary Node Replication Failure` | This alert is triggered when we detect that a MongoDB secondary node is out of sync for replication. | Count > 0 | Count < = 0 |
+| `MongoDB - Sharding Balancer Failure` | This alert is triggered when we detect that data balancing failed on a MongoDB Cluster with 1 mongos instance and 3 mongod instances. | Count > 0 | Count < = 0 |
+| `MongoDB - Sharding Chunk Split Failure` | This alert is triggered when we detect that a MongoDB chunk not been split during sharding. | Count > 0 | Count < = 0 |
+| `MongoDB - Sharding Error` | This alert is triggered when we detect errors in MongoDB sharding operations. | Count > 0 | Count < = 0 |
+| `MongoDB - Sharding Warning` | This alert is triggered when we detect warnings in MongoDB sharding operations. | Count > 0 | Count < = 0 |
+| `MongoDB - Slow Queries` | This alert is triggered when we detect that a MongoDB cluster is executing slow queries. | Count > 0 | Count < = 0 |
+| `MongoDB - Too Many Connections` | This alert is triggered when we detect a given MongoDB server has too many connections (over 80% of capacity). | Count > = 80% | Count < 80% |
+| `MongoDB - Too Many Cursors Open` | This alert is triggered when we detect that there are too many cursors (>10K) opened by MongoDB. | Count > = 10000 | Count < 10000 |
+| `MongoDB - Too Many Cursors Timeouts` | This alert is triggered when we detect that there are too many cursors (100) timing out on a MongoDB server within a 5 minute time interval. | Count > = 100 | Count < 100 |