mongodb
diff --git a/‎source/crud/query-documents/sort.txt
Lines changed: 0 additions & 11 deletions b/‎source/crud/query-documents/sort.txt
Lines changed: 0 additions & 11 deletions
diff --git a/‎source/includes/mongodb-compatibility-table-java.rst
Lines changed: 0 additions & 55 deletions b/‎source/includes/mongodb-compatibility-table-java.rst
Lines changed: 0 additions & 55 deletions
diff --git a/‎source/indexes.txt
Lines changed: 2 additions & 2 deletions b/‎source/indexes.txt
Lines changed: 2 additions & 2 deletions
@@ -4,8 +4,6 @@
 Sort Results
 ============
 
-
-
 .. contents:: On this page
    :local:
    :backlinks: none
@@ -373,15 +371,6 @@ The output of the preceding code resembles the following:
    {"_id": 2, "letter": "a", "food": "donuts and coffee", "score": 0.75}
    {"_id": 3, "letter": "a", "food": "maple syrup", "score": 0.75}
 
-.. note:: Text Search Behavior in MongoDB 4.4 or Later
-
-   The structure of text search has changed for MongoDB 4.4 or later. You no
-   longer project ``Projections.metaTextScore()`` into your
-   ``FindIterable`` instance in order to sort on the text score. In addition,
-   the field name you specify in a ``$meta`` text score aggregation operation
-   used in a sort is ignored. This means that the field name argument you pass
-   to ``Sorts.metaTextScore()`` is disregarded.
-
 For more information about the classes in this section, see the
 following API Documentation:
 
 
@@ -9,130 +9,75 @@
      - MongoDB 7.0
      - MongoDB 6.1
      - MongoDB 6.0
-     - MongoDB 5.0
-     - MongoDB 4.4
-     - MongoDB 4.2
-     - MongoDB 4.0
-     - MongoDB 3.6
 
    * - 5.5
      - ✓
      - ✓
      - ✓
      - ✓
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     -
-     -
 
    * - 5.2 to 5.4
      - ✓
      - ✓
      - ✓
      - ✓
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     -
 
    * - 4.10 to 5.1
      - ⊛
      - ⊛
      - ✓
      - ✓
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
 
    * - 4.8 to 4.9
      - ⊛
      - ⊛
      - ⊛
      - ✓
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
 
    * - 4.7
      - ⊛
      - ⊛
      - ⊛
      - ⊛
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
 
    * - 4.3 to 4.6
      - ⊛
      - ⊛
      - ⊛
      - ⊛
      - ⊛
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
 
    * - 4.1 to 4.2
      - ⊛
      - ⊛
      - ⊛
      - ⊛
      - ⊛
-     - ⊛
-     - ✓
-     - ✓
-     - ✓
-     - ✓
 
    * - 4.0
      - ⊛
      - ⊛
      - ⊛
      - ⊛
      - ⊛
-     - ⊛
-     - ⊛
-     - ✓
-     - ✓
-     - ✓
 
    * - 3.11 to 3.12
      - ✗ [#v3-note]_
      - ⊛
      - ⊛
      - ⊛
      - ⊛
-     - ⊛
-     - ⊛
-     - ✓
-     - ✓
-     - ✓
 
    * - 3.8 to 3.10
      - ✗ [#v3-note]_
      - ⊛
      - ⊛
      - ⊛
      - ⊛
-     - ⊛
-     - ⊛
-     - ⊛
-     - ✓
-     - ✓
 
 .. [#v3-note] These driver versions are not compatible with MongoDB 8.1 or later because of an authentication issue. To learn more, see :ref:`java-server-8.1-incompatibility`.
@@ -79,8 +79,8 @@ when a write operation updates an indexed field, MongoDB updates the related
 index.
 
 Since MongoDB supports dynamic schemas, applications can query against fields whose names cannot be known in advance or
-are arbitrary. MongoDB 4.2 introduced :manual:`wildcard indexes </core/index-wildcard/>` to help support these queries.
-Wildcard indexes are not designed to replace workload-based index planning.
+are arbitrary. :manual:`Wildcard indexes </core/index-wildcard/>` help support these queries, but
+are not designed to replace workload-based index planning.
 
 For more information about designing your data model and choosing indexes appropriate for your application, see the {+mdb-server+}
 :manual:`Data Modeling and Indexes </core/data-model-operations/#indexes>`.