DOCSP-50027: reduce EOL server mentions (#190)

(cherry picked from commit 78d743f)

Author: norareidy

source/fundamentals/authentication.txt

@@ -64,43 +64,36 @@ password to authenticate to a server.
 
 MongoDB supports the following SCRAM-based authentication mechanisms:
 
-- :ref:`SCRAM-SHA-256 <rust-auth-scramsha256>`: an authentication mechanism that
+- :ref:`SCRAM-SHA-256 <rust-auth-scramsha256>`: An authentication mechanism that
   uses your database username and password, encrypted with the ``SHA-256``
-  algorithm
-- :ref:`SCRAM-SHA-1 <rust-auth-scramsha1>`: an authentication mechanism that
+  algorithm. This is the default authentication mechanism.
+- :ref:`SCRAM-SHA-1 <rust-auth-scramsha1>`: An authentication mechanism that
   uses your database username and password, encrypted with the ``SHA-1``
-  algorithm
+  algorithm.
 
-.. important:: Default Authentication Mechanism
-
-   If you do not specify an authentication mechanism, the server
-   attempts to validate credentials by using the default authentication
-   mechanism, a SCRAM-based mechanism that varies depending on the
-   version of the server that you are connecting to.
-
-   The ``SCRAM-SHA-256`` mechanism is the default authentication
-   mechanism for MongoDB Server versions 4.0 and later.
+.. _rust-auth-scramsha256:
 
-   To use the default authentication mechanism, omit only the
-   ``mechanism`` field when you instantiate your ``Credential`` struct.
-   This example uses the following placeholders:
+SCRAM-SHA-256
+~~~~~~~~~~~~~
 
-   - ``db_username``: Your database username
-   - ``db_password``: Your database password
-   - ``db``: The authentication database associated with the user
+Since ``SCRAM-SHA-256`` is the default authentication mechanism,
+you can omit the ``mechanism`` field when you instantiate your ``Credential`` struct
+to use this mechanism.
 
-   .. literalinclude:: /includes/fundamentals/code-snippets/auth.rs
-      :language: rust
-      :dedent:
-      :start-after: start-default
-      :end-before: end-default
+This example specifies the default authentication mechanism by using
+the following placeholders:
 
-.. _rust-auth-scramsha256:
+- ``db_username``: Your database username
+- ``db_password``: Your database password
+- ``db``: The authentication database associated with the user
 
-SCRAM-SHA-256
-~~~~~~~~~~~~~
+.. literalinclude:: /includes/fundamentals/code-snippets/auth.rs
+   :language: rust
+   :dedent:
+   :start-after: start-default
+   :end-before: end-default
 
-To specify the ``SCRAM-SHA-256`` authentication mechanism, set the
+To explicitly specify the ``SCRAM-SHA-256`` authentication mechanism, set the
 ``mechanism`` field of your ``Credential`` struct to
 ``AuthMechanism::ScramSha256``. This example specifies the
 authentication mechanism by using the following placeholders:
@@ -160,11 +153,8 @@ feature flag to your ``mongodb`` dependency in your project's
 .. important::
 
    To use the ``MONGODB-AWS`` authentication mechanism in the
-   {+driver-short+}, your application must meet the following
-   requirements:
-
-   - You are connected to MongoDB Server version 4.4 or later.
-   - You are using the ``tokio`` asynchronous runtime.
+   {+driver-short+}, your application must use the ``tokio``
+   asynchronous runtime.
 
 The driver obtains the credentials only from the first source in which
 they are found. The driver checks for your credentials from the following

source/fundamentals/connections/network-compression.txt

@@ -25,9 +25,9 @@ the total amount of data passed over the network.
 
 The driver supports the following compressors:
 
-1. `Snappy <https://google.github.io/snappy/>`__: available in MongoDB 3.4 and later
-#. `Zlib <https://zlib.net/>`__: available in MongoDB 3.6 and later
-#. `Zstandard <https://github.com/facebook/zstd/>`__: available in MongoDB 4.2 and later
+1. `Snappy <https://google.github.io/snappy/>`__
+#. `Zlib <https://zlib.net/>`__
+#. `Zstandard <https://github.com/facebook/zstd/>`__
 
 .. note:: Compressor Selection
 

source/fundamentals/crud/compound-operations.txt

@@ -151,24 +151,21 @@ The following table describes the options available in
    * - ``hint`` 
      - | The index to use for the operation. To learn more about
          indexes, see :manual:`Indexes </indexes/>` in the Server
-         manual. This option is available only when connecting to
-         {+server+} versions 4.4 and later.
+         manual.
        |
        | Type: ``Hint``
        | Default: ``None``
 
    * - ``let_vars``
      - | A map of parameters and values. You can access these parameters
-         as variables in aggregation expressions. This option is available
-         only when connecting to {+server+} versions 5.0 and later.
+         as variables in aggregation expressions.
        |
        | Type: ``Document``
 
    * - ``comment``
      - | An arbitrary ``Bson`` value tied to the operation to trace
          it through the database profiler, ``currentOp``, and
-         logs. This option is available only when connecting to
-         {+server+} versions 4.4 and later.
+         logs.
        |
        | Type: ``Bson``
        | Default: ``None``
@@ -319,24 +316,21 @@ The following table describes the options available in
    * - ``hint`` 
      - | The index to use for the operation. To learn more about
          indexes, see :manual:`Indexes </indexes/>` in the Server
-         manual. This option is available only when connecting to
-         {+server+} versions 4.4 and later.
+         manual.
        |
        | Type: ``Hint``
        | Default: ``None``
 
    * - ``let_vars``
      - | A map of parameters and values. You can access these parameters
-         as variables in aggregation expressions. This option is available
-         only when connecting to {+server+} versions 5.0 and later.
+         as variables in aggregation expressions.
        |
        | Type: ``Document``
 
    * - ``comment``
      - | An arbitrary ``Bson`` value tied to the operation to trace
          it through the database profiler, ``currentOp``, and
-         logs. This option is available only when connecting to
-         {+server+} versions 4.4 and later.
+         logs.
        |
        | Type: ``Bson``
        | Default: ``None``
@@ -482,24 +476,21 @@ The following table describes the options available in
    * - ``hint`` 
      - | The index to use for the operation. To learn more about
          indexes, see :manual:`Indexes </indexes/>` in the Server
-         manual. This option is available only when connecting to
-         {+server+} versions 4.4 and later.
+         manual.
        |
        | Type: ``Hint``
        | Default: ``None``
 
    * - ``let_vars``
      - | A map of parameters and values. You can access these parameters
-         as variables in aggregation expressions. This option is available
-         only when connecting to {+server+} versions 5.0 and later.
+         as variables in aggregation expressions.
        |
        | Type: ``Document``
 
    * - ``comment``
      - | An arbitrary ``Bson`` value tied to the operation to trace
          it through the database profiler, ``currentOp``, and
-         logs. This option is available only when connecting to
-         {+server+} versions 4.4 and later.
+         logs.
        |
        | Type: ``Bson``
        | Default: ``None``

source/fundamentals/crud/write-operations/change.txt

@@ -125,10 +125,9 @@ and descriptions </reference/operator/update-field/>`.
 
 .. note:: Aggregation Pipelines in Update Operations
 
-   If you are using MongoDB Server version 4.2 or later, you can use aggregation
-   pipelines in update operations. To learn more about the aggregation
-   stages MongoDB supports in aggregation pipelines, see our tutorial on performing
-   :manual:`updates with aggregation pipelines
+   You can use aggregation pipelines to perform update operations. To learn more
+   about the aggregation stages MongoDB supports in aggregation pipelines,
+   see our tutorial on performing :manual:`updates with aggregation pipelines
    </tutorial/update-documents-with-aggregation-pipeline/>`.
 
 Return Value
@@ -452,8 +451,7 @@ The following table describes the options available in ``UpdateOptions``:
        | Default: ``None``
 
    * - ``hint`` 
-     - | The index to use for the operation. This option is available
-         only when connecting to {+server+} versions 4.2 and later.
+     - | The index to use for the operation.
        |
        | Type: ``Hint``
        | Default: ``None``
@@ -469,16 +467,14 @@ The following table describes the options available in ``UpdateOptions``:
 
    * - ``let_vars``
      - | A map of parameters and values. These parameters can be accessed
-         as variables in aggregation expressions. This option is available
-         only when connecting to {+server+} versions 5.0 and later.
+         as variables in aggregation expressions.
        |
        | Type: ``Document``
 
    * - ``comment``
      - | An arbitrary ``Bson`` value tied to the operation to trace
          it through the database profiler, ``currentOp``, and
-         logs. This option is available only when connecting to
-         {+server+} versions 4.4 and later.
+         logs.
        |
        | Type: ``Bson``
        | Default: ``None``

source/fundamentals/crud/write-operations/delete.txt

@@ -113,24 +113,21 @@ The following table describes the options available in ``DeleteOptions``:
    * - ``hint`` 
      - | The index to use for the operation. To learn more about
          indexes, see :manual:`Indexes </indexes/>` in the Server
-         manual. This option is available only when connecting to
-         {+server+} versions 4.4 and later.
+         manual.
        |
        | Type: ``Hint``
        | Default: ``None``
 
    * - ``let_vars``
      - | A map of parameters and values. These parameters can be accessed
-         as variables in aggregation expressions. This option is available
-         only when connecting to {+server+} versions 5.0 and later.
+         as variables in aggregation expressions.
        |
        | Type: ``Document``
 
    * - ``comment``
      - | An arbitrary ``Bson`` value tied to the operation to trace
          it through the database profiler, ``currentOp``, and
-         logs. This option is available only when connecting to
-         {+server+} versions 4.4 and later.
+         logs.
        |
        | Type: ``Bson``
        | Default: ``None``

source/fundamentals/crud/write-operations/insert.txt

@@ -150,8 +150,7 @@ The following table describes the options available in ``InsertOneOptions``:
    * - ``comment``
      - | An arbitrary ``Bson`` value tied to the operation to trace
          it through the database profiler, ``currentOp``, and
-         logs. This option is available only when connecting to
-         {+server+} versions 4.4 and later.
+         logs.
        |    
        | Type: ``Bson``
        | Default: ``None``
@@ -255,8 +254,7 @@ The following table describes the options available in ``InsertManyOptions``:
    * - ``comment``
      - | An arbitrary ``Bson`` value tied to the operation to trace
          it through the database profiler, ``currentOp``, and
-         logs. This option is available only when connecting to
-         {+server+} versions 4.4 and later.
+         logs.
        |
        | Type: ``Bson``
        | Default: ``None``

source/fundamentals/indexes.txt

@@ -114,8 +114,7 @@ disk space and memory. Additionally, if a write operation updates an
 indexed field, MongoDB also must update the relevant index.
 
 MongoDB supports dynamic schemas, so your application can query
-against fields with unknown or variable names. If you are connected to
-MongoDB Server version 4.2 or later, you can create wildcard indexes to
+against fields with unknown or variable names. You can create wildcard indexes to
 support these queries. To learn more about this index type, see
 :manual:`Wildcard Indexes </core/indexes/index-types/index-wildcard/>`
 in the Server manual.

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

@@ -7,77 +7,37 @@
      - MongoDB 8.0
      - MongoDB 7.0
      - MongoDB 6.0
-     - MongoDB 5.0
-     - MongoDB 4.4
-     - MongoDB 4.2
-     - MongoDB 4.0
-     - MongoDB 3.6
    * - 3.1 to 3.2 [#2.5-onwards-limitation]_
      - ✓
      - ✓
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - 
    * - 2.6 to 3.0 [#2.5-onwards-limitation]_
      - ⊛
      - ✓
      - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
    * - 2.5 [#2.5-onwards-limitation]_
      - ⊛
      - ⊛
      - ⊛
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
    * - 2.4 [#2.4-limitation]_
      - ⊛
      - ⊛
      - ⊛
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
    * - 2.2 to 2.3 [#2.2-2.3-limitation]_
      - ⊛
      - ⊛
      - ⊛
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
    * - 2.1 [#2.1-limitation]_
      - ⊛
      - ⊛
      - ⊛
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
    * - 2.0 [#2.0-limitation]_
      - ⊛
      - ⊛
      - ⊛
-     - ✓
-     - ✓
-     - ✓
-     - ✓
-     - ✓
 
 The {+driver-short+} is not compatible with {+server+} versions
-older than 3.6.
+older than 6.0.
 
 .. [#2.5-onwards-limitation] These {+driver-short+} versions do not support
    :manual:`OCSP </core/security-transport-encryption/#ocsp--online-certificate-status-protocol->`.