merge: correction

Author: Sam Kleinman

source/tutorial/deploy-geographically-distributed-replica-set.txt

@@ -16,13 +16,13 @@ tutorials, see :doc:`/tutorial/deploy-replica-set` and
 Overview
 --------
 
-While :term:`replica sets <replica set>` provide basic protection against single-instance
-failure, when all of the members of a replica set reside within a
-single facility, the replica set is still susceptible to some classes
-of errors within that facility including power outages, networking
-distortions, and natural disasters. To protect against these classes
-of failures, deploy a replica set with one or more members in a
-geographically distinct facility or data center.
+While :term:`replica sets <replica set>` provide basic protection
+against single-instance failure, when all of the members of a replica
+set reside in a single facility, the replica set is still susceptible
+to some classes of errors in that facility including power outages,
+networking distortions, and natural disasters. To protect against
+these classes of failures, deploy a replica set with one or more
+members in a geographically distinct facility or data center.
 
 Requirements
 ------------
@@ -456,8 +456,8 @@ differences:
 - Use the procedure for a three-member set if you have an odd number of
   members (see :ref:`replica-set-deploy-distributed-three-member`).
   Ensure that Site A always has a majority of the members of the set.
-  For example, if a set has five members, deploy three remember within
-  the primary facility and two remember in other facilities.
+  For example, if a set has five members, deploy three members within
+  the primary facility and two members in other facilities.
 
 - If you have a majority of the members of the set *outside* of Site A
   and the network partitions to prevent communication between sites,