DOCSP-23870 mongosync atlas (#89)

* DOCSP-23870-mongosync-atlas

* DOCSP-23870-mongosync-atlas

* DOCSP-23870-mongosync-atlas

* DOCSP-23870-mongosync-atlas

* DOCSP-23870-mongosync-atlas

* DOCSP-23870-mongosync-atlas

* DOCSP-23870-mongosync-atlas

* DOCSP-23870-mongosync-atlas

* DOCSP-23870-mongosync-atlas

Co-authored-by: jason-price-mongodb <[email protected]>

Author: jason-price-mongodb

source/includes/example-connect.rst

@@ -50,3 +50,25 @@ following command on one line:
                        clusterTwo02.fancyCorp.com:20020,
                        clusterTwo03.fancyCorp.com:20020
 
+Atlas clusters require TLS/SSL connections. To use ``mongosync`` with
+Atlas clusters, you add the :urioption:`ssl=true <ssl>` option. For
+example:
+
+.. code-block:: shell
+
+   mongosync \
+      --cluster0 'mongodb://clusterAdmin:[email protected]:20020,clusterOne02.fancyCorp.com:20020,clusterOne03.fancyCorp.com:20020/?ssl=true' \
+      --cluster1 'mongodb://clusterAdmin:[email protected]:20020,clusterTwo02.fancyCorp.com:20020,clusterTwo03.fancyCorp.com:20020/?ssl=true'
+
+You can also use ``mongodb+srv`` connection strings with ``mongosync``.
+You do not need to add the :urioption:`ssl=true <ssl>` option to a
+``mongodb+srv`` connection string. For example:
+
+.. code-block:: shell
+
+   mongosync \
+      --cluster0 'mongodb+srv://clusterAdmin:[email protected]:20020/' \
+      --cluster1 'mongodb+srv://clusterAdmin:[email protected]:20020/'
+
+For more details about ``mongodb+srv`` connection strings, see
+:ref:`connections-dns-seedlist`.

source/multiple-mongosyncs.txt

@@ -151,11 +151,11 @@ Use ``curl`` or another HTTP client to issue the :ref:`start
 
 .. code-block:: shell
 
-   curl monogsync01Host:27601/api/v1/start -XPOST --data \
+   curl mongosync01Host:27601/api/v1/start -XPOST --data \
         '{ "source": "cluster0", "destination": "cluster1", \
            "reversible": false, "enableUserWriteBlocking": false }'
 
-   curl monogsync02Host:27602/api/v1/start -XPOST --data \
+   curl mongosync02Host:27602/api/v1/start -XPOST --data \
         '{ "source": "cluster0", "destination": "cluster1", \
            "reversible": false, "enableUserWriteBlocking": false }'
 
@@ -175,10 +175,10 @@ instance synchronizing that shard.
 
 .. code-block:: shell
 
-   curl monogsync02Host:27602/api/v1/progress -XGET
+   curl mongosync02Host:27602/api/v1/progress -XGET
 
 This command checks the progress of the ``mongosync`` instance that is
-running on ``monogsync02Host`` and using ``port 27602`` for
+running on ``mongosync02Host`` and using ``port 27602`` for
 synchronization. To check progress on other shards, update the host and
 port number then repeat the API call to each ``mongosync`` instance.
 
@@ -194,10 +194,10 @@ HTTP client to issue the ``pause`` command to a ``mongosync`` instance.
 
 .. code-block:: shell
 
-   curl monogsync01Host:27601/api/v1/pause -XPOST --data '{}'
+   curl mongosync01Host:27601/api/v1/pause -XPOST --data '{}'
 
 This command pauses the ``mongosync`` instance that is running on
-``monogsync01Host`` and using ``port 27601`` for synchronization. To
+``mongosync01Host`` and using ``port 27601`` for synchronization. To
 pause synchronization on other shards, update the host and port number
 then repeat the API call to each ``mongosync`` instance.
 
@@ -216,10 +216,10 @@ Use ``curl`` or another HTTP client to issue the :ref:`resume
 
 .. code-block:: shell
 
-   curl monogsync01Host:27601/api/v1/resume -XPOST --data '{}'
+   curl mongosync01Host:27601/api/v1/resume -XPOST --data '{}'
 
 This command resumes synchronization on the ``mongosync`` instance that
-is running on ``monogsync01Host`` and using ``port 27601``.  To 
+is running on ``mongosync01Host`` and using ``port 27601``.  To 
 resume synchronization on other shards, update the host and port number
 then repeat the API call to each ``mongosync`` instance.
 
@@ -248,13 +248,13 @@ instance.
 .. code-block:: shell
 
    // Check progress
-   curl monogsync01Host:27601/api/v1/progress -XGET
+   curl mongosync01Host:27601/api/v1/progress -XGET
 
    // Commit 
-   curl monogsync01Host:27601/api/v1/commit -XPOST --data '{}'
+   curl mongosync01Host:27601/api/v1/commit -XPOST --data '{}'
 
 These commands only check progress and commit synchronization for the
-``mongosync`` instance that is running on ``monogsync01Host`` and using
+``mongosync`` instance that is running on ``mongosync01Host`` and using
 ``port 27601``. To synchronize all of the shards, make additional calls
 to ``progress`` and  ``commit`` on any other ``mongosync`` instances
 that may be running.
@@ -279,10 +279,10 @@ instance.
 
 .. code-block:: shell
 
-   curl monogsync01Host:27601/api/v1/reverse -XPOST --data '{}'
+   curl mongosync01Host:27601/api/v1/reverse -XPOST --data '{}'
 
 This command reverses synchronization on the ``mongosync``
-instance that is running on ``monogsync01Host`` and using ``port
+instance that is running on ``mongosync01Host`` and using ``port
 27601``. Make additional calls to ``reverse`` on any other
 ``mongosync`` instances that may be running.
 

source/quickstart.txt

@@ -157,10 +157,10 @@ Follow the instructions below to setup {+c2c-product-name+}.
 
       For more details, see :ref:`c2c-connecting`.
 
-Initialize ``monogsync``
+Initialize ``mongosync``
 ------------------------
 
-``monogsync`` must create an initial connection to the source and
+``mongosync`` must create an initial connection to the source and
 destination clusters before it can start to sync data. To create the
 initial connection, issue the following command on a single line (the
 command is reformated here for clarity):