From da5e268247cd0af8c7e7f8aa103da577d3524847 Mon Sep 17 00:00:00 2001
From: Michael Morisi <michael.morisi@mongodb.com>
Date: Thu, 22 May 2025 11:17:37 -0400
Subject: [PATCH 1/2] DOCSP-50018: Remove EOL server version mentions

---
 source/crud/query-documents/sort.txt          | 11 ----
 .../mongodb-compatibility-table-java.rst      | 55 -------------------
 source/indexes.txt                            |  4 +-
 3 files changed, 2 insertions(+), 68 deletions(-)

diff --git a/source/crud/query-documents/sort.txt b/source/crud/query-documents/sort.txt
index 794e55c13..a27a72ff6 100644
--- a/source/crud/query-documents/sort.txt
+++ b/source/crud/query-documents/sort.txt
@@ -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:
 
diff --git a/source/includes/mongodb-compatibility-table-java.rst b/source/includes/mongodb-compatibility-table-java.rst
index 6991fd286..61d776d1a 100644
--- a/source/includes/mongodb-compatibility-table-java.rst
+++ b/source/includes/mongodb-compatibility-table-java.rst
@@ -9,11 +9,6 @@
      - 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
      - ✓
@@ -21,11 +16,6 @@
      - ✓
      - ✓
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     -
-     -
 
    * - 5.2 to 5.4
      - ✓
@@ -33,11 +23,6 @@
      - ✓
      - ✓
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     -
 
    * - 4.10 to 5.1
      - ⊛
@@ -45,11 +30,6 @@
      - ✓
      - ✓
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
 
    * - 4.8 to 4.9
      - ⊛
@@ -57,11 +37,6 @@
      - ⊛
      - ✓
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
 
    * - 4.7
      - ⊛
@@ -69,11 +44,6 @@
      - ⊛
      - ⊛
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
 
    * - 4.3 to 4.6
      - ⊛
@@ -81,11 +51,6 @@
      - ⊛
      - ⊛
      - ⊛
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
 
    * - 4.1 to 4.2
      - ⊛
@@ -93,11 +58,6 @@
      - ⊛
      - ⊛
      - ⊛
-     - ⊛
-     - ✓
-     - ✓
-     - ✓
-     - ✓
 
    * - 4.0
      - ⊛
@@ -105,11 +65,6 @@
      - ⊛
      - ⊛
      - ⊛
-     - ⊛
-     - ⊛
-     - ✓
-     - ✓
-     - ✓
 
    * - 3.11 to 3.12
      - ✗ [#v3-note]_
@@ -117,11 +72,6 @@
      - ⊛
      - ⊛
      - ⊛
-     - ⊛
-     - ⊛
-     - ✓
-     - ✓
-     - ✓
 
    * - 3.8 to 3.10
      - ✗ [#v3-note]_
@@ -129,10 +79,5 @@
      - ⊛
      - ⊛
      - ⊛
-     - ⊛
-     - ⊛
-     - ⊛
-     - ✓
-     - ✓
 
 .. [#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`.
diff --git a/source/indexes.txt b/source/indexes.txt
index 7401dce4e..2c10e1555 100644
--- a/source/indexes.txt
+++ b/source/indexes.txt
@@ -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>`.

From 6c7903a6fe2b9f8483507329ee0cbc4048cc627f Mon Sep 17 00:00:00 2001
From: Michael Morisi <michael.morisi@mongodb.com>
Date: Thu, 22 May 2025 11:26:42 -0400
Subject: [PATCH 2/2] RR feedback

---
 source/indexes.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/indexes.txt b/source/indexes.txt
index 2c10e1555..bf35c8c59 100644
--- a/source/indexes.txt
+++ b/source/indexes.txt
@@ -78,7 +78,7 @@ that you track index memory and disk usage for capacity planning. In addition,
 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
+Since MongoDB supports dynamic schemas, applications can query against fields whose names you don't know in advance or
 are arbitrary. :manual:`Wildcard indexes </core/index-wildcard/>` help support these queries, but
 are not designed to replace workload-based index planning.