[Node.js] Style guide fixes for TDBX vale rules (#842)

* apply vale rules

Author: rachel-mack

source/connection-troubleshooting.txt

@@ -29,7 +29,7 @@ using the {+driver-long+} to connect to a MongoDB deployment.
      {+driver-short+}
    - The :ref:`Issues & Help <node-issues-help>` page, which has
      information about reporting bugs, contributing to the driver, and 
-     finding additional resources
+     finding more resources
    - The `MongoDB Community Forums <https://community.mongodb.com>`__ for
      questions, discussions, or general technical support
 
@@ -139,8 +139,7 @@ file descriptor limit in your operating system.
 
 .. warning::
 
-   Changing the configuration of your operating system should always be done
-   with caution.
+   Always be cautious when changing the configuration of your operating system.
 
 Authentication Error
 ~~~~~~~~~~~~~~~~~~~~
@@ -320,8 +319,8 @@ time the driver spends attempting to establish the connection by using the
 :manual:`Timeout Options </reference/connection-string/#timeout-options>` in
 the Server manual.
 
-You should ensure the ``connectTimeoutMS`` setting is not lower than
-the highest network latency you have to a member of the set. If one of the
+Ensure the ``connectTimeoutMS`` setting is not lower than
+the highest network latency you have for a member of the set. If one of the
 secondary members has a latency of 10000 milliseconds, setting the
 ``connectTimeoutMS`` to 9000 prevents the driver from ever connecting to that
 member.

source/faq.txt

@@ -40,7 +40,7 @@ the value of ``maxPoolSize``, the next request to that server will wait
 until a connection becomes available.
 
 In addition to the sockets needed to support your application's requests,
-each ``MongoClient`` instance opens two additional sockets per server
+each ``MongoClient`` instance opens two more sockets per server
 in your MongoDB topology for monitoring the server's state.
 For example, a client connected to a three-node replica set opens six
 monitoring sockets. If the application uses the default setting for
@@ -187,7 +187,7 @@ driver correctly closed the corresponding socket.
 To make sure that the driver correctly closes the socket in these cases,
 set the ``socketTimeoutMS`` option. When a MongoDB process times out, the driver
 will close the socket. We recommend that you select a value
-for ``socketTimeoutMS`` that is two to three times as long as the
+for ``socketTimeoutMS`` that is two to three times longer than the
 expected duration of the slowest operation that your application executes.
 
 How Can I Prevent Sockets From Timing Out Before They Become Active?

source/fundamentals/aggregation.txt

@@ -36,8 +36,8 @@ assembles the initial parts and materials into finished products.
 The **aggregation pipeline** is the assembly line, **aggregation stages** are the assembly stations, and
 **operator expressions** are the specialized tools.
 
-Aggregation vs. Query Operations
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Comparing Aggregation and Query Operations
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Using query operations, such as the ``find()`` method, you can perform the following actions:
 
@@ -58,9 +58,9 @@ Aggregation operations have some :manual:`limitations </core/aggregation-pipelin
 - Returned documents must not violate the :manual:`BSON-document size limit </reference/limits/#mongodb-limit-BSON-Document-Size>`
   of 16 megabytes.
 
-- Pipeline stages have a memory limit of 100 megabytes by default. If necessary, you may exceed this limit by setting the ``allowDiskUse``
-  property of ``AggregateOptions`` to ``true``. See the
-  `AggregateOptions API documentation <{+api+}/interfaces/AggregateOptions.html>`__
+- Pipeline stages have a memory limit of 100 megabytes by default. You can exceed this
+  limit by setting the ``allowDiskUse`` property of ``AggregateOptions`` to ``true``. See
+  the `AggregateOptions API documentation <{+api+}/interfaces/AggregateOptions.html>`__
   for more details.
 
 .. important:: $graphLookup exception
@@ -69,8 +69,8 @@ Aggregation operations have some :manual:`limitations </core/aggregation-pipelin
    </reference/operator/aggregation/graphLookup/>` stage has a strict
    memory limit of 100 megabytes and will ignore ``allowDiskUse``.
 
-Useful References
-~~~~~~~~~~~~~~~~~
+References
+~~~~~~~~~~
 
 To learn more about aggregation concepts, see the following pages in the
 Server manual:
@@ -117,7 +117,7 @@ In the example, the aggregation pipeline uses the following aggregation stages:
    :language: javascript
    :dedent:
 
-This example should produce the following output:
+This example produces the following output:
 
 .. code-block:: json
    :copyable: false

source/fundamentals/authentication/enterprise-mechanisms.txt

@@ -91,8 +91,8 @@ The following code sample authenticates to Kerberos for UNIX using ``GSSAPI``.
 
 .. note::
    The method refers to the ``GSSAPI`` authentication mechanism instead
-   of ``Kerberos`` because the driver authenticates via
-   `GSSAPI RFC-4652 <https://tools.ietf.org/html/rfc4752>`_ the SASL
+   of ``Kerberos`` because the driver authenticates through
+   `GSSAPI RFC-4652 <https://tools.ietf.org/html/rfc4752>`_, the SASL
    mechanism.
 
 ``LDAP (PLAIN)``

source/fundamentals/authentication/mechanisms.txt

@@ -341,5 +341,5 @@ connection URI.
    * - ``tlsAllowInvalidHostnames``
      - boolean
      - ``false``
-     - Specifies whether the driver should permit a mismatch between the
+     - Specifies whether the driver raises an error when there is a mismatch between the
        server hostname and TLS certificate hostname.

source/fundamentals/bson/undefined-values.txt

@@ -76,7 +76,7 @@ You can specify the ``ignoreUndefined`` setting at the following levels:
 - The operation level
 
 The ``ignoreUndefined`` setting automatically applies to the scope of the
-object instance in which you specified it, as well as any other objects created
+object instance in which you specified it and any other objects created
 from that instance.
 
 For example, if you set the ``ignoreUndefined`` setting when

source/fundamentals/bson/utf8-validation.txt

@@ -32,7 +32,7 @@ between your application and MongoDB.
 .. note::
 
    The current version of the {+driver-short+} automatically substitutes
-   invalid UTF-8 characters with alternate valid UTF-8 ones prior to
+   invalid UTF-8 characters with alternate valid UTF-8 ones before
    validation when you send data to MongoDB. Therefore, the validation
    only throws an error when the setting is enabled and the driver
    receives invalid UTF-8 document data from MongoDB.
@@ -45,7 +45,7 @@ Read the sections below to learn how to set UTF-8 validation using the
 Specify the UTF-8 Validation Setting
 ------------------------------------
 
-You can specify whether the driver should perform UTF-8 validation by
+You can specify whether the driver performs UTF-8 validation by
 defining the ``enableUtf8Validation`` setting in the options parameter
 when you create a client, reference a database or collection, or call a
 CRUD operation. If you omit the setting, the driver enables UTF-8 validation.

source/fundamentals/connection/connect.txt

@@ -26,10 +26,9 @@ a MongoDB instance, or a replica set using the Node.js driver.
 Connection URI
 --------------
 
-The **connection URI** is the set of instructions that the driver uses to
-connect to a MongoDB deployment. It instructs the driver on how it should
-connect to MongoDB and how it should behave while connected. The following
-example shows each part of the connection URI:
+The **connection URI** is the set of instructions that the driver uses to connect to a
+MongoDB deployment. It tells the driver how to connect to MongoDB and how to behave
+while connected. The following example shows each part of the connection URI:
 
 .. figure:: /includes/figures/dns_seedlist_connection_string_parts.png
    :alt: Each part of the connection string

source/fundamentals/connection/connection-options.txt

@@ -45,8 +45,8 @@ parameters of the connection URI to specify the behavior of the client.
    * - **authMechanismProperties**
      - comma separated key:value pairs, for example, "opt1:val1,opt2:val2"
      - ``null``
-     - Specifies additional options provided for authentication, such as
-       enabling hostname canonicalization for GSSAPI.
+     - Specifies other options provided for authentication, such as the option to enable
+       hostname canonicalization for GSSAPI.
 
    * - **authSource**
      - string

source/fundamentals/connection/network-compression.txt

@@ -56,7 +56,7 @@ by specifying the algorithms in one of two ways:
       :tabid: mongoclientoptions
 
       To enable compression using the `MongoClientOptions <{+api+}/api/global.html#MongoClientOptions>`__,
-      pass the ``compressors`` option along with the compression
+      pass the ``compressors`` option and the compression
       algorithm you want to use. You can specify one or more compression
       algorithms, separating them with commas: