DOCS-306: edits

Author: Sam Kleinman

source/administration/sharding.txt

@@ -621,16 +621,17 @@ In most circumstances, you should let the automatic balancer
 migrate :term:`chunks <chunk>` between :term:`shards <shard>`.
 However, you may want to migrate chunks manually in a few cases:
 
-- If you create chunks by :term:`pre-splitting` the data in your collection,
-  you will have to migrate chunks manually to distribute chunks
-  evenly across the shards.
+- If you create chunks by :term:`pre-splitting` the data in your
+  collection, you will have to migrate chunks manually to distribute
+  chunks evenly across the shards. Use pre-splitting in limited
+  situations, to support bulk data ingestion.
 
 - If the balancer in an active cluster cannot distribute chunks within
   the balancing window, then you will have to migrate chunks manually.
 
 See the :ref:`chunk migration <sharding-chunk-migration>` section to
-understand the internal process of how :term:`chunks <chunk>` move
-between :term:`shards <shard>`.
+understand the internal process of how chunks move
+between shards.
 
 To migrate chunks, use the :dbcommand:`moveChunk` command.
 
@@ -660,9 +661,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 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`.
+See :ref:`sharding-administration-create-chunks` for an introduction
+to pre-splitting. 
 
 .. versionadded:: 2.2
    :dbcommand:`moveChunk` command has the: ``_secondaryThrottle``

source/reference/command/moveChunk.txt

@@ -6,9 +6,9 @@ moveChunk
 
 .. dbcommand:: moveChunk
 
-   :dbcommand:`moveChunk` is an internal command that moves
-   :term:`chunks <chunk>` between :term:`shards <shard>`. The command
-   has the following prototype form:
+   :dbcommand:`moveChunk` is an internal administrative command that
+   moves :term:`chunks <chunk>` between :term:`shards <shard>`. The
+   command has the following prototype form:
 
    .. code-block:: javascript
 
@@ -18,25 +18,23 @@ moveChunk
                        <options> } )
 
    :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"``.
+                             the :term:`chunk` exists. Specify the 
+                             collection's full namespace, including
+                             the database name. 
 
-   :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 find: A query expression that will select a document within
+                the chunk you wish to move. The query need not specify
+                the :term:`shard key`.
 
-   :param to: The shard ID where the chunk will be moved to, for
-              example: ``"shard1"``.
+   :param to: The identifier of the shard, that you want to migrate the
+              chunk to.
 
    :param _secondaryThrottle: Optional. Set to ``false`` by
                               default. Provides :ref:`write concern
                               <write-concern>` support for chunk
                               migrations.
 
-   If ``_secondaryThrottle`` is set to ``true``, during chunk
+   If you set ``_secondaryThrottle`` 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
@@ -63,11 +61,9 @@ moveChunk
 
    .. note::
 
-      The :dbcommand:`moveChunk` command should be used in special circumstances
+      Only use the :dbcommand:`moveChunk` in special circumstances
       such as preparing your :term:`shard cluster` for an initial
-      ingestion of data.
-
-      .. seealso:: ":ref:`Create chunk <sharding-administration-create-chunks>`"
-
+      ingestion of data, or a large bulk import operation. See
+      :ref:`sharding-administration-create-chunks` for more information.
 
    .. admin-only