Edits for style, grace & clarity

source/reference/command/captrunc.txt

@@ -9,14 +9,14 @@ Definition
 
 .. dbcommand:: captrunc
 
-   Truncates capped collections. :dbcommand:`captruc` is an internal
+   Truncates capped collections. :dbcommand:`captrunc` is an internal
    command to support testing, that takes the following form:
 
    .. code-block:: javascript
 
       { captrunc: "<collection>", n: <integer>, inc: <true|false> }.
 
-   :dbcommand:`captruc` has the following fields:
+   :dbcommand:`captrunc` has the following fields:
 
    .. include:: /reference/command/captrunc-field.rst
 

source/reference/method/db.collection.findOne.txt

@@ -12,12 +12,12 @@ Definition
    Returns one document that satisfies the specified query. If
    multiple documents satisfy the query, this method returns the first
    document according to the :term:`natural order` which reflects the
-   order of documents on the disc. In :term:`capped collections
+   order of documents on the disk. In :term:`capped collections
    <capped collection>`, natural order is the same as insertion order.
 
    .. include:: /reference/method/db.collection.findOne-param.rst
 
-   :returns: 
+   :returns:
 
       One document that satisfies the query specified as the argument
       to this method. If you specify the ``projection`` argument,

source/reference/method/sh.moveChunk.txt

@@ -15,7 +15,7 @@ Definition
    command and takes the following arguments:
 
    .. include:: /reference/method/sh.moveChunk-param.rst
-              
+
    .. important:: In most circumstances, allow the :term:`balancer` to
       automatically migrate :term:`chunks <chunk>`, and avoid calling
       :method:`sh.moveChunk()` directly.
@@ -28,7 +28,7 @@ Example
 -------
 
 Given the ``people`` collection in the ``records`` database, the
-following operations finds the chunk that contains the documents with the
+following operation finds the chunk that contains the documents with the
 ``zipcode`` field set to ``53187`` and then moves that chunk to the
 shard named ``shard0019``:
 

source/reference/user-privileges.txt

@@ -225,7 +225,7 @@ Administrative Roles
    - :dbcommand:`unsetSharding`
 
    For some cluster administration operations, MongoDB requires read
-   and write access to the ``local`` or ``config``. You must specify
+   and write access to the ``local`` or ``config`` databases. You must specify
    this access separately from :authrole:`clusterAdmin`. See the
    :ref:`auth-role-combined` section for more information.
 

source/tutorial/replace-config-server.txt

@@ -26,7 +26,7 @@ If you must change the hostname of the instance, use the procedure to
    modify the DNS records and wait for them to propagate.
 
 #. Shut down *one* (and only one) of the existing config servers. Copy
-   all this host's :setting:`dbpath` file system tree from the current system
+   all of this host's :setting:`dbpath` file system tree from the current system
    to the system that will provide the new config server. This
    command, issued on the system with the data files, may resemble the
    following:

source/tutorial/upgrade-revision.txt

@@ -126,7 +126,7 @@ To upgrade a sharded cluster:
 
    ..example:: Given the following config string:
 
-     .. code-block:: cfg
+     .. code-block:: sh
 
         mongos --configdb cfg0.example.net:27019,cfg1.example.net:27019,cfg2.example.net:27019