From 85fd410c49bd44ebeaa0e6993c96763a77ac8797 Mon Sep 17 00:00:00 2001
From: Andrew Leung <andrew.leung@10gen.com>
Date: Mon, 27 Aug 2012 17:52:01 -0400
Subject: [PATCH] minor wording edits to currentOp

---
 draft/reference/current-op.txt | 28 ++++++++++++----------------
 1 file changed, 12 insertions(+), 16 deletions(-)

diff --git a/draft/reference/current-op.txt b/draft/reference/current-op.txt
index fb3215f7152..7e9cd47af5b 100644
--- a/draft/reference/current-op.txt
+++ b/draft/reference/current-op.txt
@@ -8,7 +8,7 @@ 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 which contains a
+instance. The command returns the ``inprog`` array, that contains a
 document for each in progress operation. Consider the following
 example output:
 
@@ -57,7 +57,7 @@ example output:
 .. optional::
 
    You may specify the ``true`` argument to :method:`db.currentOp()`
-   to return full output. For example:
+   to return a more verbose output. For example:
 
    .. code-block:: javascript
 
@@ -66,9 +66,6 @@ example output:
    Furthermore, active operations (i.e. where :data:`active` are
    ``true``) will return additional fields.
 
-Continue reading for full documentation of the entire output of
-:method:`db.currentOp()`.
-
 Output Reference
 ----------------
 
@@ -80,9 +77,8 @@ Output Reference
 
 .. data:: active
 
-   A boolean value, that reports if the option is currently running,
-   with the ``true`` value, or queued and waiting for a lock to run,
-   with the ``false`` value.
+   A boolean value, that is ``true`` if the option is currently running,
+   or ``false`` if queued and waiting for a lock to run.
 
 .. data:: secs_running
 
@@ -135,7 +131,7 @@ Output Reference
 
 .. data:: locks
 
-   The :data:`locks` document reports on the kinds of locks that this
+   The :data:`locks` document reports on the kinds of locks this
    operation currently holds. The following lock types are possible:
 
    .. data:: locks.^
@@ -160,7 +156,7 @@ Output Reference
 
    Returns a boolean value. :data:`waitingForLock` is ``true`` if the
    operation is waiting for a lock and ``false`` if the operation has
-   the locks that it needs to complete.
+   the lock that it needs to complete.
 
 .. data:: msg
 
@@ -173,14 +169,14 @@ Output Reference
    :data:`numYields` is a counter that reports the number of time that
    this operation has yielded to allow other operations to complete.
 
-   Typically, operations will yield when they need to access that that
-   is not yet in memory while MongoDB pages in that data. This allows
-   other operations that are already in memory, to complete quickly
-   while MongoDB reads the data for the first operation into memory.
+   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.
 
 .. data:: lockStats
 
-   The :data:`lockStats` document reflects the amount of time that a
+   The :data:`lockStats` document reflects the amount of time that
    this operation has spent both acquiring and holding
    locks. :data:`lockStats` reports data on a per-lock type, with the
    following possible lock types:
@@ -191,7 +187,7 @@ Output Reference
     .. data:: timeLockedMicros
 
        The :data:`timeLockedMicros` document reports the amount of
-       time this operation has spent holding specific locks.
+       time this operation has spent holding a specific lock.
 
        .. data:: timeLockedMicros.r