DOCSP-33284 v6.0 (#4830)

* DOCSP-33284 Fix Compact Behavior Notes

* *

* *

* *

* *

* *

* *

* *

* *

Author: ianf-mongodb

source/reference/command/compact.txt

@@ -207,7 +207,6 @@ replica set, however there are some important considerations:
 
 - The primary node does not replicate the ``compact`` command to the
   secondaries.
-- The ``compact`` command blocks writes while it runs.
 - You should run ``compact`` on secondary nodes whenever possible. If
   you cannot run ``compact`` on secondaries, see the :ref:`force 
   <compact-force-option>` option.
@@ -256,17 +255,21 @@ Blocking behavior on secondary nodes is version specific.
        - Secondary node is in :replstate:`RECOVERING` state.
 
    * - 4.4
-     - - ``compact`` blocks all write activity.
-       - No replication possible.
-       - Reads not permitted.
+     - - No replication is possible.
+       - Reads are not permitted.
 
-   * - Post 4.4.17, 5.0.12, 6.0.2
-     - - ``compact`` blocks all write activity.
-       - A secondary node can replicate while ``compact`` is running.
+   * - Post 4.4.17, 5.0.12, and 6.0.2
+     - - A secondary node can replicate while ``compact`` is running.
        - Reads permitted.  
 
-When ``compact`` completes, the secondary returns to the
-:replstate:`SECONDARY` state.
+Replication status while the ``compact`` command is running depends on 
+your specific MongoDB version:
+
+- In MongoDB versions ``4.4.9`` and later, the replica set remains in a 
+  :replstate:`SECONDARY` status.
+
+- In MongoDB versions earlier than ``4.4.9``, ``compact`` forces
+  the replica set into the :replstate:`RECOVERING` status.
 
 For more information about replica set member states, see
 See :ref:`replica-set-member-states`.