DOCSP-28856-secondary-throttle-update (#7258) (#7362)

* DOCSP-28856-secondary-throttle-update

* DOCSP-28856-secondary-throttle-update

* DOCSP-28856-secondary-throttle-update

* DOCSP-28856-secondary-throttle-update

---------

Co-authored-by: jason-price-mongodb <[email protected]>

Author: jason-price-mongodb

source/core/sharding-balancer-administration.txt

@@ -236,16 +236,10 @@ when the migration proceeds with next document in the range.
 In the :data:`config.settings` collection:
 
 - If the ``_secondaryThrottle`` setting for the balancer is set to a
-  write concern, each document move during range migration must receive
+  :term:`write concern`, each document moved during range migration must receive
   the requested acknowledgment before proceeding with the next
   document.
 
-- If the ``_secondaryThrottle`` setting for the balancer is set to
-  ``true``, each document move during range migration must receive
-  acknowledgment from at least one secondary before the migration
-  proceeds with the next document in the range. This is equivalent to a
-  write concern of :writeconcern:`{ w: 2 } <\<number\>>`.
-
 - If the ``_secondaryThrottle`` setting is unset, the migration process
   does not wait for replication to a secondary and instead continues
   with the next document.

source/tutorial/manage-sharded-cluster-balancer.txt

@@ -31,15 +31,15 @@ Check the Balancer State
 actively migrating data.
 
 To see if the balancer is enabled in your :term:`sharded cluster`,
-issue the following command, which returns a boolean:
+run the following command, which returns a boolean:
 
 .. code-block:: javascript
 
    sh.getBalancerState()
 
 You can also see if the balancer is enabled using :method:`sh.status()`.
 The :data:`~sh.status.balancer.currently-enabled` field indicates
-whether the balancer is enabled, while the
+whether the balancer is enabled, and the
 :data:`~sh.status.balancer.currently-running` field indicates if the
 balancer is currently running.
 
@@ -134,15 +134,15 @@ all migration, use the following procedure:
 
    .. include:: /includes/extracts/4.2-changes-stop-balancer-autosplit.rst
 
-#. To verify that the balancer will not start, issue the following command,
+#. To verify that the balancer won't start, run the following command,
    which returns ``false`` if the balancer is disabled:
 
    .. code-block:: javascript
 
       sh.getBalancerState()
 
    Optionally, to verify no migrations are in progress after disabling,
-   issue the following operation in the :binary:`~bin.mongosh` shell:
+   run the following operation in the :binary:`~bin.mongosh` shell:
 
    .. code-block:: javascript
 
@@ -320,18 +320,11 @@ when the migration proceeds with next document in the chunk.
 
 In the :data:`config.settings` collection:
 
-
 - If the ``_secondaryThrottle`` setting for the balancer is set to a
-  write concern, each document move during chunk migration must receive
+  :term:`write concern`, each document moved during chunk migration must receive
   the requested acknowledgment before proceeding with the next
   document.
 
-- If the ``_secondaryThrottle`` setting for the balancer is set to
-  ``true``, each document move during chunk migration must receive
-  acknowledgment from at least one secondary before the migration
-  proceeds with the next document in the chunk. This is equivalent to a
-  write concern of :writeconcern:`{ w: 2 } <\<number\>>`.
-
 - If the ``_secondaryThrottle`` setting is unset, the migration process
   does not wait for replication to a secondary and instead continues
   with the next document.
@@ -342,7 +335,7 @@ To change the ``_secondaryThrottle`` setting, connect to a
 :binary:`~bin.mongos` instance and directly update the
 ``_secondaryThrottle`` value in the :data:`~config.settings` collection
 of the :ref:`config database <config-database>`. For example, from a
-:binary:`~bin.mongosh` shell connected to a :binary:`~bin.mongos`, issue
+:binary:`~bin.mongosh` shell connected to a :binary:`~bin.mongos`, run
 the following command:
 
 .. code-block:: javascript
@@ -440,7 +433,7 @@ To set the balancer's ``attemptToBalanceJumboChunks`` setting, connect
 to a :binary:`~bin.mongos` instance and directly update the
 :data:`config.settings` collection. For example, from a
 :binary:`~bin.mongosh` shell connected to a :binary:`~bin.mongos`
-instance, issue the following command:
+instance, run the following command:
 
 .. code-block:: javascript