MW PR fixes 1

Author: rustagir

source/monitoring.txt

@@ -12,7 +12,7 @@ Monitor Your Application
 .. /monitoring/command-monitoring
 .. /monitoring/connection-monitoring
 
-- :ref:`Cluster Monitoring <php-cluster-monitoring>`: monitor changes
+- :ref:`Cluster Monitoring <php-cluster-monitoring>`: Monitor changes
   in your cluster configuration
 
 .. TODO - :ref:`Command Monitoring <php-command-monitoring>`: monitor command

source/monitoring/cluster-monitoring.txt

@@ -23,7 +23,7 @@ Overview
 This guide shows you how to use the {+php-library+} to monitor topology
 events in a MongoDB instance, replica set, or sharded cluster. The
 driver creates topology events, also known as Server Discovery and
-Monitoring (**SDAM**) events, when there are any changes in the state of the
+Monitoring (SDAM) events, when there are any changes in the state of the
 MongoDB instance or cluster that you are connected to.
 
 You might use information about topology events in your
@@ -34,14 +34,15 @@ Subscribe to Events
 -------------------
 
 You can access details about SDAM events by subscribing to them
-in your application. To subscribe to any event, create a class that
+in your application. To subscribe to an event, create a class that
 implements the ``MongoDB\Driver\Monitoring\SDAMSubscriber`` interface,
 then use the ``MongoDB\Client::addSubscriber()`` method to register the
 event subscriber with your ``MongoDB\Client`` instance.
 
-The following code creates the ``MySubscriber`` class that implements
-``SDAMSubscriber`` to output a message when a ``ServerOpeningEvent`` is
-generated by the server:
+The following code creates the ``MySubscriber`` class, which implements
+the ``SDAMSubscriber`` interface. The class is defined with a method to
+output a message when a ``ServerOpeningEvent`` is generated by the
+server:
 
 .. literalinclude:: /includes/monitoring/sdam.php
    :start-after: start-mysubscriber
@@ -53,12 +54,12 @@ generated by the server:
 .. note::
 
    As shown in the preceding code, you must implement all of the methods
-   of ``SDAMSubscriber``, even for events you are not subscribing to.
+   of the ``SDAMSubscriber`` interface, even for events you are not subscribing to.
    You can implement these methods with empty bodies so that the library
    does not generate any messages for these events.
 
-Then, the following code uses the ``addSubscriber()`` method to register
-``MySubscriber`` with the client:
+Then, use the ``addSubscriber()`` method to register ``MySubscriber``
+with the client, as shown in the following code:
 
 .. literalinclude:: /includes/monitoring/sdam.php
    :start-after: start-add-sub