NR feedback

Author: mcmorisi

source/includes/monitoring/monitoring.py

@@ -8,19 +8,19 @@ class MyCommandListener(CommandListener):
     def succeeded(self, event: CommandSucceededEvent):
         print(f"Command {event.command_name} succeeded")
 
-    # Other event method implementations here
+    # Include other event method implementations here
 
 class MyServerListener(ServerListener):
     def heartbeat_started(self, event: ServerHeartbeatStartedEvent):
         print(f"Heartbeat started on server with id: {event.connection_id}")
 
-    # Other event method implementations here
+    # Include other event method implementations here
 
 class MyPoolListener(ConnectionPoolListener):
     def connection_created(self, event: ConnectionCreatedEvent):
         print(f"Connection {event.connection_id} created")
 
-    # Other event method implementations here
+    # Include other event method implementations here
 
 listeners = [MyCommandListener(), MyServerListener(), MyPoolListener()]
 client = MongoClient("<connection URI>", event_listeners=listeners)

source/monitoring.txt

@@ -31,7 +31,7 @@ listen for driver events to monitor your application.
 .. note:: Event Logging
 
    This page explains how to monitor your application in code. To learn how to record
-   this information to an external log, see :ref:`Logging. <pymongo-logging>`
+   this information to an external log, see the :ref:`pymongo-logging` guide.
 
 Event Types
 -----------
@@ -45,9 +45,9 @@ The following table describes the types of events that the driver emits:
 
    * - Event Type
      - Description
-   * - Command Events
+   * - Command events
      - Events related to MongoDB database commands, such as ``find``, ``insert``,
-       ``delete``, and ``count``. To learn how to use the {+driver-short+} to run a
+       ``delete``, and ``count``. To learn how to use {+driver-short+} to run a
        database command, see :ref:`<pymongo-run-command>`. For more information about
        MongoDB database commands, see :manual:`Database Commands </reference/command/>`
        in the {+mdb-server+} manual.
@@ -56,10 +56,10 @@ The following table describes the types of events that the driver emits:
        command events. This protects the sensitive information contained in these command
        events.
 
-   * - Server Discovery and Monitoring (SDAM) Events
+   * - Server Discovery and Monitoring (SDAM) events
      - Events related to changes in the state of the MongoDB deployment.
 
-   * - Connection Pool Events
+   * - Connection Pool events
      - Events related to the connection pool held by the driver.
 
 For a complete list of events the driver emits, see the
@@ -69,7 +69,7 @@ Listening for Events
 --------------------
 
 To monitor an event, you must pass an event listener to your application's ``MongoClient``.
-The following steps describe how to monitor your application using an event listener:
+The following steps describe how to monitor your application by using an event listener:
 
 1. Create a class that inherits from one of the event listener base classes
    provided by {+driver-short+}. The base class you choose depends on the type of event
@@ -94,5 +94,5 @@ API Documentation
 To learn more about the methods and classes used to monitor events in the driver, see the
 following API documentation:
 
-- `pymongo.monitoring <{+api-root+}pymongo/monitoring.html>`__
+- `monitoring <{+api-root+}pymongo/monitoring.html>`__
 - `MongoClient <{+api-root+}pymongo/mongo_client.html#pymongo.mongo_client.MongoClient>`__