write blocking params

Author: mayaraman19

source/includes/live-upgrade.rst

@@ -5,4 +5,4 @@ only live upgrade to ``mongosync`` 1.7.3 or later from ``mongosync``
 
 .. important::
 
-   ``mongosync`` does not support live upgrades to version 1.11.
+   ``mongosync`` does not support live upgrades to version 1.11 or 1.12.

source/reference/api/start.txt

@@ -117,26 +117,29 @@ Request Body Parameters
    * - ``enableUserWriteBlocking``
      - boolean or string
      - Optional
-     - If set to ``true``, blocks writes on the destination 
-       cluster while the migration is in progress, and unblocks writes right
-       before the :ref:`/progress <c2c-api-progress>` endpoint reports 
-       that ``canWrite`` is ``true``.  Blocks writes on the source
-       cluster after ``mongosync`` calls the :ref:`/commit <c2c-api-commit>`
-       endpoint.
-
-       If set to ``false``, no write blocking occurs.
-
-       If set to ``"destinationOnly"``, blocks writes on the destination
-       cluster while migration is in progress, and unblocks writes right
-       before ``canWrite`` is ``true``.
-
-       :gold:`IMPORTANT:` If you are migrating from a pre-6.0 source cluster, 
-       you cannot set ``enableUserWriteBlocking`` to ``true``.
+     - Supported options:
+       
+       - ``true`` or ``"sourceAndDestination"``: blocks writes on the destination 
+         cluster while the migration is in progress, and unblocks writes right
+         before the :ref:`/progress <c2c-api-progress>` endpoint reports 
+         that ``canWrite`` is ``true``.  Blocks writes on the source
+         cluster after ``mongosync`` calls the :ref:`/commit <c2c-api-commit>`
+         endpoint.
+         
+         :gold:`IMPORTANT:` If you are migrating from a pre-6.0 source cluster, 
+         you cannot set ``enableUserWriteBlocking`` to ``true`` or
+         ``"sourceAndDestination"``.
+
+       - ``false`` or ``"none"``: no write blocking occurs.
+
+       - ``"destinationOnly"``: blocks writes on the destination
+         cluster while migration is in progress, and unblocks writes right
+         before ``canWrite`` is ``true``.
 
        To reverse sync, the ``enableUserWriteBlocking`` field must be set
-       to ``true``. To allow the source cluster to accept writes again,
-       for example after running migration tests, run the following
-       command: 
+       to ``true`` or ``"sourceAndDestination"``. To allow the source cluster 
+       to accept writes again, for example after running migration tests, 
+       run the following command: 
 
        .. code-block:: shell