Add note about using $changeStreamSplitLargeEvent and update verion (#5572)

* Add note about using $changeStreamSplitLargeEvent and update verion

* remove space in link

* fix link again

* update version style as per Jeff

* update version formatting

* reverting forced push

Author: MongoCaleb

source/administration/change-streams-production-recommendations.txt

@@ -17,17 +17,19 @@ opened against it, the change stream cursors close when they advance to
 that point in the oplog. Change stream cursors with the ``fullDocument :
 updateLookup`` option may return ``null`` for the lookup document.
 
-Attempting to resume a change stream against a dropped collection results in
-an error. Any data changes that occurred on the collection between the last
-event the change stream captured and the collection drop event are lost.
-
 Change stream response documents must adhere to the 16MB BSON document limit.
 Depending on the size of documents in the collection against which you open a
 change stream, notifications may fail if the resulting notification document
 exceeds the 16MB limit. For example, update operations on change streams
 configured to return the full updated document, or insert/replace operations
 with a document that is at or just below the limit.
 
+.. important::
+
+   Starting in version 6.0.9, you can use the 
+   :pipeline:`$changeStreamSplitLargeEvent` aggregation 
+   stage to split the events into smaller fragments. 
+
 Replica Sets
 ------------
 
@@ -77,14 +79,6 @@ Consider utilizing notification filters for these types of collections.
 For example, passing a :pipeline:`$match` pipeline configured to filter
 only ``insert`` operations.
 
-For sharded collections, update operations with :ref:`multi : true
-<multi-parameter>` may cause any change streams opened against that collection
-to send notifications for :term:`orphaned documents <orphaned document>`.
-
-From the moment an unsharded collection is sharded until the time the change
-stream catches up to the first chunk migration, the ``documentKey`` in the
-change stream notification document only includes the ``_id`` of the document,
-not the full shard key.
 
 Indexes and Performance
 -----------------------

source/includes/change-streams-and-orphans.rst

@@ -1,4 +1,4 @@
 Starting in MongoDB 5.3, during :ref:`range migration
 <range-migration-procedure>`, :ref:`change stream <changeStreams>`
 events are not generated for updates to :term:`orphaned documents
-<orphaned document>`.
+<orphaned document>`.

source/reference/command/serverStatus.txt

@@ -1884,6 +1884,14 @@ metrics
 
    .. versionadded:: 5.1
 
+.. serverstatus:: metrics.changeStreams.largeEventsSplit
+
+   The number of change stream events larger than 16 MB that were split
+   into smaller fragments. Events are only split if you use the
+   :pipeline:`$changeStreamSplitLargeEvent` pipeline stage.
+
+   .. versionadded:: 7.0 (*Also available in 6.0.9*)
+
 .. serverstatus:: metrics.changeStreams
 
    A document that reports information about :ref:`change stream
@@ -1900,13 +1908,6 @@ metrics
 
    .. versionadded:: 7.0
 
-.. serverstatus:: metrics.changeStreams.largeEventsSplit
-
-   The number of change stream events larger than 16 MB that were split
-   into smaller fragments. Events are only split if you use the
-   :pipeline:`$changeStreamSplitLargeEvent` pipeline stage.
-
-   .. versionadded:: 7.0
 
 .. serverstatus:: metrics.changeStreams.showExpandedEvents
 

source/reference/operator/aggregation/changeStreamSplitLargeEvent.txt

@@ -13,11 +13,11 @@ Definition
 
 .. pipeline:: $changeStreamSplitLargeEvent
 
-.. versionadded:: 7.0
+.. versionadded:: 7.0 (*Also available in 6.0.9*)
 
 If a :ref:`change stream <changeStreams>` has large events that exceed
 16 MB, a ``BSONObjectTooLarge`` exception is returned. Starting in
-MongoDB 7.0, you can use a ``$changeStreamSplitLargeEvent`` stage to
+MongoDB 6.0.9, you can use a ``$changeStreamSplitLargeEvent`` stage to
 split the events into smaller fragments.
 
 You should only use ``$changeStreamSplitLargeEvent`` when strictly