diff --git a/source/reference/verification.txt b/source/reference/verification.txt
index 38e09f565..9d24a5486 100644
--- a/source/reference/verification.txt
+++ b/source/reference/verification.txt
@@ -44,8 +44,8 @@ source to the destination cluster.
      - Starting in 1.9, ``mongosync`` includes an embedded
        verifier, which runs a series of verification checks on
        the source and destination clusters to confirm that the
-       migration was successful. This is the preferred
-       verification method for deployments that meet the
+       migration was successful. **This is the preferred
+       verification method for deployments that meet the**
        :ref:`requirements <c2c-verify-embedded-limitations>`.
 
        When the ``mongosync`` process starts, it prompts the
@@ -159,9 +159,6 @@ source to the destination cluster.
        comparing documents, views, and indexes to confirm the
        sync was successful.
 
-       Migration Verifier is an experimental and unsupported
-       tool.
-
 The specific method you use to verify your data depends on your
 application workload and the complexity of the data.
 
diff --git a/source/reference/verification/verifier.txt b/source/reference/verification/verifier.txt
index 9e1095f5b..aff724058 100644
--- a/source/reference/verification/verifier.txt
+++ b/source/reference/verification/verifier.txt
@@ -33,8 +33,6 @@ About This Task
    Migration Verifier does not support DDL operations. Do not run any DDL 
    operations on the source cluster while verifying data with Migration Verifier. 
 
-Migration Verifier is an experimental and unsupported tool.
-
 For installation instructions and usage limitations, see
 `GitHub <https://github.com/mongodb-labs/migration-verifier>`__.