additional revisions for clarity and style

Author: Andrew Leung

source/administration/sharding.txt

@@ -658,8 +658,8 @@ This command moves the chunk that includes the shard key value "smith" to the
 :term:`shard` named ``mongodb-shard3.example.net``. The command will
 block until the migration is complete.
 
-See :ref:`create chunks <sharding-administration-create-chunks>` to
-understand how to use :term:`pre-splitting` to improve initial data
+See the :ref:`create chunks <sharding-administration-create-chunks>` section
+for an overview of how :term:`pre-splitting` can improve initial data
 load on a :term:`shard cluster`.
 
 .. versionadded:: 2.2

source/reference/command/moveChunk.txt

@@ -8,7 +8,7 @@ moveChunk
 
    :dbcommand:`moveChunk` is an internal command that moves
    :term:`chunks <chunk>` between :term:`shards <shard>`. The command
-   uses the following syntax:
+   has the following prototype form:
 
    .. code-block:: javascript
 
@@ -17,40 +17,44 @@ moveChunk
                        to : <destination>,
                        <options> } )
 
-   :param moveChunk: the name of the :term:`collection` which the :term:`chunk`
-     exists. The collection's full namespace must be given, including
-     the database name, for example: ``"test.blog.posts"``
+   :param command moveChunk: The name of the :term:`collection` which
+                             the :term:`chunk` exists. The
+                             collection's full namespace must be
+                             given, including the database name, for
+                             example: ``"test.blog.posts"``.
 
-   :param find: a query expression that specifies a document of the chunk
-     to be moved, for example: ``{ author: "eliot" }``
+   :param find: A query expression that specifies a document of the
+                chunk to be moved, for example: ``{ author: "eliot"
+                }``. The query does not have to be related to the
+                :term:`shard key`.
 
-   :param to: the shard ID where the chunk will be moved to, for
-     example: ``"shard1"``
+   :param to: The shard ID where the chunk will be moved to, for
+              example: ``"shard1"``.
 
+   :param _secondaryThrottle: Optional. Set to ``false`` by
+                              default. Provides :ref:`write concern
+                              <write-concern>` support for chunk
+                              migrations.
 
-   :option _secondaryThrottle: Set to ``false`` by default. Provides
-     :ref:`write concern <write-concern>` support for chunk
-     migrations.
-
-     If ``_secondaryThrottle`` is set to ``true``, during chunk
-     migrations when a :term:`shard` hosted by a :term:`replica set`,
-     the :program:`mongod` will wait until the :term:`secondary`
-     members replicate the migration operations continuing to migrate
-     chunk data. In the balancer configuration, the ``replThrottle``
-     configuration provides ``_secondaryThrottle`` behavior.
+   If ``_secondaryThrottle`` is set to ``true``, during chunk
+   migrations when a :term:`shard` hosted by a :term:`replica set`,
+   the :program:`mongod` will wait until the :term:`secondary` members
+   replicate the migration operations continuing to migrate chunk
+   data. In the balancer configuration, the ``replThrottle``
+   configuration provides ``_secondaryThrottle`` behavior.
 
    Use the :method:`sh.moveChunk()` helper in the :program:`mongo`
-   shell for manual chunk migrations.
+   shell to migrate chunks manually.
 
-   For details on how chunks move within MongoDB see the :ref:`chunk
-   migration <sharding-chunk-migration>` section.
+   The :ref:`chunk migration <sharding-chunk-migration>` section
+   describes how chunks move between shards on MongoDB.
 
-   :dbcommand:`moveChunk` will return the following ``errmsg`` if the
-   :term:`chunk` to be moved is in use by another :term:`cursor`:
+   :dbcommand:`moveChunk` will return the following if the
+   chunk to be moved is in use by another :term:`cursor`:
 
    .. code-block:: none
 
-      The collection's metadata lock is already taken.
+      errmsg: "The collection's metadata lock is already taken."
 
    These errors usually occur when there are too many open
    :term:`cursors <cursor>` accessing the chunk you are migrating. You
@@ -59,9 +63,9 @@ moveChunk
 
    .. note::
 
-      This command should not be used except in special circumstances
+      The :dbcommand:`moveChunk` command should be used in special circumstances
       such as preparing your :term:`shard cluster` for an initial
-      ingest of data.
+      ingestion of data.
 
       .. seealso:: ":ref:`Create chunk <sharding-administration-create-chunks>`"