Docsp 16491 typos fundamentals (#111)

Co-authored-by: Nathan <[email protected]>

Author: biniona-mongodb

source/fundamentals/auth.txt

@@ -14,7 +14,7 @@ Overview
 --------
 
 In this guide, we show you how to authenticate with MongoDB using each
-**authentication mechanism** available in the MongoDB Community Edition.
+**authentication mechanism** available in MongoDB Community Edition.
 Authentication mechanisms are processes by which the driver and server
 confirm identity and establish trust to ensure security.
 
@@ -110,15 +110,15 @@ see the :manual:`SCRAM </core/security-scram/>` section of the server manual.
 
 ``SCRAM-SHA-256`` is a salted challenge-response authentication mechanism
 (SCRAM) that uses your username and password, encrypted with the ``SHA-256``
-algorithm to authenticate your user.
+algorithm, to authenticate your user.
 
 The following code snippets show how to specify the authentication mechanism,
 using the following placeholders:
 
-* ``username`` - your MongoDB username
-* ``password`` - your MongoDB user's password
-* ``hostname`` - network address of your MongoDB server, accessible by your client
-* ``port`` - port number of your MongoDB server
+* ``username`` - your MongoDB username.
+* ``password`` - your MongoDB user's password.
+* ``hostname`` - network address of your MongoDB server, accessible by your client.
+* ``port`` - port number of your MongoDB server.
 * ``authenticationDb`` - MongoDB database that contains your user's
   authentication data. If you omit this parameter, the driver uses the
   default value ``admin``.
@@ -161,16 +161,16 @@ mechanism:
    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 with the ``SHA-1`` algorithm, to authenticate
 your user.
 
 The following code snippets show how to specify the authentication mechanism,
 using the following placeholders:
 
-* ``username`` - your MongoDB username
-* ``password`` - your MongoDB user's password
-* ``hostname`` - network address of your MongoDB server, accessible by your client
-* ``port`` - port number of your MongoDB server
+* ``username`` - your MongoDB username.
+* ``password`` - your MongoDB user's password.
+* ``hostname`` - network address of your MongoDB server, accessible by your client.
+* ``port`` - port number of your MongoDB server.
 * ``authenticationDb`` - MongoDB database that contains your user's
   authentication data. If you omit this parameter, the driver uses the
   default value ``admin``.
@@ -215,7 +215,7 @@ mechanism was deprecated starting in MongoDB 3.6 and is no longer
 supported as of MongoDB 4.0.
 
 You cannot specify this method explicitly; refer to the fallback provided
-by the :ref:`Default authentication mechanism <default-auth-mechanism>` to
+by the :ref:`default authentication mechanism <default-auth-mechanism>` to
 connect using ``MONGODB-CR``.
 
 .. _mongodb-aws-auth-mechanism:
@@ -234,14 +234,14 @@ user.
 The following code snippets show how to specify the authentication mechanism,
 using the following placeholders:
 
-* ``username`` - value of your ``AWS_ACCESS_KEY_ID``
-* ``password`` - value your ``AWS_SECRET_ACCESS_KEY``
-* ``hostname`` - network address of your MongoDB server, accessible by your client
-* ``port`` - port number of your MongoDB server
+* ``username`` - value of your ``AWS_ACCESS_KEY_ID``.
+* ``password`` - value of your ``AWS_SECRET_ACCESS_KEY``.
+* ``hostname`` - network address of your MongoDB server, accessible by your client.
+* ``port`` - port number of your MongoDB server.
 * ``authenticationDb`` - MongoDB database that contains your user's
   authentication data. If you omit this parameter, the driver uses the
   default value ``admin``.
-* ``awsSessionToken`` - value of your ``AWS_SESSION_TOKEN`` *(optional)*
+* ``awsSessionToken`` - value of your ``AWS_SESSION_TOKEN``. *(optional)*
 
 Select the :guilabel:`Connection String` or the :guilabel:`MongoCredential`
 tab below for instructions and sample code for specifying this authentication
@@ -329,8 +329,8 @@ the subject name of the client certificate.
 The following code snippets show how to specify the authentication mechanism,
 using the following placeholders:
 
-* ``hostname`` - network address of your MongoDB server, accessible by your client
-* ``port`` - port number of your MongoDB server
+* ``hostname`` - network address of your MongoDB server, accessible by your client.
+* ``port`` - port number of your MongoDB server.
 * ``authenticationDb`` - MongoDB database that contains your user's
   authentication data. If you omit this parameter, the driver uses the
   default value ``admin``.
@@ -346,7 +346,7 @@ mechanism:
 
       To specify the ``X.509`` authentication mechanism using a connection
       string, assign the ``authMechanism`` parameter the value ``MONGODB-X509``
-      value to the ``authMechanism`` and enable TLS by assigning the ``tls``
+      and enable TLS by assigning the ``tls``
       parameter a ``true`` value. Your code to instantiate a ``MongoClient``
       should look something like this:
 

source/fundamentals/connection.txt

@@ -249,7 +249,7 @@ parameters of the connection URI to specify the behavior of the client.
 
    * - **maxPoolSize**
      - integer
-     - Specifies the maximum size of the instance connection pool.
+     - Specifies the maximum size of the connection pool.
 
    * - **waitQueueTimeoutMS**
      - integer
@@ -295,7 +295,7 @@ parameters of the connection URI to specify the behavior of the client.
      - boolean
      - Specifies that the driver should allow invalid hostnames for TLS
        connections. Has the same effect as setting
-       **tlsAllowInvalidHostnames** to true. To configure TLS security
+       **tlsAllowInvalidHostnames** to ``true``. To configure TLS security
        constraints in other ways, use a
        :ref:`custom SSLContext <tls-custom-sslContext>`.
 
@@ -420,12 +420,12 @@ parameters of the connection URI to specify the behavior of the client.
    * - **retryWrites**
      - boolean
      - Specifies that the driver must retry supported write operations
-       if they fail due to a network error. Defaults to true.
+       if they fail due to a network error. Defaults to ``true``.
 
    * - **retryReads**
      - boolean
      - Specifies that the driver must retry supported read operations
-       if they fail due to a network error. Defaults to true.
+       if they fail due to a network error. Defaults to ``true``.
 
    * - **uuidRepresentation**
      - string

source/fundamentals/connection/jndi.txt

@@ -7,10 +7,11 @@ Java Naming and Directory Interface (JNDI)
    :depth: 2
    :class: singlecol
 
+
 Overview
 --------
 
-MongoClientFactory includes a `JNDI
+``MongoClientFactory`` includes a `JNDI
 <http://docs.oracle.com/javase/8/docs/technotes/guides/jndi/index.html>`__
 ``ObjectFactory`` implementation that returns ``MongoClient`` instances
 based on a :ref:`connection URI <connection-uri>`. Follow the guides
@@ -49,7 +50,7 @@ below to configure your application to connect using a JNDI DataSource.
 
          .. note::
 
-            Replace the placeholder connection value URI in the ``property`` tag
+            Replace the placeholder connection value in the ``property`` tag
             with a value that points to your MongoDB installation.
 
       This will make a MongoClient instance accessible via the JNDI name
@@ -61,7 +62,7 @@ below to configure your application to connect using a JNDI DataSource.
       1. Copy the ``mongo-java-driver.jar`` jar file into the ``lib`` directory
          of your `Tomcat <http://tomcat.apache.org/>`__ installation.
 
-      #. In ``context.xml`` of your application, add a resource that references
+      #. In the ``context.xml`` file of your application, add a resource that references
          the ``MongoClientFactory`` class and the :ref:`connection string
          <connection-uri>` for the MongoDB cluster:
 
@@ -77,7 +78,7 @@ below to configure your application to connect using a JNDI DataSource.
 
          .. note::
 
-            Replace the placeholder connection value URI in the ``connectionString``
+            Replace the placeholder URI in the ``connectionString``
             attribute with a value that points to your MongoDB installation.
 
       #. In ``web.xml`` of your application, add a reference to the

source/fundamentals/connection/tls.txt

@@ -156,7 +156,7 @@ Disable Hostname Verification
 -----------------------------
 
 By default, the driver ensures that the hostname included in the server's
-TLS/SSL certificate(s) matches the hostname(s) provided when constructing
+TLS/SSL certificates matches the hostnames provided when constructing
 a ``MongoClient``. If you need to disable hostname verification for your
 application, you can explicitly disable this by setting the
 ``invalidHostNameAllowed`` property of the builder to ``true`` in the

source/fundamentals/data-formats/codecs.txt

@@ -20,7 +20,7 @@ In this guide, you can learn about **Codecs** and the supporting classes that
 handle the encoding and decoding of Java objects to and from BSON data in
 MongoDB. The ``Codec`` abstraction allows you to map any Java type to
 a corresponding BSON type. You can use this to map your domain objects
-directly to and from BSON instead of using an intermediate map-based one such
+directly to and from BSON instead of using an intermediate map-based object such
 as ``Document`` or ``BsonDocument``.
 
 You can learn how to specify custom encoding and decoding logic using
@@ -164,7 +164,7 @@ the ``fromCodecs()`` method:
 In the example above, we assign the ``CodecRegistry`` the following ``Codec``
 implementations:
 
-- IntegerCodec, a ``Codec`` that converts Integers and is part of the BSON package.
+- ``IntegerCodec``, a ``Codec`` that converts ``Integers`` and is part of the BSON package.
 - :ref:`PowerStatusCodec <codecs-powerstatus-codec>`, our sample ``Codec``
   that converts certain Java strings to BSON booleans.
 
@@ -221,7 +221,7 @@ section of this guide.
 
 When working with POJOs, consider using the  ``PojoCodecProvider`` to
 minimize duplicate code to convert commonly-used data types and customize
-the behavior. See our
+their behavior. See our
 :doc:`POJO Customization guide </fundamentals/data-formats/pojo-customization>`
 for more information.
 
@@ -347,7 +347,7 @@ After defining the conversion logic, we can perform the following:
 The following example class contains code that assigns the
 ``MonolightCodecProvider`` to the ``MongoCollection`` instance by passing it
 to the ``withCodecRegistry()`` method. The example class also inserts and
-retrieves data using the ``Monolight`` class and associated ``Codecs``:
+retrieves data using the ``Monolight`` class and associated codecs:
 
 .. literalinclude:: /includes/fundamentals/code-snippets/MonolightCodecExample.java
    :start-after: start class
@@ -369,4 +369,3 @@ see the following API Documentation:
 - :java-docs:`MongoClientSettings.getDefaultCodecRegistry() <apidocs/mongodb-driver-core/com/mongodb/MongoClientSettings.html#getDefaultCodecRegistry()>`
 - :java-docs:`Codec <apidocs/bson/org/bson/codecs/Codec.html>`
 - :java-docs:`CodecProvider <apidocs/bson/org/bson/codecs/configuration/CodecProvider.html>`
-

source/fundamentals/data-formats/document-data-format-bson.txt

@@ -16,7 +16,7 @@ Overview
 --------
 
 This guide explains the BSON data format, how MongoDB uses it, and how to
-install the BSON library independently of the MongoDB driver.
+install the BSON library independently of the MongoDB Java driver.
 
 BSON Data Format
 ----------------
@@ -36,7 +36,7 @@ MongoDB and BSON
 ----------------
 
 The MongoDB Java Driver, which uses the BSON library, allows you to work
-with BSON data by using one of the object types that implement the
+with BSON data by using one of the object types that implements the
 :java-docs:`Bson <apidocs/bson/org/bson/conversions/Bson.html>` interface,
 including:
 
@@ -58,12 +58,12 @@ These instructions show you how to add the BSON library as a dependency to
 your project. If you added the MongoDB Java driver as a dependency to your
 project, you can skip this step since the BSON library is already included
 as a required dependency of the driver. For instructions on how to add the
-MongoDB driver as a dependency to your project, see the
+MongoDB Java driver as a dependency to your project, see the
 :ref:`driver installation <add-mongodb-dependency>` section of our Quick Start
 guide.
 
 We recommend that you use the `Maven <https://maven.apache.org/>`__ or
-`Gradle <https://gradle.org/>`__ build automation tool to manage your project
+`Gradle <https://gradle.org/>`__ build automation tool to manage your project's
 dependencies. Select from the tabs below to see the dependency declaration
 for that tool:
 

source/fundamentals/data-formats/document-data-format-extended-json.txt

@@ -22,9 +22,9 @@ store data.
 
 This guide explains the following topics:
 
-- the different MongoDB Extended JSON formats
-- how to use the BSON library to convert between Extended JSON and Java objects
-- how to create a custom conversion of BSON types
+- The different MongoDB Extended JSON formats
+- How to use the BSON library to convert between Extended JSON and Java objects
+- How to create a custom conversion of BSON types
 
 For more information on the difference between these formats, see our
 `article on JSON and BSON <https://www.mongodb.com/json-and-bson>`__.
@@ -38,7 +38,7 @@ and meet specific use cases. The **extended** format, also known as the
 **canonical** format, features specific representations for every BSON type
 for bidirectional conversion without loss of information. The **Relaxed mode**
 format is more concise and closer to ordinary JSON, but does not represent
-all the type information such as specific byte size of number fields.
+all the type information such as the specific byte size of number fields.
 
 See the table below to see a description of each format:
 
@@ -60,15 +60,16 @@ See the table below to see a description of each format:
 
    * - **Shell**
      - | JSON representation that matches the syntax used in the MongoDB shell.
-       | This format prioritizes for compatibility with the MongoDB shell which often uses JavaScript functions to represent types.
+       | This format prioritizes compatibility with the MongoDB shell which often uses JavaScript functions to represent types.
+
 
 .. _extended_json_example_section:
 
 .. note::
 
-   The ``$uuid`` Extended JSON type is parsed from a String to a
-   ``BsonBinary`` object of binary subtype 4. For more information about
-   ``$uuid`` field parsing, see the
+   The driver parses the ``$uuid`` Extended JSON type from a string to a
+   ``BsonBinary`` object of binary subtype 4. For more information about ``$uuid`` field
+   parsing, see the
    :spec:`special rules for parsing $uuid fields </extended-json.rst#special-rules-for-parsing-uuid-fields>`
    section in the extended JSON specification.
 
@@ -130,7 +131,7 @@ Read Extended JSON
 Using the Document Classes
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-You can read an Extended JSON string into Java document objects by calling
+You can read an Extended JSON string into a Java document object by calling
 the ``parse()`` static method from either the ``Document`` or ``BsonDocument``
 class, depending on which object type you need. This method parses the Extended
 JSON string in any of the formats and returns an instance of that class
@@ -162,12 +163,12 @@ Using the BSON Library
 ~~~~~~~~~~~~~~~~~~~~~~
 
 You can also read an Extended JSON string into Java objects without using
-the MongoDB driver's document classes by using the ``JsonReader`` class.
+the MongoDB Java driver's document classes by using the ``JsonReader`` class.
 This class contains methods to sequentially parse the fields and values
 in any format of the Extended JSON string, and returns them as Java objects.
-MongoDB driver's document classes also use this class to parse Extended JSON.
+The driver's document classes also use this class to parse Extended JSON.
 
-The following code example shows how you can use ``JsonReader`` to convert
+The following code example shows how you can use the ``JsonReader`` class to convert
 an Extended JSON string into Java objects:
 
 .. code-block:: java
@@ -238,7 +239,7 @@ the BSON library with the ``JsonWriter`` class. To construct an instance
 of ``JsonWriter``, pass a subclass of a Java ``Writer`` to specify how
 you want to output the Extended JSON. You can optionally pass a ``JsonWriterSettings``
 instance to specify options such as the Extended JSON format. By default, the
-``JsonWriter`` uses the Relaxed mode format. MongoDB driver's
+``JsonWriter`` uses the Relaxed mode format. The MongoDB Java driver's
 document classes also use this class to convert BSON to Extended JSON.
 
 The following code example shows how you can use ``JsonWriter`` to create an

source/fundamentals/data-formats/document-data-format-pojo.txt

@@ -20,17 +20,17 @@ data representation.
 
 In the following sections we show:
 
-- a POJO example
-- how to configure the driver to serialize and deserialize the POJO
-- sample code to read and write documents to MongoDB using the POJO
+- A POJO example
+- How to configure the driver to serialize and deserialize POJOs
+- Sample code to read and write documents to MongoDB using POJOs
 
 .. _fundamentals-example-pojo:
 
 Example POJO
 ------------
 
 To follow the steps in this guide, you can create your own class or use the
-following sample POJO class which describes characteristics of a flower:
+following sample POJO class which describes some characteristics of a flower:
 
 .. code-block:: java
 
@@ -99,7 +99,7 @@ following sample POJO class which describes characteristics of a flower:
    }
 
 If you are creating your own POJO for storing and retrieving data in MongoDB,
