Backports DOCSP-38840 to v7.0 (#195)

Backports #187 

[Build](https://workerpool-boxgs.mongodbstitch.com/pages/job.html?collName=queue&jobId=6634f195b67dbf804aa441b1)

Author: sarahsimpers

source/tutorial/prepare-for-maintenance.txt

@@ -11,9 +11,13 @@ Prepare for Cluster Maintenance
    :class: singlecol
 
 |mms| performs a :opsmgr:`rolling restart </reference/glossary/#std-term-rolling-restart>` when you perform maintenance
-on nodes in a cluster. {+aagent+} updates nodes in a cluster one-by-one 
-until all nodes are updated to maintain cluster availability during a 
-maintenance period.
+on nodes in a cluster. To maintain cluster availability during a 
+maintenance period, {+aagent+} updates nodes in a cluster in the
+following way:
+
+- For three-member replica sets, {+aagent+} updates nodes one node at a
+  time.
+- For five-member replica sets, {+aagent+} updates two nodes at a time.
 
 Before you perform maintenance on your clusters, review the following 
 considerations and take action, if necessary, to maintain cluster
@@ -53,27 +57,19 @@ Fault Tolerance
 ---------------
 
 Nodes undergoing maintenance don't provide failover support to the 
-cluster. For three-member replica sets, if an additional node becomes 
-unavailable while one node is undergoing maintenance, the cluster has 
-lost the majority of nodes. The primary node loses this status and 
+cluster. For three-member and five-member replica sets, if an
+additional node becomes unavailable during maintenance, the cluster
+loses the majority of nodes. The primary node loses this status and 
 steps down to become a secondary node. A new primary can't be elected
-until a majority of the cluster's nodes are available.
+until a majority of the cluster's nodes become available.
 
 For mission-critical applications with high uptime needs, consider 
-converting a three-member replica set to a five-member replica 
-set before performing maintenance to maintain cluster majority in case 
+:ref:`adding a temporary arbiter <add-member-to-rs>` to a 
+three-member or five-member replica set before you perform maintenance.
+The temporary arbiter can maintain cluster majority in case 
 an additional cluster node becomes unavailable during a maintenance 
 period.
 
-.. note::
-
-   Five-member replica sets or larger are more resilient and less likely
-   to experience loss of majority during maintenance periods.
-
-A simpler but less resilient option to increase multiple failure 
-tolerance is to :ref:`add a temporary arbiter <add-member-to-rs>` to a 
-three-member replica set before you perform maintenance.
-
 Unique Index Builds
 -------------------