DOCSP-33948: Atomic typos and cleanup (#829)

* DOCSP-33948: Atomic typos and cleanup

* tagging

* vale

* vale fix

* edit

* MW re-review

* vale

Author: norareidy

source/connection-troubleshooting.txt

@@ -4,6 +4,13 @@
 Connection Troubleshooting
 ==========================
 
+.. facet::
+   :name: genre
+   :values: reference
+
+.. meta:: 
+   :keywords: code example, node.js, disconnected, help
+
 .. contents:: On this page
    :local:
    :backlinks: none
@@ -283,7 +290,7 @@ The following section describes a method that may help resolve the issue.
 Check the Number of Connections
 -------------------------------
 
-If you need to create more open connections, increase ``maxPoolSize``. For more
+To create more open connections, increase the value of ``maxPoolSize``. For more
 information about checking the number of connections, see
 :ref:`Check the Number of Connections <node-troubleshooting-connection-number-connections>`
 in the Error Sending Message section.

source/faq.txt

@@ -135,8 +135,8 @@ What Is the Difference Between "connectTimeoutMS", "socketTimeoutMS" and "maxTim
        have already been connected.
    * - **maxTimeMS**
      - `maxTimeMS <{+api+}/classes/FindCursor.html#maxTimeMS>`__
-       specifies the maximum amount of time the server 
-       should wait for an operation to complete after it has reached the
+       specifies the maximum amount of time that the server 
+       waits for an operation to complete after it has reached the
        server. If an operation runs over the specified time limit, it
        returns a timeout error. You can pass ``maxTimeMS`` only to an
        individual operation or to a cursor.
@@ -339,8 +339,8 @@ The connection string passed to the driver must use exact hostnames for
 the servers as set in the :manual:`Replica Set Config </reference/replica-configuration/>`.
 Given the following configuration settings for your Replica Set, in
 order for the Replica Set discovery and :manual:`failover
-</reference/glossary/#term-failover>` to work the driver should be able
-to reach ``server1``, ``server2``, and ``server3``.
+</reference/glossary/#term-failover>` to work, the driver must have access
+to ``server1``, ``server2``, and ``server3``.
 
 .. code-block:: JSON
 

source/fundamentals/connection/connection-options.txt

@@ -4,6 +4,13 @@
 Connection Options
 ==================
 
+.. facet::
+   :name: genre
+   :values: reference
+
+.. meta:: 
+   :keywords: node.js, customize
+
 This section explains the MongoDB connection and authentication options
 supported by the driver. You can pass the connection options as
 parameters of the connection URI to specify the behavior of the client.
@@ -44,7 +51,7 @@ parameters of the connection URI to specify the behavior of the client.
    * - **authSource**
      - string
      - ``null``
-     - Specifies the database that connections should authenticate against.
+     - Specifies the database that connections authenticate against.
 
    * - **compressors**
      - comma separated list of strings, for example, "snappy,zlib,zstd"
@@ -118,8 +125,8 @@ parameters of the connection URI to specify the behavior of the client.
    * - **minPoolSize**
      - non-negative integer
      - ``0``
-     - Specifies the number of connections the driver should create and
-       maintain in the connection pool even when no operations are occurring.
+     - Specifies the number of connections the driver creates and
+       maintains in the connection pool even when no operations are occurring.
        This count includes connections in use.
 
    * - **proxyHost**
@@ -246,17 +253,16 @@ parameters of the connection URI to specify the behavior of the client.
    * - **tlsAllowInvalidCertificates**
      - boolean
      - ``false``
-     - Specifies whether the driver should error when the server’s
-       TLS certificate is invalid. You should only set this option to
-       ``true`` for testing purposes.
+     - Specifies whether the driver generates an error when the server's
+       TLS certificate is invalid. Set this option to ``true`` for testing
+       purposes only.
 
    * - **tlsAllowInvalidHostnames**
      - boolean
      - ``false``
-     - Specifies whether the driver should error when there is a mismatch
-       between the server’s hostname and the hostname specified by the
-       TLS certificate. You should only set this option to
-       ``true`` for testing purposes.
+     - Specifies whether the driver generates an error when there is a mismatch
+       between the server's hostname and the hostname specified by the
+       TLS certificate. Set this option to ``true`` for testing purposes only.
 
    * - **tlsCAFile**
      - string
@@ -285,8 +291,8 @@ parameters of the connection URI to specify the behavior of the client.
      - boolean
      - ``false``
      - Specifies to relax TLS constraints as much as possible, such as
-       allowing invalid certificates or hostname mismatches. You should
-       only set this option to ``true`` for testing purposes.
+       allowing invalid certificates or hostname mismatches. Set this option
+       to ``true`` for testing purposes only.
 
    * - **w**
      - non-negative integer or string

source/fundamentals/connection/tls.txt

@@ -4,6 +4,13 @@
 Enable TLS on a Connection
 ==========================
 
+.. facet::
+   :name: genre
+   :values: reference
+
+.. meta:: 
+   :keywords: code example, node.js, security, encrypt
+
 .. contents:: On this page
    :local:
    :backlinks: none
@@ -101,7 +108,7 @@ files.
    certificates generated and signed by the same certificate authority.
    For testing, you can use self-signed certificates.
 
-The following list describes the components that you need to establish
+The following list describes the components required to establish
 a connection with TLS:
 
 .. list-table::

source/fundamentals/crud/compound-operations.txt

@@ -4,6 +4,13 @@
 Compound Operations
 ===================
 
+.. facet::
+   :name: genre
+   :values: reference
+
+.. meta:: 
+   :keywords: node.js, atomic operation, read, write
+
 .. contents:: On this page
    :local:
    :backlinks: none
@@ -13,9 +20,9 @@ Compound Operations
 Overview
 --------
 
-Most database requests need to either read data out of a database or
-write data into a database. However, there are instances where you may
-need to read and write data in a single interaction.
+Most database requests either read data from a database or write data into
+a database. However, there are instances where you may require a single
+operation that reads and writes data.
 
 **Compound operations** combine read and write operations
 in a single atomic statement, so there's no chance of data changing in

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

@@ -80,7 +80,7 @@ Legacy coordinate pairs use the following structure:
 
    <field> : [ x, y ]
 
-The field should contain an array of two values in which the first represents
+The field contains an array of two values in which the first represents
 the ``x`` axis value and the second represents the ``y`` axis value.
 
 To enable querying using legacy coordinate pairs, create a ``2d`` index on

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

@@ -70,12 +70,11 @@ field of each document:
      console.dir(doc);
    }
 
