DOCSP-33885 Fix Server Version Requirement References (#200)

* DOCSP-33885 Fix Server Version Requirement References

* *

* typos

* AB feedback

* AV feedback

* *

Author: ajhuh-mdb

source/includes/cross-version-sync.rst

@@ -1,11 +1,11 @@
-Starting in 1.7.0, ``mongosync`` can perform a cross version migration
+Starting in 1.7.0, ``mongosync`` can perform a cross-version migration
 from a lower major version source cluster to a higher major version
 destination cluster. You can migrate up to two major versions ahead. For
 example, you can synchronize a cluster running MongoDB 6.0 with a
 cluster running 7.0.
 
-Cross version migration requires additional preparation and
-configuration when migrating from a pre-6.0 release. To perform a cross
-version migration from a pre-6.0 version of the MongoDB Server using
+Cross-version migration requires additional preparation and
+configuration when migrating from a pre-6.0 release. To perform a cross-version 
+migration from a pre-6.0 version of the MongoDB Server using
 ``mongosync``, please `contact <https://mongodb.com/contact>`__ your
 account team to inquire about Professional Services.

source/includes/fact-minimum-fcv.rst

@@ -0,0 +1,2 @@
+The minimum supported server :manual:`feature compatibility version <view-fcv>` 
+is 6.0.

source/includes/fact-minimum-server-version-support.rst

@@ -0,0 +1 @@
+The minimum supported server versions of MongoDB are 6.0.8 and 7.0.0.

source/quickstart.txt

@@ -41,7 +41,7 @@ Follow the instructions below to setup {+c2c-product-name+}.
    .. step:: Define a source and a destination cluster
 
       If you already have a MongoDB cluster, either self-managed or
-      hosted in :atlas:`MongodDB Atlas </getting-started?jmp=docs>`, 
+      hosted in :atlas:`MongoDB Atlas </getting-started?jmp=docs>`, 
       use that cluster as the source cluster. If you don't have a
       cluster to work with, you will need to create one.
 
@@ -50,14 +50,10 @@ Follow the instructions below to setup {+c2c-product-name+}.
       sharded cluster, or between sharded clusters, see:
       :ref:`c2c-sharded-clusters`.
 
-      The source and destination clusters must be:
-      
-      - at least MongoDB 6.0.
-      - at least Feature Compatibility Version 6.0
-
-      .. include:: /includes/version-sync-limitation.rst
+      .. seealso::
 
-      .. include:: /includes/cross-version-sync.rst
+         For more information on MongoDB server version compatibility or 
+         cross-version migrations, see :ref:`c2c-server-version-compatibility`.
 
       The number of nodes in the destination replica set does not have
       to equal the number of nodes in the source replica set.

source/reference/limitations.txt

@@ -24,35 +24,11 @@ Limitations
 General Limitations
 -------------------
 
-- The minimum supported server versions are MongoDB 6.0.8 and 7.0.0.
+.. note:: 
 
-- .. include:: /includes/fact-minimum-versions.rst
+  For information on MongoDB server compatility, see 
+  :ref:`c2c-server-version-compatibility`.
 
-- ``mongosync`` doesn't support MongoDB rapid releases such as 6.1 or
-  6.2. The minimum supported server version is MongoDB 6.0.5.
-  For more information on MongoDB versioning, see
-  :ref:`release-version-numbers`.
-- In ``mongosync`` versions earlier than 1.7.0, the source and
-  destination clusters must have the same major and minor release
-  version, but can have different patch releases.
-
-  For example:
-
-  - ``mongosync`` can sync from a MongoDB 6.0.8 source cluster to a
-    destination cluster using MongoDB 6.0.9. This is because the patch
-    releases have the same major version.
-  - ``mongosync`` doesn't support a sync from a MongoDB 6.0.9 source
-    cluster to a destination cluster using MongoDB 7.0.0. This is
-    because the releases have different major versions.
-
-- In ``mongosync`` versions earlier than 1.7.0, the source and
-  destination clusters must have the same :dbcommand:`Feature
-  Compatibility Version <setFeatureCompatibilityVersion>`.
-
-- .. include:: /includes/cross-version-sync.rst
-
-- The minimum supported :dbcommand:`Feature Compatibility Version
-  <setFeatureCompatibilityVersion>` is 6.0.
 - The destination cluster must be empty.
 - ``mongosync`` doesn't validate that the clusters or the environment
   are properly configured. 

source/reference/versioning.txt

@@ -39,35 +39,30 @@ asked to upgrade in order to receive support.
 MongoDB Server Version Compatibility and Support
 ------------------------------------------------
 
-{+c2c-product-name+} supports the following versions of MongoDB Server:
+Before you run {+c2c-product-name+}, consider the following MongoDB server 
+version limitations and requirements: 
 
+- .. include:: /includes/fact-minimum-server-version-support.rst
 
-.. list-table::
-   :header-rows: 1
-   :stub-columns: 1
+- ``mongosync`` doesn't support MongoDB rapid releases, such as 6.1 or 6.2.
 
-   * - ``mongosync`` Version
-     - MongoDB Server Version
+- .. include:: /includes/fact-minimum-fcv.rst 
 
-   * - 1.6.0
-     - 7.0.x
+Synchronize Data Between Clusters Running Older MongoDB Server Versions
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-   * - 1.0.0
-     - 6.0.x
+.. include:: /includes/fact-minimum-versions.rst
 
-Considerations
---------------
 
-{+c2c-product-name+} has the following version related considerations:
+Synchronize Data Between Clusters with Different MongoDB Server Major Versions
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Same Server Version
-~~~~~~~~~~~~~~~~~~~
+.. include:: /includes/cross-version-sync.rst
 
-{+c2c-product-name+} only supports syncing between the same version of
-MongoDB Server. The major and minor :ref:`server version numbers
-<release-version-numbers>` must be the same on both clusters.
-Starting in ``mongosync`` 1.6.0, the source and destination cluster
-can use different patch releases of the same major and minor version.
+Version-Related Considerations
+------------------------------
+
+{+c2c-product-name+} has the following version related considerations:
 
 Support Lifecycle 
 ~~~~~~~~~~~~~~~~~
@@ -214,7 +209,7 @@ Major Releases
 
 - Changes that break compatibility with a supported version of MongoDB
   Server.
-- Dropping a version of the REST API. ``mongosync`` may dropping all
+- Dropping a version of the REST API. ``mongosync`` may drop all
   older endpoints in favor of a new version of the API. There will never
   be any other types of backwards incompatible changes in the REST API.
 - Removing support for a previously supported MongoDB Server feature if