DOCS-306: edits and clarification

Author: Sam Kleinman

source/administration/sharding.txt

@@ -548,7 +548,7 @@ However, you may want to migrate chunks manually in a few cases:
 - If the balancer in an active cluster cannot distribute chunks within
   the balancing window, then you will have to migrate chunks manually.
 
-To migrate chunks, use the :dbcommand:`moveChunk` command. 
+To migrate chunks, use the :dbcommand:`moveChunk` command.
 
 .. note::
 
@@ -577,22 +577,26 @@ This command moves the chunk that includes the shard key value "smith" to the
 block until the migration is complete.
 
 .. versionadded:: 2.2
-   :dbcommand:`moveChunk` command now has the : ``_secondaryThrottle``
+   :dbcommand:`moveChunk` command has the: ``_secondaryThrottle``
    paramenter. When set to ``true``, MongoDB ensures that
    :term:`secondary` members have replicated operations before allowing
    new chunk migrations.
 
 .. warning::
 
-   The :dbcommand:`moveChunk` command may produce an error message:
+   The :dbcommand:`moveChunk` command may produce the following error
+   message:
 
    .. code-block:: none
 
       The collection's metadata lock is already taken.
 
-   when there are open :term:`cursors <cursor>` accessing the chunk to
-   be moved. To fix this situation, either wait until the cursors
-   complete their operation or remove the cursors.
+   These errors occur when clients have too many open :term:`cursors
+   <cursor>` that access the chunk you are migrating. You can either
+   wait until the cursors complete their operation or close the
+   cursors manually.
+
+   .. TODO insert link to killing a cursor.
 
 .. index:: balancing; operations
 .. _sharding-balancing-operations:
@@ -718,8 +722,8 @@ be able to migrate chunks:
    patterns, it is important to ensure that the balancing window you
    select will be sufficient to support the needs of your deployment.
 
-Remove Balancing Window Schedule
---------------------------------
+Remove a Balancing Window Schedule
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 If you have :ref:`set the balancing window
 <sharding-schedule-balancing-window>` and wish to remove the schedule

source/faq/sharding.txt

@@ -332,14 +332,23 @@ hashed value in your application and include this value in your
 documents for use as a shard key, the :issue:`SERVER-2001` issue will
 implement this capability within MongoDB.
 
-What does "ERROR: moveChunk commit failed: version is at X|Y instead of A|B" and "ERROR: TERMINATING" mean? What happened?
---------------------------------------------------------------------------------------------------------------------------
+What do ``moveChunk commit failed`` errors mean?
+------------------------------------------------
 
-During a :ref:`chunk migration <sharding-chunk-migration>`, the
-:term:`shard` could not connect to the :term:`config database` to update
-chunk information. If the shard cannot update the config database
-after :dbcommand:`moveChunk`, the shard cluster will have an
-inconsistent view of all chunks. For this situation, the shard will
-terminate itself to prevent data inconsistency and produce this error.
+Consider the following error message:
 
-Please contact MongoDB support directly for help in resolving this situation.
+.. code-block:: none
+
+   ERROR: moveChunk commit failed: version is at <n>|<nn> instead of <N>|<NN>" and "ERROR: TERMINATING"
+
+:program:`mongod` procudes this message if, during a :ref:`chunk
+migration <sharding-chunk-migration>`, the term:`shard` could not
+connect to the :term:`config database` to update chunk information. If
+the shard cannot update the config database after
+:dbcommand:`moveChunk`, the shard cluster will have an inconsistent
+view of all chunks. For this situation, the shard will terminate
+itself to prevent data inconsistency.
+
+If you encounter this issue, contact the `MongoDB User Group
+<http://groups.google.com/group/mongodb-user>`_ or 10gen support to
+address this issue.