feedback

Author: gmiller-mdb

source/reference/verification.txt

@@ -98,7 +98,7 @@ source to the destination cluster.
        comparing documents, views, and indexes to confirm the
        sync was successful.
 
-   * - :ref:`Custom or Manual Verification <c2c-custom-manual-verification>`
+   * - :ref:`Verifying Data with Custom Scripts <c2c-custom-manual-verification>`
      - Different types of data require different methods of verification. You can
        can use custom or manual verification to verify :ref:`documents <c2c-document-comparison>`,
        :ref:`indexes <c2c-index-comparison>`, :ref:`metadata <c2c-metadata-comparison>`,
@@ -114,7 +114,7 @@ application workload and the complexity of the data.
    Use Document Counts </reference/verification/count>
    Use Hash Comparison </reference/verification/hash>
    Use Migration Verifier </reference/verification/verifier>
-   Custom or Manual Verification </reference/verification/custom-manual>
+   Verifying Data with Custom Scripts </reference/verification/custom-manual>
 
 Learn More
 ----------

source/reference/verification/custom-manual.txt

@@ -1,7 +1,7 @@
 .. _c2c-custom-manual-verification:
 
 ==================================
-Custom or Manual Verification Page
+Verifying Data with Custom Scripts
 ==================================
 
 .. default-domain:: mongodb
@@ -16,40 +16,38 @@ Custom or Manual Verification Page
    :depth: 1
    :class: singlecol
 
+You can write a script to query your source cluster and compare the documents,
+indexes, collections, metadata, and views with the destination cluster. 
+
 .. _c2c-document-comparison: 
 
-Document Comparison
+Comparing Documents
 -------------------
 
-You can verify sync by comparing documents on the source and destination 
-clusters. 
-
-Write a script that queries collections on the source cluster and then checks 
-that the correct documents, indexes, collections, metadata, and views exist with
-the same values on the destination cluster.
+You can verify sync by comparing documents on the source and destination clusters. 
 
 Before you can verify data transfer with this method, ``mongosync`` must be in 
 the ``COMMITTED`` state.
 
 .. _c2c-index-comparison: 
 
-Index Comparison
-----------------
+Comparing Indexes
+-----------------
 
-To verify the transfer of indexes, run the :method:`db.collection.getIndexes` 
-method on the source and destination clusters and compare the results. 
+To verify the transfer of indexes, run :method:`db.collection.getIndexes` 
+on the source and destination clusters and compare the results. 
 
 .. _c2c-metadata-comparison:
 
-Metadata Comparison
--------------------
+Comparing Metadata
+------------------
 
-To verify the transfer of metadata, run the :method:`db.getCollectionInfos` method
+To verify the transfer of metadata, run :method:`db.getCollectionInfos`
 on the source and destination clusters and compare the results.
 
 .. _c2c-shardkey-comparison: 
 
-Shard Key Comparison
+Comparing Shard Keys
 --------------------
 
 To verify the transfer of shard keys to a synced collection, run a query on the