fixes to the dev replset tutorial

Author: gwaldo

source/tutorial/deploy-replica-set.txt

@@ -17,22 +17,31 @@ Overview
 
 For most deployments, a simple 3 node replica set provides a
 sufficient redundancy to survive most network partitions and other
-system failures. A replica set of this size provides sufficient
-capacity to host many distributed read operations. 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
+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.
 
+
+
 Requirements
 ------------
 
 Three distinct systems, so that each system can run its own instance
-of :program:`mongod`. For test systems you can 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: Deploy
-replica set members on distinct hardware, and on systems that draw
-power from different circuits, to the greatest extent possible.
+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.
 
 Procedure
 ---------
@@ -75,9 +84,10 @@ following options for more information: :option:`--port <mongod --port>`,
    option. You will also need to specify the :option:`--bind_ip
    <mongod --bind_ip>` option.
 
-Log in with the :program:`mongo` shell to the first host. If you're
-accessing this command remotely, modify the hostname.  using the
-following command: ::
+Connect to the mongod instance with the :program:`mongo` shell to the 
+first host. If you're accessing this command remotely, replace 
+"localhost" with the approriate hostname.  Open a new terminal session
+and enter the following: ::
 
       mongo localhost:27017
 
@@ -104,8 +114,11 @@ replica set.
    rs.add("localhost:27019")
 
 Congratulations, after these commands return you will have a fully
-functional replica set. You may have to wait several moments for the
-new replica set to successfully elect a :term:`primary` node.
+functional replica set. Within a couple moments the new replica set 
+should successfully elect a :term:`primary` node.
+
+At any time, you may check the status of your replica set with the 
+:func:`rs.status()` command.
 
 See the documentation of the following shell functions for more
 information: :func:`rs.initiate()`, :func:`rs.conf()`,