DOCSP-23037 supported instance types (#21)

* DOCSP-23037 supported instance types

* Staging fixes

* Staging fixes, file cleanup

* Reveiw feedback

* Review feedback

* layout test

Author: Dave Cuthbert

source/reference/api/pause.txt

@@ -4,6 +4,8 @@
 ``pause``
 =========
 
+.. include:: /includes/preview-warning
+
 .. default-domain:: mongodb
 
 .. contents:: On this page

source/reference/api/resume.txt

@@ -4,6 +4,8 @@
 ``resume``
 ==========
 
+.. include:: /includes/preview-warning
+
 .. default-domain:: mongodb
 
 .. contents:: On this page

source/reference/mongosync.txt

@@ -19,11 +19,21 @@
 Description
 -----------
 
-The ``mongosync`` binary is the primary process used in Cluster-to-Cluster Sync.
-It migrates data from one cluster to another and can keep the clusters
-in continuous sync.
+The ``mongosync`` binary is the primary process used in
+{+c2c-product-name+}. ``mongosync`` migrates data from one cluster to
+another and can keep the clusters in continuous sync. 
 
-This document provides a complete overview of all command-line options.
+This document provides a complete overview of the ``mongosync`` command
+line options.
+
+.. note::
+
+   - Both the source cluster and destination cluster must use MongoDB
+     6.0 or later.
+   - ``mongosync`` supports replica sets and sharded clusters.
+   - Standalone MongoDB instances are not supported. :ref:`Convert the
+     standalone instance <server-replica-set-deploy-convert>` to a
+     replica set before using {+c2c-product-name+}. 
 
 Options
 -------
@@ -34,39 +44,30 @@ Global Options
 .. option:: --cluster0 <URI>
 
    Sets the :ref:`connection URI <mongodb-uri>` for the first cluster.
-   The first cluster can serve as either the source cluster or the destination 
-   cluster in the sync process.
-
-   .. note::
- 
-      The cluster must use MongoDB 6.0 or later.
-
+   The first cluster can serve as either the source or the destination
+   in the sync process. Designate the source and destination clusters
+   in the call to the :ref:`c2c-api-start` API endpoint.
 
    For more information on connecting ``mongosync``, see
    :ref:`Connections <c2c-connecting>`.
 
-
 .. option:: --cluster1 <URI>
 
    Sets the :ref:`connection URI <mongodb-uri>` for the second cluster.
-   The second cluster can serve as either the source cluster or the destination 
-   cluster in the sync process.
-
-   .. note::
-
-      The cluster must use MongoDB 6.0 or later.
-
+   The second cluster can serve as either the source or the destination
+   in the sync process. Designate the source and destination clusters
+   in the call to the :ref:`c2c-api-start` API endpoint.
 
    For more information on connecting ``mongosync``, see
    :ref:`Connections <c2c-connecting>`.
 
-
 .. option:: --verbosity <level>
 
    *Default*: ``INFO``
 
-   Sets the verbosity level to use in log messages.  Cluster-to-Cluster Sync logs
-   all messages at the specified level as well as any messages at less severe levels.
+   Sets the verbosity level to use in log messages.
+   {+c2c-product-name+} logs all messages at the specified level and
+   any messages at lower levels.
 
    The ``--verbosity`` option supports the following values:
 
@@ -78,46 +79,43 @@ Global Options
    - ``FATAL``
    - ``PANIC``
 
-
 .. option:: --logPath <DIR>
 
-   Sets the path to the log directory. Cluster-to-Cluster Sync writes logs to
-   files in this directory.
-
+   Sets the path to the log directory. {+c2c-product-name+} writes logs
+   to files in this directory.
 
 .. option:: --port
 
    *Default*: ``27182``
 
-   Sets the port used by the HTTP server for the Cluster-to-Cluster Sync REST API.
-
+   Sets the port used by the HTTP server for the {+c2c-product-name+}
+   REST API.
 
 .. option:: --id <ID>
 
    Sets an identifier for the ``mongosync`` instance.
 
-   Use this option when running multiple instances of ``mongosync`` on a sharded
-   cluster, to synchronize the shards individually.  The ``--id`` option must
-   correspond to the shard ID of the shard it
-   syncs.  To find the shard ID, use the :dbcommand:`listShards` command.
+   Use this option when running multiple instances of ``mongosync`` on
+   a sharded cluster, to synchronize the shards individually. 
+   
+   The ``--id`` option must correspond to the shard ID of the shard it
+   syncs.  To find the shard ID, use the :dbcommand:`listShards`
+   command.
 
 .. option:: --config <filename>
 
    Sets the path to the configuration file.
 
    For more information, see :ref:`c2c-mongosync-config`.
 
-
 .. option:: --version, -v
 
    Prints ``mongosync`` version information to stdout.
 
-
 .. option:: --help, h
 
    Prints usage information to stdout.
 
-
 Behavior
 --------
 
@@ -126,16 +124,16 @@ Behavior
 Configuration File
 ~~~~~~~~~~~~~~~~~~
 
-Options for ``mongosync`` can be set in a YAML configuration file, specified
-using the :option:`--config` option.  For example:
+Options for ``mongosync`` can be set in a YAML configuration file. Use
+the :option:`--config` option. To specify the path to the configuration
+file. For example:
 
 .. code-block:: yaml
 
    # Cluster Configuration
    cluster0: "mongodb://192.0.2.10:27017,192.0.2.11:27017,192.0.2.12:27017"
    cluster1: "mongodb://192.0.2.20:27017,192.0.2.21:27017,192.0.2.22:27017"
 
-
 Examples
 --------
 
@@ -165,4 +163,14 @@ Examples
    .. code-block:: json
       :copyable: false
 
-      { "success": true }
+      { "success": true }
+
+
+.. code-block: shell
+
+   12345 67890 12345 67890 12345 67890 12345 67890 12345 67890 12345 67890 12345 67890 12345 67890
+
+.. code-block: shell
+   :copyable: false
+   
+   12345 67890 12345 67890 12345 67890 12345 67890 12345 67890 12345 67890 12345 67890 12345 67890