DOCS-153 clarification

Author: Sam Kleinman

source/administration/sharding-architectures.txt

@@ -166,7 +166,5 @@ potential failure scenarios and available resolutions:
   splits <sharding-procedure-create-split>`. Replace the config server
   as soon as possible. If all multiple config databases become
   unavailable, the cluster can become inoperable.
-  
-  .. note::
-     
-     All config servers must be running when you first set up a shard cluster.
+
+  .. include:: /includes/note-config-server-startup.rst

source/administration/sharding.txt

@@ -59,10 +59,8 @@ more detail or use the following procedure as a quick starting point:
    :doc:`command line </reference/mongod>` and :doc:`configuration
    file </reference/configuration-options>` options are available for config
    server instances.
-   
-.. note::
 
-   All config servers must be running when you first set up a shard cluster.
+   .. include:: /includes/note-config-server-startup.rst
 
 #. Start a :program:`mongos` instance issuing the following command:
 
@@ -893,7 +891,7 @@ For redundancy, all production :term:`shard clusters <shard cluster>` should
 deploy three config servers processes on three different machines.
 
 Do not use only a single config server for production deployments.
-Consider deploying a single config server only for testing.
+Only use a single config server deployments for testing.
 You should upgrade to three config servers immediately if you are
 shifting to production.
 The following process shows how to upgrade from one to

source/includes/note-config-server-startup.rst

@@ -0,0 +1,4 @@
+.. note::
+
+   All config servers must be running and available when you first initiate
+   a :term:`shard cluster`.