added in note to specify difference of shard vs shard primary terminating and continued access

Author: Andrew Leung

source/faq/sharding.txt

@@ -343,11 +343,15 @@ Consider the following error message:
 
 :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
+connect to the :term:`config database` to update chunk information at
+the end of the migration process. 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.
+view of all chunks. For this situation, the :term:`primary` member of
+the shard will terminate
+itself to prevent data inconsistency. The :term:`secondary` members of
+the shard will elect a new primary member so that the remainder of the
+shard data is available for access.
 
 If you encounter this issue, contact the `MongoDB User Group
 <http://groups.google.com/group/mongodb-user>`_ or 10gen support to