-The projection document specifies a value of ``1`` for ``name`` to
-indicate that the read operation result should *include* the ``name``
-field of each returned document. As a result, this projection implicitly
-excludes the ``qty`` and ``rating`` fields. Passing this projection to
-``find()`` with an empty query document and no sort document yields
-the following results:
+The projection document specifies a value of ``1`` for ``name``. This instructs
+the operation to *include* the ``name`` field of each returned document in
+the results and *exclude* the ``qty`` and ``rating`` fields. Passing this projection
+to ``find()`` with an empty query document and no sort document yields the following
+results:
 
 .. code-block:: json
    :copyable: false
@@ -110,12 +109,11 @@ returned documents.
      console.dir(doc);
    }
 
-The projection document specifies a value of ``1`` for ``name`` to
-indicate that the read operation result should *include* the ``name``
-field of each returned document. As a result, this projection implicitly
-excludes the ``qty`` and ``rating`` fields. Passing this projection to
-``find()`` with an empty query document and no sort document yields
-the following results:
+The projection document specifies a value of ``1`` for ``name`` and ``0`` for 
+``_id``. This instructs the operation to *include* the ``name`` field of each
+returned document in the results and *exclude* the ``_id``, ``qty``, and ``rating``
+fields. Passing this projection to ``find()`` with an empty query document and
+no sort document yields the following results:
 
 .. code-block:: json
    :copyable: false

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

@@ -4,6 +4,13 @@
 Insert Documents
 ================
 
+.. facet::
+   :name: genre
+   :values: reference
+
+.. meta:: 
+   :keywords: code example, node.js, add data
+
 .. contents:: On this page
    :local:
    :backlinks: none
@@ -18,7 +25,7 @@ In this guide, you can learn how to insert documents into MongoDB.
 You can use MongoDB to retrieve, update and delete information. To
 perform any of those operations, that information, such as user profiles
 and orders, needs to exist in MongoDB. For that information to exist,
-you need to first perform an **insert operation**.
+you must first perform an **insert operation**.
 
 An insert operation inserts one or more documents into a MongoDB collection.
 The {+driver-short+} provides the following methods to perform insert

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

@@ -4,7 +4,12 @@
 Insert or Update in a Single Operation
 ======================================
 
-.. default-domain:: mongodb
+.. facet::
+   :name: genre
+   :values: reference
+
+.. meta:: 
+   :keywords: code example, node.js, write, add data
 
 .. contents:: On this page
    :local:
@@ -16,8 +21,8 @@ Overview
 --------
 
 If your application stores and modifies data in MongoDB, you probably use
-insert and update operations. In certain workflows, you may need to choose
-between an insert and update depending on whether the document exists.
+insert and update operations. In certain workflows, whether you perform
+an insert or update operation depends on whether the document exists.
 In these cases, you can streamline your application logic by using the
 ``upsert`` option available in the following methods:
 
@@ -69,7 +74,7 @@ Performing an Upsert
 
 Consider the case in which you want to add information about the food
 truck even if it does not currently exist in your collection. Rather than
-first querying whether it exists to determine whether we need to insert or
+first querying whether it exists to determine whether to insert or
 update the document, we can set ``upsert`` to ``true`` in our call to
 ``updateOne()`` as follows:
 

source/fundamentals/monitoring/cluster-monitoring.txt

@@ -4,7 +4,12 @@
 Cluster Monitoring
 ==================
 
-.. default-domain:: mongodb
+.. facet::
+   :name: genre
+   :values: reference
+
+.. meta:: 
+   :keywords: code example, node.js, watch
 
 .. contents:: On this page
    :local:
@@ -22,8 +27,8 @@ a change in the state of the instance or cluster that you connected to.
 For example, the driver creates an event when you establish a new connection
 or if the cluster elects a new primary.
 
-Read this guide if you need to record topology changes in your application or
-want to explore the information provided in these events.
+The following sections demonstrate how to record topology changes in your application
+and explore the information provided in these events.
 
 Event Subscription Example
 --------------------------