DOCSP-33952: Atomic typos (#319)

* DOCSP-33952: Atomic typos

* tagging

* style guide edits

* more tagging

* vale

* RR feedback

(cherry picked from commit 9b44ddd)

Author: norareidy

source/connection-troubleshooting.txt

@@ -4,6 +4,13 @@
 Connection Troubleshooting
 ==========================
 
+.. facet::
+   :name: genre
+   :values: reference
+
+.. meta::
+   :keywords: code example, disconnected, deployment
+
 .. contents:: On this page
    :local:
    :backlinks: none
@@ -27,7 +34,7 @@ using the {+driver-long+} to connect to a MongoDB deployment.
      questions, discussions, or general technical support
 
 Connection Error
-~~~~~~~~~~~~~~~~
+----------------
 
 The following error message is a general message indicating that the driver
 cannot connect to a server on the specified hostname or port:
@@ -42,7 +49,7 @@ The following sections describe methods that may help resolve the issue.
 .. _golang-troubleshooting-connection-string-port:
 
 Check Connection String
------------------------
+~~~~~~~~~~~~~~~~~~~~~~~
 
 Verify that the hostname and port number in the connection string are both
 accurate. In the sample error message, the hostname is ``127.0.0.1`` and the
@@ -52,7 +59,7 @@ port is ``27017``. The default port value for a MongoDB instance is
 .. _golang-troubleshooting-connection-firewall:
 
 Configure Firewall
-------------------
+~~~~~~~~~~~~~~~~~~
 
 Assuming that your MongoDB deployment uses the default port, verify that port
 ``27017`` is open in your firewall. If your deployment uses a different port,
@@ -64,7 +71,7 @@ verify the correct port is open in your firewall.
    used by your MongoDB instance.
 
 Authentication Error
-~~~~~~~~~~~~~~~~~~~~
+--------------------
 
 The {+driver-short+} can fail to connect to a MongoDB instance if
 the authorization is not configured correctly. In these cases, the driver raises
@@ -88,7 +95,7 @@ The following sections describe methods that may help resolve the issue.
 .. _golang-troubleshooting-connection-string-auth:
 
 Check Connection String
------------------------
+~~~~~~~~~~~~~~~~~~~~~~~
 
 An invalid connection string is the most common cause of authentication
 issues when attempting to connect to MongoDB.
@@ -110,15 +117,15 @@ are in the correct format.
 
       : / ? # [ ] @
 
-When connecting to a replica set, you should include all of the hosts
-in the replica set in your connection string. Separate each of the hosts
-in the connection string with a comma. This enables the driver to establish a
-connection if one of the hosts is unreachable.
+When connecting to a replica set, include all the replica set hosts
+in your connection string. Separate each of the hosts in the connection
+string with a comma. This enables the driver to establish a connection
+if one of the hosts is unreachable.
 
 .. _golang-troubleshooting-connection-auth-mechanism:
 
 Verify the Authentication Mechanism
------------------------------------
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Ensure that your credentials and authentication mechanism are correct. You can
 store your authentication credentials in environment variables or you can pass
@@ -130,7 +137,7 @@ To learn more about authentication, see the
 .. _golang-troubleshooting-connection-admin:
 
 Verify User Is in Authentication Database
------------------------------------------
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 To successfully authenticate a connection by using a username and password,
 the username must be defined in the authentication database. The default
@@ -146,7 +153,7 @@ database:
    client := mongo.Connect(uri)
 
 Error Sending Message
-~~~~~~~~~~~~~~~~~~~~~
+---------------------
 
 When the driver fails to send a command after you make a request,
 it often displays the following general error message:
@@ -159,38 +166,38 @@ it often displays the following general error message:
 The following sections describe methods that may help resolve the issue.
 
 Check Connection String
------------------------
+~~~~~~~~~~~~~~~~~~~~~~~
 
 Verify that the connection string in your app is accurate. For more information
 about verifying your connection string, see
 :ref:`Connection Error <golang-troubleshooting-connection-string-port>`
 and :ref:`Authentication Error <golang-troubleshooting-connection-string-auth>`.
 
 Verify the Authentication Mechanism
------------------------------------
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Make sure you are using the correct authentication mechanism and credentials.
 For more information about authentication errors, see
 :ref:`Authentication Error <golang-troubleshooting-connection-auth-mechanism>`.
 
 Verify User Is in Authentication Database
------------------------------------------
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Verify the user is in the correct authentication database. For more
 information about the authentication database, see
 :ref:`Authentication Error <golang-troubleshooting-connection-admin>`.
 
 Configure Firewall
-------------------
+~~~~~~~~~~~~~~~~~~
 
-The firewall needs to have an open port for communicating with the MongoDB
+The firewall must have an open port for communicating with the MongoDB
 instance. For more information about configuring the firewall, see
 :ref:`Connection Error <golang-troubleshooting-connection-firewall>`.
 
 .. _golang-troubleshooting-connection-number-connections:
 
 Check the Number of Connections
--------------------------------
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Each ``MongoClient`` instance supports a maximum number of concurrent open
 connections in its connection pool. The configuration parameter ``maxPoolSize``
@@ -203,7 +210,7 @@ connection pooling works, see
 in the FAQ.
 
 Timeout Error
-~~~~~~~~~~~~~
+-------------
 
 Sometimes when you send a request through the driver to the server, the request
 times out. When this happens, you might receive an error message
@@ -218,7 +225,7 @@ If you receive this error, try the following methods to resolve the
 issue.
 
 Set Timeout Option
-------------------
+~~~~~~~~~~~~~~~~~~
 
 The ``Client`` supports a single ``Timeout`` option that controls the amount of
 time a single operation can take to execute. You can set this value by using
@@ -234,7 +241,7 @@ connection string option:
    client := mongo.Connect(uri)
 
 Check the Number of Connections
--------------------------------
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The number of connections to the server may exceed ``maxPoolSize``. For more
 information about checking the number of connections, see

source/faq.txt

@@ -4,7 +4,12 @@
 FAQ
 ===
 
-.. default-domain:: mongodb
+.. facet::
+   :name: genre
+   :values: reference
+
+.. meta::
+   :keywords: code example, connection error, question, help
 
 .. contents:: On this page
    :local:
@@ -46,7 +51,7 @@ The ``Client`` instance opens two additional sockets per server in your
 MongoDB topology for monitoring the server's state.
 
 For example, a client connected to a 3-node replica set opens 6
-monitoring sockets. It also opens as many sockets as needed to support
+monitoring sockets. It also opens the necessary sockets to support
 an application's concurrent operations on each server, up to
 the value of ``maxPoolSize``. If ``maxPoolSize`` is ``100`` and the
 application only uses the primary (the default), then only the primary
@@ -150,10 +155,10 @@ variable as a ``bson.D`` type so that the driver can convert it to BSON:
 How Do I Convert a BSON Document to JSON?
 -----------------------------------------
 
-The driver provides a variety of marshaller methods that can be used to
+The driver provides a variety of marshaler methods that can be used to
 convert a BSON document to JSON, such as the ``MarshalExtJSON()``
 method. To view a readable form of the JSON encoding, you must use
-an unmarshaller method or string type-casting to parse the JSON byte
+an unmarshaler method or string type-casting to parse the JSON byte
 format.
 
 The following code converts a BSON document to JSON using the

source/fundamentals/auth.txt

@@ -238,7 +238,7 @@ they are listed:
       .. literalinclude:: /includes/fundamentals/code-snippets/authentication/aws-connection-string.go
          :language: go
 
-      If you need to specify an AWS session token, use the temporary
+      If you must specify an AWS session token, use the temporary
       credentials returned from an `assume role request <https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html>`__.
 
       To use temporary credentials, assign the value of your ``sessionToken`` to 
@@ -261,8 +261,8 @@ they are listed:
 
       .. note::
 
-         If you don't need an AWS session token for the role you're
-         authenticating with, omit the line containing ``AWS_SESSION_TOKEN`` .
+         If you don't require an AWS session token for the role you're
+         authenticating with, omit the line containing ``AWS_SESSION_TOKEN``.
 
       After you've set the preceding environment variables, specify the ``MONGODB-AWS``
       authentication mechanism as shown in the following example:

source/fundamentals/bson.txt

@@ -331,9 +331,9 @@ user-defined struct by using methods from the ``bson`` package:
 .. note::
 
    You can use the ``Raw`` type to retrieve elements from a BSON
-   document byte slice without unmarshalling it to a Go type. This can
-   be useful if you need to look up individual elements without
-   unmarshalling the entire BSON document.
+   document byte slice without unmarshalling it to a Go type. This type
+   allows you to look up individual elements without unmarshalling
+   the entire BSON document.
 
 To learn more about the marshalling and unmarshalling methods used with the
 ``Cursor`` type, see the `Cursor API documentation <{+api+}/mongo#Cursor>`__

source/fundamentals/collations.txt

@@ -166,8 +166,8 @@ Set a Collation on an Index
 ---------------------------
 
 You can apply a collation when you create a new index on a collection. The index stores
-an ordered representation of the documents in the collection so your MongoDB instance
-does not need to perform the ordering for sorting operations in-memory. 
+an ordered representation of the documents in the collection, so your MongoDB instance
+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

source/fundamentals/connections/connection-guide.txt

@@ -69,8 +69,8 @@ options, read the :ref:`golang-connection-options` section of this guide.
 Connection Example
 ~~~~~~~~~~~~~~~~~~
 
-To connect to MongoDB, you need to create a client. A client manages
-your connections and runs database commands.
+To connect to MongoDB, you must create a client. A client manages your
+connections and runs database commands.
 
 .. tip:: Reuse Your Client
 
@@ -116,7 +116,7 @@ verify that the connection is successful:
    To learn about connecting to Atlas Serverless, see the
    :ref:`Serverless Instance Limitations page
    <atlas-serverless-drivers>` to identify the minimum driver version
-   you need.
+   required.
 
 --------------------------------
 Other Ways to Connect to MongoDB
@@ -159,7 +159,7 @@ When connecting to a replica set, the driver takes the following actions by defa
 
 .. tip::
 
-   You only need to specify one host to connect to a replica set.
+   You can specify just one host to connect to a replica set.
    However, to ensure connectivity when the specified host
    is unavailable, you should provide the full list of hosts.
 

source/fundamentals/context.txt

@@ -4,7 +4,12 @@
 Context
 =======
 
-.. default-domain:: mongodb
+.. facet::
+   :name: genre
+   :values: reference
+
+.. meta::
+   :keywords: code example, unblock
 
 .. contents:: On this page
    :local:
@@ -17,7 +22,7 @@ Overview
 
 The {+driver-long+} uses the `context package
 <https://pkg.go.dev/context>`__ from Go's standard library to allow
-applications to signal timeouts and cancelations for any **blocking method**
+applications to signal timeouts and cancellations for any **blocking method**
 call. A blocking method relies on an external event, such as a network
 input or output, to proceed with its task.
 
@@ -72,19 +77,19 @@ The driver might block a method call if there are no available
 connections to check out.
 
 After selecting a server, the driver tries to check out a connection
-from the server’s connection pool. If the Context expires while checking
+from the server's connection pool. If the Context expires while checking
 out a connection, the method returns a timeout error.
 
 Connection Establishment
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
-The driver might block an method call if it needs to create a new
+The driver might block a method call if it must create a new
 connection.
 
-When the driver needs to create a new connection to execute an
-operation, the Context sets a timeout for the establishment process. The
-driver sets the timeout to either the Context expiration or connection
-timeout, whichever is shorter.
+When the driver creates a new connection to perform an operation, the
+Context sets a timeout for the establishment process. The driver sets the
+timeout to either the Context expiration or connection timeout, whichever is
+shorter.
 
 The following example sets the connection timeout to *1* second and the
 Context deadline to *2* seconds. Because the connection timeout is

source/fundamentals/crud/compound-operations.txt

@@ -31,8 +31,8 @@ MongoDB supports the following compound operations:
 
 .. tip::
 
-   If you need to read and write to more than one document, use
-   :ref:`transactions <golang-transactions>`.
+   To learn how to perform compound operations on more than one document
+   at a time, see the :ref:`Transactions <golang-transactions>` guide.
 
 Sample Data
 ~~~~~~~~~~~
@@ -79,8 +79,8 @@ the specified query filter and deletes it. The method returns a
    ``FindOneAndDelete()`` in that you cannot specify a sort order for the
    matched documents. 
 
-   If you don't need to find and delete a document in a single transaction, you can call 
-   the ``findOne()`` method followed by the ``deleteOne()`` method. 
+   To find a document and delete it in separate operations, call the
+	 ``findOne()`` method followed by the ``deleteOne()`` method.
 
 Modify Behavior
 ~~~~~~~~~~~~~~~
@@ -168,7 +168,7 @@ document.
    ``FindOneAndUpdate()`` in that you cannot specify a sort order for the
    matched documents. 
 
-   If you don't need to find and update a document in a single transaction, you can call 
+   To find a document and update it in separate operations, call 
    the ``findOne()`` method followed by the ``updateOne()`` method. 
 
 Modify Behavior

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

@@ -4,7 +4,12 @@
 Access Data From a Cursor
 =========================
 
-.. default-domain:: mongodb
+.. facet::
+   :name: genre
+   :values: reference
+
+.. meta::
+   :keywords: code example, read operation, see results, iterate
 
 .. contents:: On this page
    :local:
@@ -104,7 +109,7 @@ method:
 Close the Cursor
 ----------------
 
-When your application no longer needs to use a cursor, close the cursor
+When your application no longer requires a cursor, close the cursor
 with the ``Close()`` method. This method frees the resources your cursor
 consumes in both the client application and the MongoDB server.
 

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

@@ -309,7 +309,7 @@ Unordered
 
 To execute bulk write operations in any order and continue if an error
 occurs, specify ``false`` to the ``SetOrdered()`` method. The method
-reports the errors afterwards.
+reports the errors afterward.
 
 Example
 ```````