(DOCSP-44663) Changes related to v6.0 are minimal here due to no support for such migrations (v6.0) in OM-v7.0-backport (492) (#572)

# Backport

This will backport the following commits from `master` to `v7.0`:
- [(DOCSP-44663) Changes related to v6.0 are minimal here due to no
support for such migrations (v6.0) in OM
(#492)](10gen/docs-ops-manager#492)

<!--- Backport version: 9.6.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

Author: JuliaMongo

snooty.toml

@@ -77,7 +77,8 @@ bagent = "Backup"
 bagent-version = "7.6.0.1059"
 bagent-version-cloud = "7.6.0.1059"
 bagent-version-opsmgr = "6.8.6.1013"
-c2c-version = "6.0.8"
+c2c-version = "6.0.17"
+c2c-version-7 = "7.0.13"
 cloudmgr-url = "cloud.mongodb.com"
 fcv-list = "**5.0**, **6.0**, and **7.0**"
 service = "Atlas"

source/migration.txt

@@ -14,11 +14,11 @@ Migrate Deployments
 
 .. _c2c-based-live-migration-choices:
 
-MongoDB {+c2c-version+} and Later: Live Migrate to Atlas
-----------------------------------------------
+MongoDB {+c2c-version+}+ or {+c2c-version-7+}+: Live Migrate to Atlas
+-----------------------------------------------------------------------
 
-If both the source and destination clusters are running MongoDB {+c2c-version+} or
-later, you can migrate your data from a source cluster into a destination
+If both the source and the destination clusters are running MongoDB {+c2c-version+}+
+or {+c2c-version-7+}+, you can migrate your data from a source cluster into a destination
 MongoDB cluster in |service-short| using one of the following types of
 guided live migration in the |service| UI:
 
@@ -29,7 +29,7 @@ The choice between push and pull live migrations depends on whether the
 network for your deployment allows flexibility in ingress rules and allows
 access through the firewall.
 
-In addition, you can use these migration methods for MongoDB {+c2c-version+} and later
+In addition, you can use these migration methods for MongoDB {+c2c-version+}+ or {+c2c-version-7+}+
 deployments:
 
 - If your data is in a MongoDB deployment and you don't have access to the :manual:`oplog </reference/glossary/#std-term-oplog>`,

source/tutorial/migrate-to-atlas.txt

@@ -46,12 +46,13 @@ Supported Platforms
 The list of supported platforms depends on which type of live migration
 you are using:
 
-- For live migrations of MongoDB 6.0.5+ clusters monitored by |cloud-short| to |service-short|,
+- For live migrations of MongoDB {+c2c-version+}+ or {+c2c-version-7+}+
+  clusters monitored by |cloud-short| to |service-short|,
   see `mongosync platforms <https://www.mongodb.com/docs/cluster-to-cluster-sync/current/installation>`__ to review
   the list of supported platforms for the migration host.
 
-- For live migrations of source clusters running MongoDB versions 4.4.x
-  or 5.0.x (FCV), the live migration to |service-short|
+- For live migrations of source clusters running MongoDB earlier than
+  {+c2c-version+}, the live migration to |service-short|
   :ref:`is supported <live-migration-host-supported-platforms>` for all
   platforms on which you can provision a migration host.
 

source/tutorial/provision-migration-host.txt

@@ -60,8 +60,8 @@ following supported platforms. The platforms depend on the migration tool
 that the migration host will be running to facilitate the migration.
 
 - Migration host for live migrations (push) of source deployments of MongoDB
-  versions 5.0+ but not 6.0 (FCV) that you add to monitoring in |cloud-short|,
-  where the migration host runs mongomirror:
+  earlier than {+c2c-version+} that you add to monitoring in |cloud-short|,
+  where the migration host runs ``mongomirror``:
 
   .. include:: /includes/list-tables/only-v5-agent-platform-support-table.rst
 
@@ -83,7 +83,8 @@ that the migration host will be running to facilitate the migration.
 
      translators-connectors-releases.s3.amazonaws.com
 
-- Migration host for live migrations (push) of MongoDB 6.0.5+ source
+- Migration host for live migrations (push) of MongoDB {+c2c-version+}+ or
+  {+c2c-version-7+}+ source
   deployments monitored in |cloud-short|, where the migration host runs `mongosync <https://www.mongodb.com/docs/cluster-to-cluster-sync/current/reference/mongosync/>`__:
 
   The migration host must use a 64-bit CPU architecture and one of the
@@ -105,11 +106,11 @@ You may also need to provision additional storage for the
 :setting:`cloudMigrationOplogPath` option described in the following
 procedure.
 
-- MongoDB {+c2c-version+}+. For the migration host that runs ``mongosync`` to
+- MongoDB {+c2c-version+}+ or {+c2c-version-7+}+. For the migration host that runs ``mongosync`` to
   facilitate push live migrations, use an instance
   with a minimum of 8 CPUs and 24 GB of RAM.
 
-- MongoDB versions 5.0+ but not 6.0 (FCV). For the migration host that runs
+- MongoDB versions earlier than {+c2c-version+}. For the migration host that runs
   ``mongomirror`` to facilitate push live migrations, use a host
   with 2-4 CPU cores and 4-8 GB of RAM to migrate a replica set.
   Use an instance with 2-4 CPU cores per shard to migrate a sharded cluster.