DOCSP-23928 Fixes relevant limitations (#79)

* DOCSP-23928 Fixes relevant limitations

* DOCSP-23928 Fix per Lingzhi

* DOCSP-23928 Fixes per Ashley

Author: kennethdyer

source/reference/limitations.txt

@@ -37,11 +37,8 @@ General Limitations
 - The source and destination clusters must have the same Feature
   Compatibility Version.
 - The destination cluster must be empty.
-- DDL operations are currently not supported during syncing. 
 - ``mongosync`` does not validate that the clusters or the environment
   are properly configured. 
-- The primary shard cannot be :dbcommand:`reassigned <movePrimary>`
-  while syncing.
 - Other clients must not write to the destination cluster while
   ``mongosync`` is running.
 - If write blocking is disabled, the client must :ref:`prevent writes
@@ -52,7 +49,7 @@ General Limitations
 - Network compression is not supported.
 - :dbcommand:`applyOps` operations from the source cluster are not
   supported.
-- The :data:`system.js <<database>.system.js>` collection is not
+- :ref:`system.* collections <metadata-system-collections>` are not
   replicated.
 - Documents that have dollar (``$``) prefixed field names are not
   supported. See :ref:`Field Names with Periods and Dollar Signs
@@ -73,7 +70,6 @@ discuss your requirements.
 Unsupported Collection Types
 ----------------------------
 
-- Collections with collation are currently not supported.
 - Capped collections are currently not supported.
 - Time-series collections are not supported.
 
@@ -88,7 +84,8 @@ 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
 - There is no replication for zone configuration. ``mongosync``
   replicates data, it does not inherit zones.
 - Shards cannot be added or removed while synchronizing.