DOCSP 28174 adding info to commit page (#222) (#237)

* DOCSP 28174 adding info to commit page (#222)

* DOCSP-28714 clarifying commit

* DOCSP-28174 adding commit information

* DOCSP-28174 adding commit information

* DOCSP-28174 copy edits

* DOCSP-28174 copy edits

* DOCSP-28174 adding commit behavior table

* DOCSP-28174 adding commit behavior table

* DOCSP-28174 adding commit behavior table

* DOCSP-28174 adding commit behavior table

* DOCSP-28174 updating disaster recovery

* DOCSP-28174-v1.7-backport removing capped collections reference

Author: ltran-mdb2

source/reference/api/commit.txt

@@ -15,7 +15,34 @@
 Description
 -----------
 
-Commits the synchronization operation to the destination cluster.
+Finalizes the sync between the source cluster and the destination
+cluster and stops continuous sync between clusters. ``commit`` also
+restores collection characteristics that ``mongosync`` temporarily
+alters during synchronization. 
+
+The following table illustrates the impact of ``commit`` on collection
+characteristics that ``mongosync`` alters during the synchronization process.
+
+.. list-table::
+   :header-rows: 1
+
+   * - Collection Characteristic
+     - Impact of ``commit`` 
+   * - :ref:`Unique Indexes <c2c-dr-unique>`
+     - ``commit`` resets unique indexes that ``mongosync`` replicated as
+       non-unique on the destination cluster.
+
+   * - :ref:`TTL Indexes <c2c-dr-ttl>`
+     - ``commit`` resets ``expireAfterSeconds`` which ``mongosync`` set
+       to the value of ``MAX_INT`` on the destination cluster.
+
+   * - :ref:`Hidden Indexes <c2c-dr-hidden>`
+     - ``commit`` resets hidden indexes that ``mongosync``
+       replicated as non-hidden on the destination cluster.
+
+   * - :ref:`Write Blocking <c2c-dr-write-blocking>`
+     - If ``mongosync`` disabled writes on the destination cluster,
+       ``commit`` disables the Write Block Mode. 
 
 Requirements
 ------------
@@ -114,4 +141,7 @@ Behavior
 
 If the ``commit`` request is successful, ``mongosync`` enters the
 ``COMMITTING`` state, then automatically transitions to the
-``COMMITTED`` state.
+``COMMITTED`` state. Once ``mongosync`` enters the ``COMMITTED`` state,
+continuous sync between the clusters stops. 
+
+

source/reference/disaster-recovery.txt

@@ -25,8 +25,9 @@ during synchronization. The original values are restored during the
 you must manually reset these collection characteristics on the destination
 cluster before you can use it as the primary cluster.
 
-To prepare the destination cluster to replace the source cluster, make the 
-following changes:
+To prepare the destination cluster to replace the source cluster, make
+the following changes that mimic the sync finalization process of the
+``commit`` endpoint. 
 
 .. list-table::
    :header-rows: 1