DOCS-538 verify connectivity: minor edits

Author: Bob Grabar

source/administration/replica-sets.txt

@@ -664,7 +664,11 @@ Test the Connection Between Each Member
 There must be connectivity from every :term:`replica set` member to
 every other member in order for replication to work. Problems with
 network or firewall rules can prevent this connectivity and prevent
-replication from working. To test the connection from every member to
+replication from working. Network topologies and firewalls might allow a
+connection in one direction but not the other. Therefore you must make
+sure to verify that the connection works in both directions.
+
+To test the connection from every member to
 every other member, in both directions, consider the following example:
 
 .. example:: Given a replica set with three members running on three separate
@@ -679,19 +683,16 @@ every other member, in both directions, consider the following example:
 
       .. code-block:: sh
 
-         mongo --host m2.example.net --port 27017"
+         mongo --host m2.example.net --port 27017
 
-         mongo --host m3.example.net --port 27017"
+         mongo --host m3.example.net --port 27017
 
    #. Test the connection from ``m2.example.net`` to the other two
       hosts by running similar appropriate operations from ``m2.example.net``.
 
-      This means you have now tested the connection between
+      You have now tested the connection between
       ``m2.example.net`` and ``m1.example.net`` twice, but each time
-      from a different direction. This is important to verifying
-      connectivity. Network topologies and firewalls might allow a
-      connection in one direction but not the other. Therefore you must
-      make sure to verify that the connection works in both directions.
+      from a different direction.
 
    #. Test the connection from ``m3.example.net`` to the other two
       hosts by running the operations from ``m3.example.net``.

source/tutorial/deploy-replica-set.txt

@@ -49,8 +49,10 @@ Deploy a Development or Testing Replica Set
 
 The examples in this procedure create a new replica set named ``rs0``.
 
-1. Before creating your replica set, verify there is full connectivity
-   between all the hosts to be in the replica set, as described in
+1. Before creating your replica set, verify that every member can
+   successfully connect to every other member. The connection between
+   any two members must work in both directions. To test the connection
+   from each member to every other member, see
    :ref:`replica-set-troubleshooting-check-connection`.
 
 #. Start three instances of :program:`mongod` as members of a replica
@@ -190,8 +192,10 @@ deployment described above, with the following differences:
 
 To deploy a production replica set:
 
-1. Before creating your replica set, verify there is full connectivity
-   between all the hosts to be in the replica set, as described in
+1. Before creating your replica set, verify that every member can
+   successfully connect to every other member. The connection between
+   any two members must work in both directions. To test the connection
+   from each member to every other member, see
    :ref:`replica-set-troubleshooting-check-connection`.
 
 #. On each system start the :program:`mongod` process by issuing a