edits for style, adding "command" qualification in various places or

fixing grammar.

Author: Ed Costello

source/administration/sharding-architectures.txt

@@ -106,7 +106,7 @@ created subsequently, may reside on any shard in the cluster.
 .. [#sharding-databases] As you configure sharding, you will use the
    :dbcommand:`enableSharding` command to enable sharding for a
    database. This simply makes it possible to use the
-   :dbcommand:`shardCollection` on a collection within that database.
+   :dbcommand:`shardCollection` command on a collection within that database.
 
 .. [#overloaded-primary-term] The term "primary" in the context of
    databases and sharding, has nothing to do with the term

source/administration/sharding.txt

@@ -236,7 +236,7 @@ procedure:
    .. optional::
 
       You may specify a "name" as an argument to the
-      :dbcommand:`addShard`, as follows:
+      :dbcommand:`addShard` command, as follows:
 
       .. code-block:: javascript
 
@@ -323,7 +323,7 @@ The procedure to remove a shard is as follows:
 
 #. View progress of the migration.
 
-   You can run the :dbcommand:`removeShard` again at any stage of the
+   You can run the :dbcommand:`removeShard` command again at any stage of the
    process to view the progress of the migration, as follows:
 
    .. code-block:: javascript
@@ -360,7 +360,7 @@ The procedure to remove a shard is as follows:
 
    .. warning::
 
-      Do not run the :dbcommand:`movePrimary` until you have *finished*
+      Do not run the :dbcommand:`movePrimary` command until you have *finished*
       draining the shard.
 
    The command will not return until MongoDB completes moving all

source/core/sharding-internals.txt

@@ -267,7 +267,7 @@ Shard Key Indexes
 All sharded collections **must** have an index that starts with the
 :term:`shard key`. If you shard a collection that does not yet contain
 documents and *without* such an index, the :dbcommand:`shardCollection`
-will create an index on the shard key. If the collection already
+command will create an index on the shard key. If the collection already
 contains documents, you must create an appropriate index before using
 :dbcommand:`shardCollection`.
 

source/reference/collection-statistics.txt

@@ -48,7 +48,7 @@ Or:
 Example Document
 ----------------
 
-The output of :method:`db.collection.stats()` resembles the following: 
+The output of :method:`db.collection.stats()` resembles the following:
 
 .. code-block:: javascript
 
@@ -115,13 +115,13 @@ Fields
 
    The number of indexes on the collection. All collections have at
    least one index on the :term:`_id` field.
-   
+
    .. versionchanged:: 2.2
       Before 2.2, capped collections did not necessarily have an
       index on the ``_id`` field, and some capped collections created
       with pre-2.2 versions of :program:`mongod` may not have an
       ``_id`` index.
-      
+
 
 .. stats:: lastExtentSize
 
@@ -161,7 +161,7 @@ Fields
    Reports the flags on this collection set by the user. In version
    2.2 the only user flag is ``usePowerOf2Sizes``.
 
-   See :dbcommand:`collMod` for more information on setting user
+   See the :dbcommand:`collMod` command for more information on setting user
    flags and :ref:`usePowerOf2Sizes <usePowerOf2Sizes>`.
 
 .. stats:: totalIndexSize

source/reference/command/reIndex.txt

@@ -14,9 +14,9 @@ reIndex
       { reIndex: "collection" }
 
    Normally, MongoDB compacts indexes during routine updates. For most
-   users, the :dbcommand:`reIndex` is unnecessary. However, it may be worth
-   running if the collection size has changed significantly or if the
-   indexes are consuming a disproportionate amount of disk space.
+   users, the :dbcommand:`reIndex` command is unnecessary. However, it
+   may be worth running if the collection size has changed significantly
+   or if the indexes are consuming a disproportionate amount of disk space.
 
    Note that the :dbcommand:`reIndex` command will block the server against
    writes and may take a long time for large collections.

source/reference/command/renameCollection.txt

@@ -20,7 +20,7 @@ renameCollection
    The ``dropTarget`` argument is optional.
 
    If you specify a collection to the ``to`` argument in a different database, the
-   :dbcommand:`renameCollection` will copy the collection to the new
+   :dbcommand:`renameCollection` command will copy the collection to the new
    database and then drop the source collection.
 
    :param source-namespace:

source/reference/mongod.txt

@@ -54,8 +54,8 @@ Options
 .. option:: --quiet
 
    Runs the :program:`mongod` instance in a quiet mode that attempts to limit
-   the amount of output. This option suppresses: 
-   
+   the amount of output. This option suppresses:
+
    - output from :term:`database commands <database command>`,
      including :dbcommand:`drop`, :dbcommand:`dropIndexes`,
      :dbcommand:`diagLogging`, :dbcommand:`validate`, and
@@ -353,7 +353,7 @@ Options
 .. option:: --repair
 
    Runs a repair routine on all databases. This is equivalent
-   to shutting down and running :dbcommand:`repairDatabase` database
+   to shutting down and running the :dbcommand:`repairDatabase` database
    command on all databases.
 
    .. include:: /includes/warning-repair.rst
@@ -385,7 +385,7 @@ Options
    option. The database logs all slow queries to the log, even when
    the profiler is not turned on. When the database profiler is on,
    :program:`mongod` the profiler writes to the ``system.profile``
-   collection. See :dbcommand:`profile` for more information on the
+   collection. See the :dbcommand:`profile` command for more information on the
    database profiler.
 
 .. option:: --smallfiles
@@ -583,9 +583,9 @@ Sharding Cluster Options
 .. option:: --noMoveParanoia
 
    Disables a "paranoid mode" for data writes for chunk migration
-   operation. See the :ref:`chunk migration
-   <sharding-chunk-migration>` and :dbcommand:`moveChunk` command
-   documentation for more information.
+   operation. See the
+   :ref:`chunk migration <sharding-chunk-migration>`
+   and :dbcommand:`moveChunk` command documentation for more information.
 
    By default :program:`mongod` will save copies of migrated chunks on
    the "from" server during migrations as "paranoid mode." Setting

source/use-cases/storing-log-data.txt

@@ -216,7 +216,7 @@ The following command will insert the ``event`` object into the
 By setting ``w=0``, you do not require that MongoDB
 acknowledges receipt of the insert.  Although very fast, this is risky
 because the application cannot detect network and server failures. See
-:ref:`write-concern` for more information. 
+:ref:`write-concern` for more information.
 
 If you want to ensure that MongoDB acknowledges inserts, you can pass
 ``w=1`` argument as follows:
@@ -496,7 +496,7 @@ that select, process, and aggregate results from large numbers of
 documents. The :method:`aggregate() <db.collection.aggregate()>` (and :dbcommand:`aggregate`
 :term:`command <database command>`) offers greater flexibility,
 capacity with less complexity than the existing :dbcommand:`mapReduce`
-and :dbcommand:`group` aggregation.
+and :dbcommand:`group` aggregation commands.
 
 Consider the following aggregation :term:`pipeline`: [#sql-aggregation-equivalents]_