Docsp-23332 clean up orphan docs (#1346) (#1385)

* DOCSP-23332-clean-up-orphan-docs

* DOCSP-23332-clean-up-orphan-docs

* DOCSP-23332-clean-up-orphan-docs

* DOCSP-23332-clean-up-orphan-docs

* DOCSP-23332-clean-up-orphan-docs

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

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

Author: jason-price-mongodb

source/reference/command/cleanupOrphaned.txt

@@ -17,16 +17,21 @@ Definition
 
    .. versionchanged:: 4.4
 
-   Starting in MongoDB 4.4, :term:`chunk` migrations and orphaned
-   document cleanup are more resilient to failover. The cleanup process
-   automatically resumes in the event of a failover. You no longer need
-   to run the :dbcommand:`cleanupOrphaned` command to clean up orphaned
-   documents. Instead, use this command to wait for orphaned documents
-   in a chunk range from a shard key's
-   :doc:`minKey</reference/bson-types>` to its
+   **For orphaned documents generated after upgrading to MongoDB
+   4.4:** :term:`chunk` migrations and orphaned document cleanup are
+   more resilient to failover. The cleanup process automatically resumes
+   in the event of a failover. You no longer need to run the
+   :dbcommand:`cleanupOrphaned` command to clean up orphaned documents.
+   Instead, use this command to wait for orphaned documents in a chunk
+   range from a shard key's :doc:`minKey</reference/bson-types>` to its
    :doc:`maxKey</reference/bson-types>` for a specified namespace to be
    cleaned up from a majority of a shard's members.
 
+   **For orphaned documents generated before upgrading to MongoDB
+   4.4**: the orphaned documents are not automatically cleaned up after
+   upgrading to MongoDB 4.4 and you must use
+   :dbcommand:`cleanupOrphaned` to clean up the orphaned documents.
+
    In MongoDB 4.2 and earlier, :dbcommand:`cleanupOrphaned` initiated 
    the cleanup process for orphaned documents in a specified namespace 
    and shard key range.