DOCSP-50024: Remove EOL server version mentions

source/connect/network-compression.txt

@@ -25,11 +25,11 @@ amount of data passed over the network between MongoDB and your application.
 
 The {+driver-short+} supports the following compression algorithms:
 
-1. `Snappy <https://google.github.io/snappy/>`__: Available in MongoDB 3.6 and later.
+1. `Snappy <https://google.github.io/snappy/>`__
 
-2. `Zlib <https://zlib.net/>`__: Available in MongoDB 3.6 and later.
+#. `Zlib <https://zlib.net/>`__
 
-3. `Zstandard <https://github.com/facebook/zstd/>`__: Available in MongoDB 4.2 and later.
+#. `Zstandard <https://github.com/facebook/zstd/>`__
 
 If you don't specify a compression algorithm, the driver doesn't compress your
 network traffic. If you specify multiple compression algorithms, the driver selects the

source/includes/mongodb-compatibility-table-cxx.rst

@@ -7,133 +7,28 @@
      - MongoDB 8.0
      - MongoDB 7.0
      - MongoDB 6.0
-     - MongoDB 5.0
-     - MongoDB 4.4
-     - MongoDB 4.2
-     - MongoDB 4.0
-     - MongoDB 3.6
-     - MongoDB 3.4
-     - MongoDB 3.2
-     - MongoDB 3.0
-     - MongoDB 2.6
-     - MongoDB 2.4
 
    * - 3.11 to 4.1
      - ✓
      - ✓
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - 
-     -
-     -
-     -
-     -
-     -
 
    * - 3.8 to 3.10
      - ⊛
      - ✓
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     -
-     -
-     -
-     -
-     -
 
    * - 3.7
      - ⊛
      - ⊛
      - ⊛
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     -
-     -
-     -
-     -
-     -
 
    * - 3.6
      - ⊛
      - ⊛
      - ⊛
-     - ⊛
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     -
-     -
 
    * - 3.4 to 3.5
      - ⊛
      - ⊛
      - ⊛
-     - ⊛
-     - ⊛
-     - ⊛
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     -
-     -
-
-   * - 3.3
-     -
-     -
-     - 
-     -
-     -
-     -
-     -
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     -
-     -
-
-   * - 3.1 to 3.2
-     -
-     -
-     - 
-     -
-     -
-     -
-     -
-     -
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-
-   * - 3.0
-     -
-     -
-     - 
-     -
-     -
-     -
-     -
-     -
-     -
-     - ✓
-     - ✓
-     - ✓
-     - ✓

source/indexes/work-with-indexes.txt

@@ -40,8 +40,8 @@ when a write operation updates an indexed field, MongoDB also updates any relate
 index.
 
 Because MongoDB supports dynamic schemas, applications can query against fields
-whose names are not known in advance or are arbitrary. MongoDB 4.2 introduced
-:manual:`wildcard indexes </core/index-wildcard/>` to help support these
+whose names are not known in advance or are arbitrary. You can use
+:manual:`wildcard indexes </core/index-wildcard/>` to support these
 queries. Wildcard indexes are not designed to replace workload-based index
 planning.
 
@@ -111,7 +111,7 @@ collection:
 Remove All Indexes
 ~~~~~~~~~~~~~~~~~~
 
-Starting with MongoDB 4.2, you can drop all indexes by calling the
+You can drop all indexes by calling the
 ``drop_all()`` method on the index view in your collection:
 
 .. literalinclude:: /includes/indexes/indexes.cpp

source/security/in-use-encryption.txt

@@ -73,8 +73,7 @@ Encryption </core/queryable-encryption/>` in the MongoDB Server manual.
 Client-side Field Level Encryption
 ----------------------------------
 
-Client-side Field Level Encryption (CSFLE) was introduced in MongoDB
-Server version 4.2 and supports searching encrypted fields for equality.
+Client-side Field Level Encryption (CSFLE) supports searching encrypted fields for equality.
 CSFLE differs from Queryable Encryption in that you can select either a
 deterministic or random encryption algorithm to encrypt fields. You can only
 query encrypted fields that use a deterministic encryption algorithm when