reviewer updates

Author: amalhotra-mdb

source/faq.txt

@@ -54,6 +54,14 @@ To learn more about permissable reads and writes during synchronization, see
    Index builds on the destination cluster are treated as writes 
    while ``mongosync`` is syncing.
 
+Can I use ``mongosync`` to maintain a Disaster Recovery cluster?
+----------------------------------------------------------------
+
+No, you can't currently maintain a Disaster Recovery cluster with ``mongosync``, 
+since ``mongosync`` **must :ref:`<c2c-api-commit>`** in order to 
+safely accept traffic to the destination cluster. 
+For more information, see :ref:`c2c-faq-reads-writes-mongosync`.
+
 Why are the destination cluster indexes larger than the source cluster indexes?
 -------------------------------------------------------------------------------
 
@@ -234,11 +242,4 @@ Can I customize chunk distributions when syncing into a sharded cluster?
 No, you can't configure ``mongosync`` to customize chunk distributions
 on a destination sharded cluster.  ``mongosync`` samples each collection
 during initialization to determine how to distribute documents
-efficiently across the destination cluster’s shards after migration.
-
-Can I use ``mongosync`` to set up a Disaster Recovery cluster?
---------------------------------------------------------------
-
-No, you can't currently set up a Disaster Recovery cluster with ``mongosync``, 
-since ``mongosync`` **must commit** in order to safely accept traffic to the 
-destination cluster. For more information, see :ref:`c2c-faq-reads-writes-mongosync`.
+efficiently across the destination cluster’s shards after migration.

source/includes/fact-no-mongosync-disaster-recovery.rst

@@ -1,4 +1,4 @@
-Until you've called commit on ``mongosync`` and ``canWrite`` successfully 
+Until you've called :ref:`<c2c-api-commit>` on ``mongosync`` and ``canWrite`` successfully 
 returns ``true``, the destination cluster cannot be used to accept 
 application read or write traffic. 
 Do not use ``mongosync`` for maintaining Disaster Recovery clusters.

source/reference/mongosync/mongosync-behavior.txt

@@ -215,10 +215,6 @@ invalid index options on the destination.
 Considerations for Continuous Sync
 ----------------------------------
 
-For any continuous synchronization use cases with ``mongosync``, ensure that 
-``mongosync`` commits before cutting over from the source to the 
-destination.
-
 .. important::
 
    .. include:: /includes/fact-no-mongosync-disaster-recovery.rst