DOCSP-38446 Clarify verification in Cutover Process (#306)

* DOCSP-38446 Verification Clarification

* Reworks intro text

* Fixes links

* Adjusts tet

* Adjusts text

* Adjusts text

* Adjusts text

* Adjusts text

* Adjusts text

* Adjusts text

* Adjusts text

* Fixes per Jason

* Fixes per Ashley

Author: kennethdyer

source/reference/cutover-process.txt

@@ -1,22 +1,30 @@
 .. _c2c-cutover-process:
 
-===============
-Cutover Process 
-===============
+========================
+Finalize Cutover Process
+========================
 
 .. default-domain:: mongodb
 
 .. contents:: On this page
    :local:
    :backlinks: none
    :class: singlecol
+   :depth: 1
 
-You can finalize a migration and transfer your application's writes from
-the source to the destination cluster using the ``mongosync`` cutover
-process. 
+You can finalize a migration and transfer your application
+workload from the source to the destination cluster using the
+``mongosync`` cutover process. 
 
-Procedure 
----------
+.. note::
+
+   Before you switch your application workload to the
+   destination cluster, you should always verify that the sync
+   was successful. For more information, see
+   :ref:`c2c-verification`.
+
+Steps
+-----
 
 .. procedure:: 
    :style: normal 
@@ -43,7 +51,7 @@ Procedure
       - If you didn't start ``mongosync`` with
         ``enableUserWriteBlocking``, ensure that writes are disabled.
         For example, run the ``setUserWriteBlockMode`` command on the
-        source cluster.  
+        source cluster.
       - If ``mongosync`` uses filtered sync, it's not necessary to
         disable writes to the entire source cluster. But you must ensure
         that write operations are stopped for the collections included
@@ -66,7 +74,14 @@ Procedure
 
       Call the ``progress`` endpoint to determine if ``canWrite`` is
       ``true``. If ``canWrite`` is ``false``, wait until ``progress``
-      shows ``canWrite`` is ``true``.  
+      shows ``canWrite`` is ``true``.
+
+   .. step:: Verify data transfer.
+
+      Verify the successful sync of data from the source to the
+      destination cluster.
+
+      For more information, see :ref:`c2c-verification`.
 
    .. step:: Enable application writes on the destination cluster.
 
@@ -86,3 +101,13 @@ Procedure
       When the ``mongosync`` progress response indicates that the 
       ``mongosync`` state is ``COMMITTED``, the cutover process is
       complete. 
+
+Learn More
+----------
+
+- :ref:`c2c-verification`
+- :ref:`c2c-api-start`
+- :ref:`c2c-api-commit`
+- :ref:`c2c-api-progress`
+- :ref:`c2c-states`
+