Added in remove balance window (DOCS-453) and fixing rendering changes

Author: Andrew Leung

source/administration/sharding.txt

@@ -570,7 +570,7 @@ block until the migration is complete.
 
    :dbcommand:`moveChunk` command accepts parameter:
    ``_secondaryThrottle``, when set to ``true``, MongoDB will ensure
-   secondary members have replicated changes before allowing new chunk
+   :term:`secondary` members have replicated changes before allowing new chunk
    migrations to occur.
 
 .. note::
@@ -698,6 +698,13 @@ be able to migrate chunks:
 
       db.settings.update({ _id : "balancer" }, { $set : { activeWindow : { start : "23:00", stop : "6:00" } } }, true )
 
+To turn off the balancing window:
+
+  .. code-block:: javascript
+
+     use config
+     db.settings.update({ _id : "balancer" }, { $unset : { activeWindow : true })
+
 .. note::
 
    The balancer window must be sufficient to *complete* the migration

source/core/sharding-internals.txt

@@ -461,12 +461,12 @@ evenly among shards. Migrations may be either:
 - Manual. In these migrations you must specify the chunk that you want
   to migrate and the destination shard. Only migrate chunks manually
   after initiating sharding, to distribute data during bulk inserts,
-  or if the cluster becomes uneven. See :doc:`Migrating Chunks
+  or if the cluster becomes uneven. See :ref:`Migrating Chunks
   <sharding-balancing-manual-migration>` for more details.
 
 - Automatic. The balancer process handles most migrations when
   distribution of chunks between shards becomes uneven. See
-  :doc:`Migration Thresholds <sharding-migration-thresholds>` for more
+  :ref:`Migration Thresholds <sharding-migration-thresholds>` for more
   details.
 
 All chunk migrations use the following procedure: 
@@ -494,5 +494,5 @@ All chunk migrations use the following procedure:
 
 When the ``_secondaryThrottle`` option is set ``true`` for
 :dbcommand:`moveChunk` or the :term:`balancer`, MongoDB will ensure
-secondary members have replicated changes before allowing new chunk
+:term:`secondary` members have replicated changes before allowing new chunk
 migrations to occur.

source/reference/command/moveChunk.txt

@@ -11,13 +11,13 @@ moveChunk
    :method:`sh.moveChunk()` function in the :program:`mongo` shell if
    you must move a chunk manually.
 
-   :option _secondaryThrottle: Optional. The default setting is
-                               ``false``. If ``true`` this will
-                               specify that primary shard members
-                               should wait for its secondary shard
-                               members to replicate chunk data updates
-                               before allowing new chunk migrations to
-                               occur.
+   :option _secondaryThrottle: The default setting is ``false``. If
+                               ``true`` this will specify that
+                               :term:`primary` :term:`shard` members
+                               should wait for its :term:`secondary`
+                               shard members to replicate :term:`chunk` data
+                               updates before allowing new chunk
+                               migrations to occur.
 
 			       For details on chunk migrations, please
                                see: :ref:`Sharding Internals - Chunk