Skip to content

Commit 4f26b7c

Browse files
committed
Fixes
1 parent ec47a6a commit 4f26b7c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

source/monitoring.txt

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -62,21 +62,21 @@ The following table describes the types of events that the driver emits:
6262
* - Connection Pool Events
6363
- Events related to the connection pool held by the driver.
6464

65-
For a copmlete list of events the driver emits, see the
65+
For a complete list of events the driver emits, see the
6666
`pymongo.monitoring <{+api-root+}pymongo/monitoring.html>`__ API documentation.
6767

6868
Listening for Events
6969
--------------------
7070

7171
To monitor an event, you must pass an event listener to your application's ``MongoClient``.
72-
The following steps describe how to create monitor your application using an event listener:
72+
The following steps describe how to monitor your application using an event listener:
7373

7474
1. Create a class that inherits from one of the event listener base classes
7575
provided by {+driver-short+}. The base class you choose depends on the type of event
7676
you want to monitor. For example, to monitor command events, create a class
7777
that inherits from ``CommandListener``.
7878
#. Implement the methods of the base class that correpond to the events you want to monitor.
79-
#. Pass an instance of your class to the ``MongoClient`` constructor.
79+
#. Pass an instance of your listener class to the ``MongoClient`` constructor.
8080

8181
The following code implements a ``CommandListener`` to listen for command events, a
8282
``ServerListener`` to listen for SDAM events, and a ``ConnectionPoolListener`` to listen for

0 commit comments

Comments
 (0)