Balancer needs to be disabled

source/tutorial/schedule-backup-window-for-sharded-clusters.txt

@@ -11,14 +11,14 @@ In a :term:`sharded cluster`, the balancer process is responsible for
 distributing sharded data around the cluster, so that each
 :term:`shard` has roughly the same amount of data.
 
-However, when creating backups from a sharded cluster it's important
+However, when creating backups from a sharded cluster it is important
 that you disable the balancer while taking backups to ensure that no
 chunk migrations affect the content of the backup captured by the
 backup procedure. Using the procedure outlined in the section
-:ref:`sharding-balancing-disable-temporally` you can stop the balancer
-process temporarily using a manual process. As an alternative you can
+:ref:`sharding-balancing-disable-temporally` you can manually stop the 
+balancer process temporarily. As an alternative you can
 use this procedure to define a balancing window so that the balancer
-is always during your automated backup operation.
+is always disabled during your automated backup operation.
 
 Procedure
 ---------
@@ -32,9 +32,9 @@ following command:
    use config
    db.settings.update( { _id : "balancer" }, { $set : { activeWindow : { start : "6:00", stop : "23:00" } } }, true )
 
-This operation configures the balancer to run between 6:00 am and
+This operation configures the balancer to run between 6:00am and
 11:00pm, server time. Schedule your backup operation to run *and
-complete* in this time. Ensure that the backup can complete during the
-window when the balancer is running *and* that the balancer can
-effectively balance the collection among the shards in the window
-allotted to each.
+complete* outside of this time. Ensure that the backup can complete 
+outside the window when the balancer is running *and* that the 
+balancer can effectively balance the collection among the shards 
+in the window allotted to each.