DOCSP-47159: Clarify write blocking recommendation on finalize cutover page (#599) (#607)

* init commit

* rendering fix

* render

* clarity

* change

* change

* remove link

(cherry picked from commit 07991f7)

Co-authored-by: Maya Raman <[email protected]>

Author: github-actions[bot]

source/reference/cutover-process.txt

@@ -145,7 +145,7 @@ Steps
 
       For more information, see :ref:`c2c-verification`.
 
-   .. step:: Enable application writes on the destination cluster.
+   .. step:: If you manually blocked writes on the destination cluster by using :dbcommand:`setUserWriteBlockMode`, enable application writes on the destination cluster.
 
       To enable writes, update :dbcommand:`setUserWriteBlockMode`:
 
@@ -160,6 +160,11 @@ Steps
 
       Then, transfer your application workload to the destination cluster.
 
+      If you started ``mongosync``
+      with write-blocking by using the ``enableUserWriteBlocking`` option on
+      the :ref:`/start <c2c-api-start>` endpoint, you do not need
+      to complete this step.
+
    .. step:: Call the ``progress`` endpoint to determine the status of the ``mongosync`` process.
 
       When the ``mongosync`` progress response indicates that the