code edits

Author: lindseymoore

source/includes/fundamentals/code-snippets/Monitoring.java

@@ -42,7 +42,7 @@ private void monitorCommandEvent() {
         MongoClient mongoClient = MongoClients.create(settings);
         MongoDatabase database = mongoClient.getDatabase(DATABASE);
         MongoCollection<Document> collection = database.getCollection(COLLECTION);
-        // Run some commands to test the timer
+        // Runs sample find() commands to test the timer
         collection.find().first();
         collection.find().first();
         mongoClient.close();
@@ -61,7 +61,7 @@ private void monitorClusterEvent() {
         MongoClient mongoClient = MongoClients.create(settings);
         MongoDatabase database = mongoClient.getDatabase(DATABASE);
         MongoCollection<Document> collection = database.getCollection(COLLECTION);
-        // Run a command to trigger a ClusterDescriptionChangedEvent event
+        // Runs a sample find() command to trigger a ClusterDescriptionChangedEvent event
         collection.find().first();
         // end monitor-cluster-example
         mongoClient.close();
@@ -79,7 +79,7 @@ private void monitorConnectionPoolEvent() {
         MongoClient mongoClient = MongoClients.create(settings);
         MongoDatabase database = mongoClient.getDatabase(DATABASE);
         MongoCollection<Document> collection = database.getCollection(COLLECTION);
-        // Run a command to trigger connection pool events
+        // Runs a sample find() command to trigger connection pool events
         collection.find().first();
         // end monitor-cp-example
         /* We do not close this connection in order to prevent the driver from requesting two connections, giving

source/logging-monitoring/monitoring.txt

@@ -58,10 +58,8 @@ The MongoDB Java driver organizes the events it defines into three categories:
 
 The following sections show how to monitor each event category.
 
-To learn more about the events you can monitor, `see the event package of the 
-MongoDB Java Driver <{+api+}/apidocs/mongodb-driver-core/com/mongodb/event/package-summary.html>`__.
-
-.. fix this link text^
+To learn more about the events you can monitor, see the API documentation for `event classes 
+<{+api+}/apidocs/mongodb-driver-core/com/mongodb/event/package-summary.html>`__.
 
 .. _command-events-java:
 
@@ -78,9 +76,7 @@ To monitor command events, write a class that implements the
 
 To learn more about MongoDB database commands, see the
 :manual:`MongoDB manual entry on database commands </reference/command/>` in the
-Server (or MongoDB?) Manual.
-
-.. fix this link ^
+Server Manual.
 
 .. note:: Internal Commands
 
@@ -94,9 +90,8 @@ Server (or MongoDB?) Manual.
    As a security measure, the driver redacts the contents of some command events. This
    protects the sensitive information contained in these command events. For a
    full list of redacted command events, see the
-   :spec:`MongoDB command logging and monitoring specification </command-logging-and-monitoring/command-logging-and-monitoring.rst#security>`.
-
-.. ^fix this link
+   :spec:`MongoDB command logging and monitoring specification </command-logging-and-monitoring/command-logging-and-monitoring.md#security>`
+   in GitHub.
 
 Example
 ^^^^^^^
@@ -236,7 +231,6 @@ application run faster.
 .. Add when page is ready: To learn more about connection pools, see the {+driver-short+}'s 
 .. :ref:`Connection Pools <connection-pools>` guide. 
 
-
 To monitor connection pool events, write a class that implements the
 ``ConnectionPoolListener`` interface and register an instance of that class with your
 ``MongoClient`` instance.