(DOCSP-6257): Fixing inaccurate description of delete timing for TTL indexes

Author: jeff-allen-mongo

source/core/index-ttl.txt

@@ -66,7 +66,9 @@ output of :method:`db.currentOp()` or in the data collected by the
 Timing of the Delete Operation
 ``````````````````````````````
 
-.. include:: /includes/extracts/4.2-index-ttl.rst
+MongoDB begins removing expired documents as soon as the index
+finishes building on the :term:`primary`. For more information on the
+index build process, see :ref:`index-operations`.
 
 .. include:: /includes/fact-ttl-collection-background-timing.rst
 

source/includes/extracts-hybrid-index-fcv.yaml

@@ -15,26 +15,6 @@ content: |
     lock only at the beginning and end of the build process. The rest of
     the build process yields to interleaving read and write operations. 
     MongoDB ignores the ``background`` option if specified.
-
----
-ref: 4.2-index-ttl
-content: |
-
-  For :ref:`feature compatibility version (fcv) <view-fcv>` ``"4.2"``,
-  MongoDB begins removing expired documents as soon as the
-  index finishes building.
-
-  For :ref:`feature compatibility version (fcv) <view-fcv>` ``"4.0"``,
-  the timing of delete operations depends on the index build type:
-
-  - With foreground index builds, MongoDB can begin removing
-    expired documents only *after* the build completes.
-
-  - With background index builds, MongoDB can begin removing
-    expired documents as soon as the they are processed by the build.
-
-  For more information on the index build process, see
-  :ref:`index-operations`.
 ---
 ref: 4.2-rollbacks
 content: |
@@ -82,4 +62,4 @@ content: |
   - For :ref:`feature compatibility version (fcv) <view-fcv>` ``"4.0"``,
     the index build memory limit only applies to foreground
     index builds.
-...
+...