tweaks

Author: mayaraman19

source/includes/fact-mongosync-balancer.rst

@@ -1,21 +1,21 @@
 .. important::
 
    If the source or destination cluster is a sharded cluster
-   and you are not running ``mongosync`` with namespace filtering,
+   and you are not running ``mongosync`` with :ref:`namespace
+   filtering <c2c-filtered-sync>`,
    you must disable the source cluster's balancer
    by running the :dbcommand:`balancerStop` command and waiting 15 minutes
    for the command to complete.
 
    If the source or destination cluster is a sharded cluster and you
-   are running ``mongosync`` with :ref:`namespace
-   filtering <c2c-filtered-sync>`, you can enable the source cluster's
+   are running ``mongosync`` with namespace filtering, you can enable the source cluster's
    balancer overall but you must disable it for 
    all collections within the namespace filter. 
    See :ref:`disabling-balancer-filtered`. You can also disable
    the source cluster's balancer.
 
    You must always disable the balancer on a sharded destination
-   cluster.
+   cluster by using :dbcommand:`balancerStop`.
 
    During migration, do not run the :dbcommand:`moveChunk` or 
    :dbcommand:`moveRange` commands. If you have enabled the source cluster's

source/reference/limitations.txt

@@ -125,21 +125,21 @@ Sharded Clusters
      Indexes Across Shards <manage-indexes-find-inconsistent-indexes>`.
 
 - If the source or destination cluster is a sharded cluster
-  and you are not running ``mongosync`` with namespace filtering,
+  and you are not running ``mongosync`` with :ref:`namespace
+  filtering <c2c-filtered-sync>`,
   you must disable the source cluster's balancer
   by running the :dbcommand:`balancerStop` command and waiting 15 minutes
   for the command to complete.
 
   If the source or destination cluster is a sharded cluster and you
-  are running ``mongosync`` with :ref:`namespace
-  filtering <c2c-filtered-sync>`, you can enable the source cluster's
+  are running ``mongosync`` with namespace filtering, you can enable the source cluster's
   balancer overall but you must disable it for 
   all collections within the namespace filter. 
   See :ref:`disabling-balancer-filtered`. You can also disable
   the source cluster's balancer.
 
   You must always disable the balancer on a sharded destination
-  cluster.
+  cluster by using :dbcommand:`balancerStop`.
 
 - If you have enabled the source cluster's
   balancer, but disabled it for collections within the namespace

source/reference/mongosync/mongosync-behavior.txt

@@ -107,13 +107,15 @@ preserve the source cluster's sharding configuration.
 Disabling Balancer for Collections in Filtered Sync
 '''''''''''''''''''''''''''''''''''''''''''''''''''
 
-If you want to enable the balancer for collections that are not
-included in the namespace filter, use the following instructions before
+If you are using a :ref:`namespace filter <c2c-filtered-sync>`
+and want to enable your source cluster's balancer,
+use the following instructions before
 starting ``mongosync``. These instructions allow you to enable the balancer 
 for the source cluster and disable the balancer for collections 
 within the namespace filter.
 
 .. procedure::
+   :style: normal
 
    .. step:: Enable the balancer for the source cluster.
 
@@ -126,7 +128,7 @@ within the namespace filter.
       Disable the balancer for each collection within the
       namespace filter by running the :dbcommand:`setAllowMigrations` command:
 
-      .. code-block:: shell
+      .. code-block:: javascript
 
         db.adminCommand(
           {