DOCS-162: minor edits

Author: Bob Grabar

draft/reference/current-op.txt

@@ -8,11 +8,11 @@ Current Operation Reporting
 
 The :method:`db.currentOp()` helper in the :program:`mongo` shell
 reports on the current operations running on the :program:`mongod`
-instance. The command returns the ``inprog`` array, that contains a
+instance. The command returns the ``inprog`` array, which contains a
 document for each in progress operation. Consider the following
 example output:
 
-.. code-block::
+.. code-block:: javascript
 
    {
      "inprog": [
@@ -63,7 +63,7 @@ example output:
 
       db.currentOp(true)
 
-   Furthermore, active operations (i.e. where :data:`active` are
+   Furthermore, active operations (i.e. where :data:`active` is
    ``true``) will return additional fields.
 
 Output Reference
@@ -72,17 +72,17 @@ Output Reference
 .. data:: opid
 
    Holds an identifier for the operation. You can pass this value to
-   :method:`db.killOp()` in the :program:`mongo` shell to terminate an
+   :method:`db.killOp()` in the :program:`mongo` shell to terminate the
    operation.
 
 .. data:: active
 
-   A boolean value, that is ``true`` if the option is currently running,
-   or ``false`` if queued and waiting for a lock to run.
+   A boolean value, that is ``true`` if the option is currently running
+   or ``false`` if the operation is queued and waiting for a lock to run.
 
 .. data:: secs_running
 
-   The duration of this operation in seconds.
+   The duration of the operation in seconds.
 
 .. data:: op
 
@@ -98,20 +98,20 @@ Output Reference
 
 .. data:: ns
 
-   The :term:`namespace` that this operation targets. Namespaces are
+   The :term:`namespace` the operation targets. Namespaces are
    formed using the name of the :term:`database` and the name of the
    :term:`collection`.
 
 .. data:: query
 
-   A document containing the current operation's query. This document
+   A document containing the current operation's query. The document
    is empty for operations that do not have queries: ``getmore``,
    ``insert``, ``delete``, and ``command``.
 
 .. data:: client
 
    The IP address (or hostname) and the ephemeral port of the client
-   connection where this operation originates. If your ``inprog``
+   connection where the operation originates. If your ``inprog``
    array has operations from many different clients, use this string
    to relate operations to clients.
 
@@ -122,16 +122,16 @@ Output Reference
 
 .. data:: threadId
 
-   An identifier for the thread that services this operations and its
+   An identifier for the thread that services the operation and its
    connection.
 
 .. data:: connectionId
 
-   An identifier for the connection where this operation originated.
+   An identifier for the connection where the operation originated.
 
 .. data:: locks
 
-   The :data:`locks` document reports on the kinds of locks this
+   The :data:`locks` document reports on the kinds of locks the
    operation currently holds. The following lock types are possible:
 
    .. data:: locks.^
@@ -161,55 +161,55 @@ Output Reference
 .. data:: msg
 
    The :data:`msg` provides a message that describes the status and
-   progress of the operation. In the case of indexing operations, this
+   progress of the operation. In the case of indexing operations, the
    field reports the completion percentage.
 
 .. data:: numYields
 
-   :data:`numYields` is a counter that reports the number of time that
-   this operation has yielded to allow other operations to complete.
+   :data:`numYields` is a counter that reports the number of times the
+   operation has yielded to allow other operations to complete.
 
-   Typically, operations will yield when they need access that
-   is not yet in memory while MongoDB reads in the data. This allows
-   other operations that have data already in memory, to complete quickly
-   while MongoDB reads the data for the yielding operation into memory.
+   Typically, operations yield when they need access to data that
+   MongoDB has not yet fully read into memory. This allows
+   other operations that have data in memory to complete quickly
+   while MongoDB reads in data for the yielding operation.
 
 .. data:: lockStats
 
-   The :data:`lockStats` document reflects the amount of time that
-   this operation has spent both acquiring and holding
+   The :data:`lockStats` document reflects the amount of time the
+   operation has spent both acquiring and holding
    locks. :data:`lockStats` reports data on a per-lock type, with the
    following possible lock types:
 
-   - ``r`` represents the database specific read lock and
+   - ``r`` represents the database specific read lock, and
    - ``w`` represents the database specific write lock.
 
     .. data:: timeLockedMicros
 
        The :data:`timeLockedMicros` document reports the amount of
-       time this operation has spent holding a specific lock.
+       time the operation has spent holding a specific lock.
 
        .. data:: timeLockedMicros.r
 
-          Reports the amount of time that this operation has held the
-          database specific read lock in microseconds.
+          Reports the amount of time in microseconds the operation has held the
+          database specific read lock.
 
        .. data:: timeLockedMicros.w
 
-          Reports the amount of time that this operation has held the
-          database specific write lock in microseconds.
+          Reports the amount of time in microseconds the operation has held the
+          database specific write lock.
 
    .. data:: timeAquiringMicros
 
       The :data:`timeLockedMicros` document reports the amount of time
-      this operation has spent *waiting* to acquire a specific lock.
+      the operation has spent *waiting* to acquire a specific lock.
 
       .. data:: timeAcquiringMicros.r
 
-         Reports the mount of time the operation has waited for the
-         database specific read lock in microseconds.
+         Reports the mount of time in microseconds the operation has waited for the
+         database specific read lock.
 
       .. data:: timeAcquiringMicros.w
 
-         Reports the mount of time the operation has waited for the
-         database specific write lock in microseconds.
+         Reports the mount of time in microseconds the operation has waited for the
+         database specific write lock.