DOCS-16422 clarifying write blocking behavior (#182)

* DOCS-16422 clarifying write blocking behavior

* DOCS-16422 clarifying write blocking behavior

* DOCS-16422 clarifying write blocking behavior

* DOCS-16422 copy edits

* DOCS-16422 copy edits

* DOCS-16422 copy edits

* DOCSP-16422 moving commit section and copy edits

* DOCS-16422 fixing reference

* DOCS-16422 active voice

* DOCS-16422 fixing reference

* DOCS-16422 copy edit

Author: ltran-mdb2

source/includes/fact-write-blocking-enable.rst

@@ -1,7 +1,8 @@
-When write-blocking is enabled, ``mongosync`` blocks writes:
+``mongosync`` does not enable write-blocking by default. If you enable
+write-blocking, ``mongosync`` blocks writes:
 
-- On the destination cluster during sync
-- On the source cluster while committing
+- On the destination cluster during sync.
+- On the source cluster while ``commit`` is running.
 
 To enable write-blocking, use the :ref:`start API <c2c-api-start>`
 to set ``enableUserWriteBlocking`` to ``true``. You cannot enable

source/reference/mongosync.txt

@@ -132,24 +132,6 @@ Global Options
 Behavior
 --------
 
-Commit
-~~~~~~
-
-To stop syncing, use the :ref:`commit <c2c-api-commit>` command on the
-destination cluster to convert indexes and finalize the changes. While
-``commit`` is running:
-
-- Writes are blocked on the source cluster.
-- Writes are blocked on the destination cluster until ``mongosync``
-  begins index validation.
-
-To monitor the ``commit`` process, use the :ref:`progress
-<c2c-api-progress>` command:
-
-- The destination cluster is writable when ``canWrite`` is true.
-- Index conversion is complete when ``mongosync`` enters the
-  ``COMMITTED`` state.
-
 .. _c2c-mongosync-config:
 
 Cluster Independence
@@ -221,16 +203,35 @@ show an empty ``system.views`` collection in that database. The empty
 ``system.views`` collection will not change the accuracy of user
 data on the destination.
 
-.. c2c-write-blocking:
+.. _c2c-write-blocking:
 
 Write Blocking
 ~~~~~~~~~~~~~~
 
 .. include:: /includes/fact-write-blocking-enable.rst
 
-Write-blocking is not enabled by default. You must enable write-blocking
-when you start ``mongosync`` if you want to use :ref:`reverse
-synchronization <c2c-api-reverse>` later.
+You must enable write-blocking when you start ``mongosync`` if you want
+to use :ref:`reverse synchronization <c2c-api-reverse>` later.
+
+Commit
+~~~~~~
+
+To stop syncing, use the :ref:`commit <c2c-api-commit>` command on the
+destination cluster to convert indexes and finalize the changes. If you
+enable :ref:`write-blocking <c2c-write-blocking>`:
+
+
+- ``commit`` blocks writes on the source cluster. 
+- ``commit`` blocks writes on the destination cluster until
+  ``mongosync`` begins index validation.
+
+
+To monitor the ``commit`` process, use the :ref:`progress
+<c2c-api-progress>` command:
+
+- The destination cluster is writable when ``canWrite`` is true.
+- Index conversion is complete when ``mongosync`` enters the
+  ``COMMITTED`` state.
 
 User Permissions
 ````````````````