DOCSP-25489-harmonize-syncing-synchronizing (#93)

Author: Dave Cuthbert

source/includes/fact-oplog-background.rst

@@ -2,6 +2,6 @@ The :term:`oplog` in the source cluster must be large enough to track
 events that happen during the time it takes to complete the initial
 sync to the destination cluster.
 
-If you anticipate synchronizing a large data set, or if you plan to
-pause synchronization for an extended period of time, increase the size
-of the replica set ``oplog`` in the source cluster.
+If you anticipate syncing a large data set, or if you plan to pause
+synchronization for an extended period of time, increase the size of the
+replica set ``oplog`` in the source cluster.

source/multiple-mongosyncs.txt

@@ -171,7 +171,7 @@ The ``mongosync`` instances do not aggregate progress information
 across shards. To review synchronization progress for a particular
 shard, use ``curl`` or another HTTP client to issue the
 :ref:`progress <c2c-api-progress>` command to the ``mongosync``
-instance synchronizing that shard.
+instance syncing that shard.
 
 .. code-block:: shell
 
@@ -207,9 +207,9 @@ Resume Synchronization
 ----------------------
 
 If one or more ``mongosync`` instances are paused, you can use the
-:ref:`resume <c2c-api-resume>` command to resume synchronizing. Run a
+:ref:`resume <c2c-api-resume>` command to resume syncing. Run a
 separate ``resume`` command against each paused ``mongosync`` instance
-to continue synchronizing.
+to continue syncing.
 
 Use ``curl`` or another HTTP client to issue the :ref:`resume
 <c2c-api-resume>` command to each ``mongosync`` instance.

source/quickstart.txt

@@ -25,7 +25,7 @@ the rest of the {+c2c-product-name+} documentation.
 Setup
 -----
 
-{+c2c-product-name+} synchronizes data between two clusters. To run
+{+c2c-product-name+} syncs data between two clusters. To run
 ``mongosync``, you will need to: 
 
 #. Define a source and a destination cluster.
@@ -192,16 +192,16 @@ The command interface for ``mongosync`` is an HTTP server that
 publishes an HTTP API. To control ``mongosync``, use the API endpoints.
 
 The :ref:`start <c2c-api-start>` command initiates data synchronization.
-To start synchronizing, use ``curl`` or a similar program to issue the
+To start syncing, use ``curl`` or a similar program to issue the
 :ref:`start <c2c-api-start>` command:
 
 .. literalinclude:: /includes/api/requests/start.sh
    :language: shell
 
 Once started, ``mongosync`` will synchronize existing data on the
 source cluster with the destination cluster. After the initial sync has
-completed, new writes to the source cluster will be synchronized with
-the destination cluster.
+completed, new writes to the source cluster will be synced with the
+destination cluster.
 
 The API documentation provides details on using the following endpoints:
 

source/reference/limitations.txt

@@ -80,14 +80,14 @@ Sharded Clusters
   - Replica set to sharded cluster.
   - Sharded cluster to replica set.
   - Unequal numbers of source and destination shards.
-- The :dbcommand:`movePrimary` command cannot be used to reassign the primary
-  shard while syncing
+- The :dbcommand:`movePrimary` command cannot be used to reassign the
+  primary shard while syncing.
 - There is no replication for zone configuration. ``mongosync``
   replicates data, it does not inherit zones.
-- Shards cannot be added or removed while synchronizing.
-- Only indexes which exist on all shards are synchronized.
+- Shards cannot be added or removed while syncing.
+- Only indexes which exist on all shards are synced.
 - The shard key cannot be :ref:`refined <shard-key-refine>` while
-  synchronizing.
+  syncing.
 - The shard key cannot be modified using :dbcommand:`reshardCollection`
   during syncing.
 - The maximum number of :ref:`shard key indexes

source/reference/mongosync.txt

@@ -114,9 +114,9 @@ Behavior
 Commit
 ~~~~~~
 
-To stop synchronizing, use the :ref:`commit <c2c-api-commit>` command
-on the destination cluster to convert indexes and finalize the changes.
-While ``commit`` is running:
+To stop syncing, use the :ref:`commit <c2c-api-commit>` command on the
+destination cluster to convert indexes and finalize the changes. While
+``commit`` is running:
 
 - Writes are blocked on the source cluster.
 - Writes are blocked on the destination cluster until ``mongosync``
@@ -134,7 +134,7 @@ To monitor the ``commit`` process, use the :ref:`progress
 Cluster Independence
 ~~~~~~~~~~~~~~~~~~~~
 
-``mongosync`` synchronizes collection data between a source cluster and
+``mongosync`` syncs collection data between a source cluster and
 destination cluster. ``mongosync`` does not synchronize :ref:`users
 <users>` or :ref:`roles <built-in-roles>`. As a result, you can create
 users with different access permissions on each cluster.

source/reference/oplog-sizing.txt

@@ -47,7 +47,8 @@ Estimate ``oplog`` Size Needed for Initial Sync
       To gather performance data while synching, start the sync process
       and monitor how fast data is transferred between clusters.
 
-      To start syncing, run the :ref:`/start <c2c-api-start>` command.
+      To start syncing, run the :ref:`/start <c2c-api-start>`
+      command.
 
       To get the ``copy_rate``: