grammatical clarifications in Geo-Dist ReplSets

Author: gwaldo

source/administration/replication-architectures.txt

@@ -90,16 +90,16 @@ In many circumstances, these deployments consist of the following:
   become primary (i.e. with a :data:`members[n].priority` value of
   ``0``.)
 
-If any of the members fail, the replica set will still be able to
-elect a primary node. If the connection between the data center fails,
-the member or members in the second data center cannot become primary
+If the primary node should fail, the replica set will be able to elect a 
+new primary node as normal. If the connection between the data center 
+fails, any members in the second data center cannot become primary
 independently, and the nodes in the primary data center will continue
 to function.
 
 If the primary data center fails, recovering from the database
 instance in the secondary facility requires manual intervention, but
 with proper :term:`write concern` there will be no data loss and
-downtime is typically be minimal.
+downtime will typically be minimal.
 
 For deployments that maintain three members the primary data center,
 adding a node in a second data center will create an even number of