vaile

Author: rachel-mack

source/monitoring.txt

@@ -28,8 +28,7 @@ In this guide you will learn how to perform these tasks:
 - :ref:`Monitor connection pool events with Java Management Extensions (JMX) and JConsole <monitoring-jmx>`
 
 This guide shows how to use information about the meta activity of the driver.
-If you would like to learn how to record data transactions, consider reading
-our :ref:`Monitoring Data Changes <kotlin-sync-change-streams>` page. 
+To learn how to record data transactions, see the :ref:`Monitoring Data Changes <kotlin-sync-change-streams>` page. 
 
 .. _monitoring-monitor-events:
 
@@ -190,7 +189,7 @@ Connection Pool Events
 A connection pool event is an event related to a **connection pool** held by the driver.
 A connection pool is a set of open TCP connections your driver maintains with
 a MongoDB instance. Connection pools help reduce the number of network handshakes
-your application needs to perform with a MongoDB instance, and can help your
+your application performs with a MongoDB instance, and can help your
 application run faster.
 
 To monitor connection pool events, write a class that implements the
@@ -367,7 +366,7 @@ application, use
 include MongoDB event data in the
 `Zipkin <https://zipkin.io/>`__ distributed tracing system.
 
-If you do not use Spring Cloud or need to include driver event data in a distributed
+If you do not use Spring Cloud or want to include driver event data in a distributed
 tracing system other than Zipkin, you must write a command event listener that
 manages `spans <https://docs.spring.io/spring-cloud-sleuth/docs/current-SNAPSHOT/reference/html/getting-started.html#getting-started-terminology>`__
 for your desired distributed tracing system. To see an implementation of such a