DOCS-8616: More CR Changes

Author: ravindk89

source/includes/steps-enable-authentication-in-shardcluster-nodowntime-auth-mongos.yaml

@@ -32,7 +32,7 @@ pre: |
   
      db.getSiblingDB("admin").shutdownServer()
   
-  You can then restart the :program:`mongos specifying the path to the updated
+  You can then restart the :program:`mongos` specifying the path to the updated
   config file using :option:`--config`.
   
   .. example::

source/includes/steps-enable-authentication-in-shardcluster-nodowntime-transition-config.yaml

@@ -47,20 +47,20 @@ ref: restart-mongod
 title: "Restart the ``mongod`` with the new configuration file."
 pre: |
 
-  Connect to the :program:`mongod` and use the :method:`db.shutdownServer()`
-  method against the ``admin`` database to safely shut down the
-  :program:`mongod`.
+  If upgrading the a :term:`secondary`, connect to the :program:`mongod` and
+  use the :method:`db.shutdownServer()` method against the ``admin`` database
+  to safely shut down the :program:`mongod`.
   
   .. code-block:: javascript
   
      db.getSiblingDB("admin").shutdownServer()
   
-  If you are performing this step on the :term:`primary`, you must first use
+  If upgrading the :term:`primary`, connect to the :program:`mongod` and use
   the :method:`rs.stepDown()` method against the ``admin`` database to step
   down the primary and trigger an election. You can use the
   :method:`rs.status()` method to ensure the replica set elected a new primary.
   
-  Once you step down the primary, you shut it down using the
+  Once you step down the primary, shut it down using the
   :method:`db.shutdownServer()` method against the ``admin`` database.
   
   .. code-block:: javascript

source/includes/steps-enable-authentication-in-shardcluster-nodowntime-transition-mongos.yaml

@@ -47,10 +47,6 @@ ref: restart-mongos
 title: "Restart the ``mongos`` with the new configuration file."
 pre: |
 
-  Connect to the :program:`mongos` and use the :method:`db.shutdownServer()`
-  method against the ``admin`` database to safely shut down the
-  :program:`mongos`.
-  
   Restart one :program:`mongos` at a time to ensure that clients can connect
   to the sharded cluster. If your cluster has only one :program:`mongos`, this
   step results in downtime while the :program:`mongos` is offline.

source/tutorial/enforce-keyfile-access-control-in-existing-sharded-cluster-no-downtime.txt

@@ -244,8 +244,8 @@ sharded cluster, you must restart each :program:`mongod` instance without
 the :setting:`security.transitionToAuth` setting.
 
 Perform these steps for each :program:`mongod` in the config server replica
-set, one member at a time. Work on the :term:`secondary` or members *first*,
-and the :term:`primary` *last*.
+set, one member at a time. Start with the :term:`secondary` members
+*first*, and the :term:`primary` *last*.
 
 .. include:: /includes/steps/enable-authentication-in-shardcluster-nodowntime-auth-config.rst
 
@@ -269,7 +269,7 @@ sharded cluster without the :setting:`security.transitionToAuth` setting.
 Repeat these steps for each shard replica set in the sharded cluster.
 
 Perform these steps on one shard replica set at a time, and one member in the
-shard replica set at a time. Work on the :term:`secondary`
+shard replica set at a time. Start with the :term:`secondary`
 members *first*, and the :term:`primary` *last*.
 
 .. include:: /includes/steps/enable-authentication-in-shardcluster-nodowntime-auth-shard.rst