-make sure to follow the following guidelines:
+make sure to follow these guidelines:
 
 - The POJO class should not implement interfaces or extend classes from a
   framework.
@@ -119,8 +119,8 @@ To set up the driver to store and retrieve POJOs, we need to specify:
 - The ``PojoCodecProvider``, a codec provider that includes
   :doc:`Codecs </fundamentals/data-formats/codecs>` that define how to
   encode/decode the data between the POJO and MongoDB document, and which
-  POJO classes or packages that the Codecs should apply to.
-- A ``CodecRegistry`` instance that contains the Codecs and other related information.
+  POJO classes or packages that the codecs should apply to.
+- A ``CodecRegistry`` instance that contains the codecs and other related information.
 - A ``MongoClient``, ``MongoDatabase``, or ``MongoCollection`` instance
   configured to use the ``CodecRegistry``.
 - A ``MongoCollection`` instance created with the POJO document class
@@ -192,7 +192,7 @@ Once you have configured the ``MongoCollection`` instance above, you can:
 - save an instance of the POJO to the collection
 - retrieve instances of the POJO from a query on the collection
 
-The code below shows you how you can insert an instance of ``Flower`` into
+The code below shows how you can insert an instance of ``Flower`` into
 the collection and then retrieve it as a ``List`` of your POJO class objects:
 
 .. code-block:: java
@@ -238,7 +238,7 @@ Summary
 In this guide, we explained how to convert data between BSON and POJO fields
 by performing the following:
 
-- Instantiate a ``PojoCodecProvider`` which contains Codecs which define how to
+- Instantiate a ``PojoCodecProvider`` which contains codecs which define how to
   encode/decode data between BSON and the POJO fields.
 - Specify the **automatic** conversion behavior for the ``PojoCodecProvider``
   to apply the ``Codecs`` to any class and its properties.