DOCSP-33478: fix vale issues (#108)

(cherry picked from commit 118e6f6)

Author: rustagir

source/fundamentals/aggregation.txt

@@ -148,8 +148,7 @@ The aggregation pipeline contains the following stages:
   ``genre_interests`` field into a new document.
 - A ``$group`` stage to group documents by the value of the
   ``genre_interests`` field. This stage finds the average, minimum, and
-  maximum user age for users, using the ``$avg``, ``$min``, and ``$max``
-  operators, respectively.
+  maximum user age by using the ``$avg``, ``$min``, and ``$max`` operators.
 
 .. io-code-block::
 

source/fundamentals/connections/connection-options.txt

@@ -40,7 +40,7 @@ connected to the server.
    * - **authMechanismProperties**
      - String
      - None
-     - Specifies additional properties for the authentication mechanism
+     - Specifies more properties for the authentication mechanism
        set in the ``authMechanism`` option.
 
    * - **authSource**
@@ -72,7 +72,7 @@ connected to the server.
    * - **heartbeatFrequencyMS**
      - Integer greater than or equal to 500
      - ``10000`` (10 seconds)
-     - Specifies the amount of time, in milliseconds, that each
+     - Specifies the amount of time in milliseconds that each
        monitoring thread waits between performing server checks.
 
    * - **journal**
@@ -83,8 +83,8 @@ connected to the server.
    * - **localThresholdMS**
      - Non-negative integer
      - 15
-     - | Specifies how much longer, in milliseconds, that the average
-         round-trip time between the driver and server can take
+     - | Specifies the amount of time in milliseconds that the average
+         round-trip time between the driver and server can last
          compared to the shortest round-trip time of all the suitable servers.
        | A value of ``0`` indicates that there is no latency window, so
          only the server with the lowest average round-trip time is
@@ -93,7 +93,7 @@ connected to the server.
    * - **maxIdleTimeMS**
      - Non-negative integer
      - 0
-     - | Specifies the amount of time, in milliseconds, that a connection
+     - | Specifies the amount of time in milliseconds that a connection
          can remain idle in a connection pool the server closes it.
        | A value of ``0`` indicates that the client does not close idle
          connections.
@@ -157,7 +157,7 @@ connected to the server.
    * - **serverSelectionTimeoutMS**
      - Non-negative integer
      - ``30000`` (30 seconds)
-     - Specifies the amount of time, in milliseconds, that the
+     - Specifies the amount of time in milliseconds that the
        ``Client`` instance waits when attempting to select a server for an
        operation before timing out.
 

source/fundamentals/crud/compound-operations.txt

@@ -112,7 +112,7 @@ The following table describes the options available in
      - Description
 
    * - ``max_time`` 
-     - | The maximum amount of time, in milliseconds, that the query can
+     - | The maximum amount of time in milliseconds that the query can
          run.
        |
        | Type: ``Duration``
@@ -265,7 +265,7 @@ The following table describes the options available in
        | Default: ``false``
 
    * - ``max_time`` 
-     - | The maximum amount of time, in milliseconds, that the query can
+     - | The maximum amount of time in milliseconds that the query can
          run.
        |
        | Type: ``Duration``
@@ -396,7 +396,7 @@ Find and Replace a Document
 
 The ``find_one_and_replace()`` method finds and replaces the first
 document that matches the specified query filter. The operation replaces
-all of the fields of the document except the ``_id`` field with fields
+all the fields of the document except the ``_id`` field with fields
 and values that you provide. If a document matches the filter criteria,
 the method returns a ``Some`` type. If no documents match, it returns a
 ``None`` type.
@@ -434,7 +434,7 @@ The following table describes the options available in
        | Default: ``false``
 
    * - ``max_time`` 
-     - | The maximum amount of time, in milliseconds, that the query can
+     - | The maximum amount of time in milliseconds that the query can
          run.
        |
        | Type: ``Duration``

source/fundamentals/crud/read-operations/query.txt

@@ -93,7 +93,7 @@ Sample Data
 
 The examples in this guide use the following sample documents. Each
 document represents a fruit in a store's inventory and contains
-information about its quantity. Some documents contain additional fields
+information about its quantity. Some documents contain fields
 that describe the fruit or its vendors.
 
 .. literalinclude:: /includes/fundamentals/code-snippets/crud/query.rs
@@ -226,7 +226,7 @@ divisible by ``3``:
 .. note::
 
    If a query filter contains a literal value query with multiple field-value pairs,
-   the driver matches documents that meet all of the criteria.
+   the driver matches documents that meet all the criteria.
 
    For example, the following queries produce equivalent results:
 

source/fundamentals/crud/read-operations/retrieve.txt

@@ -67,17 +67,10 @@ Find Operations
 Use find operations to retrieve data from MongoDB. Find operations
 consist of the ``find()`` and ``find_one()`` methods.
 
-You can also run find operations after starting a session with the
-``find_with_session()`` and ``find_one_with_session()`` methods. Both methods
-take an additional ``ClientSession`` parameter, or a logical session used for
-ordering sequential operations. To learn more about these two methods, see the
-API documentation for `find_with_session() <{+api+}/struct.Collection.html#method.find_with_session>`__
-and `find_one_with_session() <{+api+}/struct.Collection.html#method.find_one_with_session>`__.
-
 Find All Matching Documents
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-To find *all of the documents* that match your criteria, use the
+To find *all the documents* that match your criteria, use the
 ``find()`` method. This method takes a query filter as a parameter. A
 query filter consists of the fields and values that form criteria for
 documents to match.
@@ -281,7 +274,7 @@ To learn more about aggregations and view aggregation examples, see the :ref:`ru
 The method returns the resulting documents in a ``Cursor`` type. If
 your aggregation pipeline does not contain a :manual:`$match
 </reference/operator/aggregation/match/>` stage, the pipeline processes
-all of the documents in the collection.
+all the documents in the collection.
 
 Modify Aggregation Behavior
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~

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

@@ -177,9 +177,9 @@ following parameters:
 
 .. note::
 
-   If the preceding example used the ``delete_one()`` method instead of
-   ``delete_many()`` for the delete operation, the driver would delete
-   the first of the two documents that matched the query filter.
+   If you use the ``delete_one()`` method instead of
+   ``delete_many()`` in the preceding code example, the driver deletes
+   only the first of the two documents that match the query filter.
 
 .. _rust-crud-del-addtl-info:
 

source/fundamentals/database-collection.txt

@@ -100,7 +100,7 @@ the ``list_database_names()`` method:
 Drop a Database
 ---------------
 
-Dropping a database permanently deletes all of the data in that database's
+Dropping a database permanently deletes all the data in that database's
 collections. To drop a database, call the `drop()
 <{+api+}/struct.Database.html#method.drop>`__ method
 on your ``Database`` instance. The following code shows
@@ -256,7 +256,7 @@ a database referenced by the ``db`` variable by using the
 Drop a Collection
 -----------------
 
-Dropping a collection permanently deletes all of the data in that
+Dropping a collection permanently deletes all the data in that
 collection. To drop a collection, call the `drop()
 <{+api+}/struct.Collection.html#method.drop>`__ method
 on your ``Collection`` instance. The following code shows

source/fundamentals/enterprise-auth.txt

@@ -92,8 +92,8 @@ authentication mechanism by using the following placeholders:
 
    Because your credentials are stored outside of MongoDB, you must use the
    ``$external`` database for authentication. The ``source`` field of
-   the ``Credential`` struct defaults to ``$external``, so you do
-   not need to explicitly set this field.
+   the ``Credential`` struct defaults to ``$external``, so you can omit
+   this field.
 
 Alternatively, you can authenticate by using a connection string URI by
 setting the value of the ``authMechanism`` connection string option to ``PLAIN``.

source/fundamentals/stable-api.txt

@@ -57,7 +57,7 @@ are compatible with that version.
 
 .. note::
 
-   The {+driver-long+} currently supports only {+stable-api+} version 1.
+   The {+driver-long+} supports only {+stable-api+} version 1.
 
 API Version Specification Example
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

source/fundamentals/tracing-logging.txt

@@ -17,19 +17,17 @@ In this guide, you can learn how to use the {+driver-short+} to configure
 **tracing** and **logging** for your application. Tracing and logging
 are two frameworks for observing your application. Logging allows you to
 view a discrete, event-based log of driver activities, while tracing
-provides a continuous view. Logs might help you identify an issue in
-your application, while a trace might help you locate the reason for the
-issue.
+provides a continuous view.
 
 In the {+driver-short+}, the functionalities of tracing and logging do not
 differ greatly. However, when you enable tracing, the driver emits messages in a
-more structured format, which can make it easier for your application to
+more structured format, which can make it more convenient for your application to
 consume event messages programmatically.
 
 Tracers and loggers log messages at a severity, or verbosity, level that you
 can specify. By enabling one of these components in your application,
-you can receive information about your application's activities at a
-high level, a detailed level, or somewhere in between.
+you can receive information about your application's activities at
+different levels of detail.
 
 .. tip::
 
@@ -90,8 +88,8 @@ against and their corresponding targets:
 To specify the logging component and severity level, you can set the
 ``RUST_LOG`` environment variable when you compile and run your
 application. Specify the logging component by setting the value of
-``RUST_LOG`` to one of the targets provided in the preceding table,
-along with a severity level.
+``RUST_LOG`` to one of the targets provided in the preceding table and
+including a severity level.
 
 The following code shows a command to execute a program that records
 connection events at the ``debug`` level: