DOCSP-36900: Quarterly tasks (#345)

* DOCSP-36900: Quarterly tasks

* more fixes

* vale fix

* RM feedback

* remove info

(cherry picked from commit 4b0ba1f)

Author: norareidy

source/faq.txt

@@ -70,11 +70,11 @@ following cases:
   rate-limits on connection creation.
 
 You can set the minimum number of concurrent connections to
-each server with the ``minPoolSize`` option, which defaults to ``0``. The connection pool
-will be initialized with this number of sockets. If sockets are closed
-due to any network errors, causing the total number of sockets (both in
-use and idle) to drop below the minimum, more sockets are opened until
-the minimum is reached.
+each server by using the ``minPoolSize`` option, which defaults to ``0``.
+After setting ``minPoolSize``, the connection pool is initialized with
+this number of sockets. If sockets close due to any network errors, causing
+the total number of sockets (both in use and idle) to drop below the minimum, more sockets
+open until the minimum is reached.
 
 You can set the maximum number of milliseconds that a connection can
 remain idle in the pool before being removed and replaced with

source/fundamentals/aggregation.txt

@@ -39,7 +39,7 @@ finished product resembles the **aggregated result**.
 Compare Operations
 ------------------
 
-The following table lists the tasks you can perform with find and aggregation operations.
+The following table lists the tasks you can perform by using find and aggregation operations.
 
 .. list-table::
    :header-rows: 1
@@ -93,7 +93,7 @@ in the ``tea`` collection:
    :dedent:
 
 To run the examples in this section, load the sample data into the
-``tea`` collection in the ``db`` database with the following snippet:
+``tea`` collection in the ``db`` database by using the following snippet:
 
 .. literalinclude:: /includes/fundamentals/code-snippets/aggregation.go
    :start-after: begin insert docs

source/fundamentals/auth.txt

@@ -45,7 +45,7 @@ type . To configure these options, pass a ``Credential`` type to the
 method of the `ClientOptions <{+api+}/mongo/options#ClientOptions>`__
 type.
 
-The following sections demonstrate this process with the five
+The following sections demonstrate this process by using the five
 mechanisms the MongoDB Community Edition supports.
 
 Example Conventions
@@ -149,7 +149,7 @@ To specify the ``SCRAM-SHA-256`` authentication mechanism, assign the
    3.0, 3.2, 3.4, and 3.6.
 
 ``SCRAM-SHA-1`` is a salted challenge-response mechanism (SCRAM) that uses your
-username and password, encrypted with the ``SHA-1`` algorithm, to authenticate
+username and password, encrypted using the ``SHA-1`` algorithm, to authenticate
 your user.
 
 To specify the ``SCRAM-SHA-1`` authentication mechanism, assign the

source/fundamentals/bson.txt

@@ -43,7 +43,7 @@ The {+driver-short+} provides four main types for working with BSON data:
 - ``E``: A single element inside a D type
 
 The following example demonstrates how to construct a query filter by using the
-``bson.D`` type to match documents with a ``quantity`` field value greater
+``bson.D`` type to match documents in which the ``quantity`` field value is greater
 than 100:
 
 .. code-block:: go

source/fundamentals/collations.txt

@@ -58,7 +58,7 @@ Specify a Collation
 
 To specify a collation, create a ``Collation`` object. You must define the ``Locale`` field
 of the ``Collation`` object; all other fields are optional. For example, the following code
-snippet specifies a ``Collation`` object with the ``"en_US"`` locale collation:
+example specifies a ``Collation`` object with the ``"en_US"`` locale collation:
 
 .. code-block:: go
 
@@ -100,7 +100,7 @@ Use the Default Collation Example
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 If you call an operation that uses a collation on the ``books`` collection, the operation
-will now use the default collation specified in the :ref:`golang-create-collection`.
+uses the default collation specified in the :ref:`golang-create-collection`.
 
 Assume the ``books`` collection contains the following documents:
 
@@ -173,8 +173,8 @@ doesn't perform the ordering for sorting operations in-memory.
 
 To use the index in an operation, your operation must use the same collation as the one
 specified in the index. Additionally, ensure that the operation is covered by the index that
-contains the collation. Set a collation through an ``IndexOptions`` object and call the
-``CreateOne()`` method with your options object as an argument.
+contains the collation. Set a collation through an ``IndexOptions`` object and pass this object
+as an argument to the ``CreateOne()`` method.
 
 Example
 ~~~~~~~
@@ -234,8 +234,8 @@ Example
 You can use operations that support collation to update and query documents in the 
 ``books`` collection. 
 
-The following example uses the ``Find()`` method to return documents with ``length`` 
-values greater than ``"1000"``. The ``NumericOrdering`` collation field has a value of
+The following example uses the ``Find()`` method to return documents in which the ``length`` 
+value is greater than ``"1000"``. The ``NumericOrdering`` collation field has a value of
 ``true`` to ensure that values are sorted in numerical order rather than alphabetical
 order:
 

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

@@ -39,7 +39,7 @@ in the ``courses`` collection:
    :dedent:
 
 To run the examples in this guide, load these documents into the
-``courses`` collection in the ``db`` database with the following snippet:
+``courses`` collection in the ``db`` database by using the following snippet:
 
 .. literalinclude:: /includes/fundamentals/code-snippets/CRUD/changeStream.go
    :language: go
@@ -77,7 +77,7 @@ outputs all changes:
    :start-after: begin open stream
    :end-before: end open stream
 
-If you modify the ``courses`` collection in a separate program or shell, this code will print
+If you modify the ``courses`` collection in a separate program or shell, this code prints
 your changes as they occur. Inserting a document with a ``title`` value
 of ``"Advanced Screenwriting"`` and an ``enrollment`` value of ``20``
 results in the following change event:

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

@@ -36,7 +36,7 @@ in the ``tea`` collection:
    :dedent:
 
 To run the examples in this guide, load these documents into the
-``tea`` collection in the ``db`` database with the following snippet:
+``tea`` collection in the ``db`` database by using the following snippet:
 
 .. literalinclude:: /includes/fundamentals/code-snippets/CRUD/retrieve.go
    :language: go

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

@@ -175,8 +175,8 @@ the following documents:
    {"title":"Plate Tectonics","enrollment":35}
 
 You can sort on additional fields to resolve ties in the original sort.
-If you want to guarantee a specific order for documents, you should
-select sort fields that will not result in additional ties.
+If you want to guarantee a specific order for documents, select sort fields
+that do not result in ties.
 
 Example
 ```````

source/fundamentals/geo.txt

@@ -179,7 +179,7 @@ queries:
 ~~~~~~~~
 To query data stored in the GeoJSON format, add the field containing
 both the ``type`` and ``coordinates`` to a ``2dsphere`` index. The
-following snippet creates a ``2dsphere`` index on the ``location`` field:
+following example creates a ``2dsphere`` index on the ``location`` field:
 
 .. code-block:: go
 
@@ -196,7 +196,7 @@ following snippet creates a ``2dsphere`` index on the ``location`` field:
 2d
 ~~
 To query data stored as legacy coordinate pairs, you must add the field containing
-legacy coordinate pairs to  a ``2d`` index. The following snippet creates a
+legacy coordinate pairs to  a ``2d`` index. The following example creates a
 ``2d`` index on the ``coordinates`` field:
 
 .. code-block:: go

source/fundamentals/logging.txt

@@ -249,7 +249,7 @@ This example demonstrates how to define and implement a custom logger.
 
       .. note::
 
-         The preceding code snippet uses a ``Mutex`` type in the
+         The preceding code example uses a ``Mutex`` type in the
          ``CustomLogger`` struct to ensure atomic writes and prevent
          race conditions. Setting a ``Mutex`` makes your logger safe for
          concurrent use by multiple goroutines.