added comments regarding premature optimization and cleaned up examples in Requirements

Author: gwaldo

source/tutorial/deploy-replica-set.txt

@@ -20,15 +20,13 @@ sufficient redundancy to survive most network partitions and other
 system failures. A replica set of this also size provides sufficient
 capacity to host many distributed read operations. 
 
-.. Whoa, Whoa, Whoa... Is 10gen really recommending against redundancy?
-.. As a SysAd, I personally disagree with this notion; what I typically
-.. recommend is absolutely to implement a basic ReplSet in Prod, but not
-.. get into Sharding unless you find that it's really necessary.
-
 While MongoDB's replica set functionality provides a great deal of flexibility 
 and specific definable node behaviors or types, it's best to avoid this
 additional complexity until your application requires the functionality.
-
+Until your circumstances require it, It is strongly recommended that 
+you avoid using the additional configuration options (delayed nodes, 
+hidden nodes, voting options, etc) unless your circumstances warrant 
+the additional complexity.  Avoid premature optimization.
 
 
 Requirements
@@ -39,9 +37,10 @@ of :program:`mongod`. For development systems you may run all three
 instances of the :program:`mongod` process on a local system. (e.g. a 
 laptop) or within a virtual instance. For production environments, you 
 should endeavor to maintain as much separation between the nodes.  For
-instance: Deploy replica set members on distinct hardware, and on 
-systems that draw power from different circuits, to the greatest extent 
-possible.
+example, when using VMs in Production, each node should live on 
+separate host servers, served by redundant power circuits, and with
+redundant network paths.
+
 
 Procedure
 ---------
@@ -85,7 +84,7 @@ following options for more information: :option:`--port <mongod --port>`,
    <mongod --bind_ip>` option.
 
 Connect to the mongod instance with the :program:`mongo` shell to the 
-first host. If you're accessing this command remotely, replace 
+first host. If you're running this command remotely, replace 
 "localhost" with the approriate hostname.  Open a new terminal session
 and enter the following: ::