adding in note about secondary members in moveChunk failure

Author: Andrew Leung

source/faq/sharding.txt

@@ -349,9 +349,9 @@ 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 :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.
+itself to prevent data inconsistency. If the config database is
+accessible by the :term:`secondary` members, the shard's data will be
+accessible after an election.
 
 If you encounter this issue, contact the `MongoDB User Group
 <http://groups.google.com/group/mongodb-user>`_ or 10gen support to