Docsp 16491 typos fundamentals crud (#112)

Author: biniona-mongodb

source/fundamentals/crud.txt

@@ -10,7 +10,6 @@ CRUD Operations
    /fundamentals/crud/read-operations
    /fundamentals/crud/write-operations
    /fundamentals/crud/query-document
-   /fundamentals/crud/bulk
    /fundamentals/crud/compound-operations
 
 CRUD (Create, Read, Update, Delete) operations enable you to work with
@@ -24,6 +23,3 @@ data stored in MongoDB.
 Some operations combine aspects of read and write operations. See our
 guide on :doc:`compound operations </fundamentals/crud/compound-operations>`
 to learn more about these hybrid methods.
-
-You can also perform multiple CRUD operations using bulk operations. See
-our guide on :doc:`bulk operations </fundamentals/crud/bulk>` to learn more.

source/fundamentals/crud/query-document.txt

@@ -113,7 +113,7 @@ Array operators query data based on the value or quantity of elements in
 an array field. 
 
 The following example uses the ``Filters.size()`` method to match
-documents where the size of ``vendor`` list is ``3`` in the
+documents where the size of the ``vendor`` list is ``3`` in the
 ``paint_purchases`` collection: 
 
 .. literalinclude:: /includes/fundamentals/code-snippets/Query.java

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

@@ -18,7 +18,7 @@ MongoDB Java driver.
 
 Read operations that return multiple documents do not immediately return
 all values matching the query. Because a query can potentially match
-large number of documents, we need to be able to access or store the
+a large number of documents, we need to be able to access or store the
 matched documents. 
 
 This page uses an initiating method, ``find()`` to show how to access
@@ -27,7 +27,7 @@ data from a :java-docs:`FindIterable
 
 .. note::
 
-   The ways to access and store data mentioned below applies equally to
+   The ways to access and store data mentioned below apply to
    other iterables such as an :java-docs:`AggregateIterable
    <apidocs/mongodb-driver-sync/com/mongodb/client/AggregateIterable.html>`.
 
@@ -37,7 +37,7 @@ instance of a ``FindIterable``.
 
 A ``FindIterable`` consists of documents matched by your search criteria
 and allows you to further specify which documents to see by setting
-parameters though methods. 
+parameters through methods. 
 
 Terminal Methods
 ----------------
@@ -152,8 +152,8 @@ iterate through results in a functional style:
 
 .. warning::
 
-   Initiating methods implement the Iterable interface which allows you
-   to iterate using iterator methods. Sometimes, we use an enhanced
+   Initiating methods return objects that implement the ``Iterable`` interface which allows you
+   to iterate through them using iterator methods. Sometimes, we use an enhanced
    for-each loop to iterate through results: 
 
    .. code-block:: java

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

@@ -46,7 +46,7 @@ Find Operation
 
 Use the find operation to retrieve a subset of your existing data in
 MongoDB. You can specify what data to return including which documents
-to retrieve, in what order to retrieve them and how many to retrieve. 
+to retrieve, in what order to retrieve them, and how many to retrieve. 
 
 To perform a find operation, call the ``find()`` method on an instance
 of a ``MongoCollection``. This method searches a collection for documents that
@@ -68,7 +68,7 @@ To address this scenario, the owner finds orders to match the criteria:
    :start-after: begin findExample
    :end-before: end findExample
 
-For more information how to build filters, see our :doc:`Filters Builders
+For more information on how to build filters, see our :doc:`Filters Builders
 </fundamentals/builders/filters>` guide.
 
 The following shows the output of the query specified above:
@@ -97,7 +97,7 @@ To perform an aggregate operation, call the ``aggregate()`` method on an
 instance of a ``MongoCollection``. This method accepts aggregation
 expressions to run in sequence. To perform aggregations, you can
 define aggregation stages that specify how to match documents, rename
-fields and group values. For more information, see our
+fields, and group values. For more information, see our
 :doc:`Aggregation </fundamentals/aggregation>` guide.
 
 Example
@@ -144,14 +144,14 @@ streams, see the MongoDB server manual page on :manual:`Change Streams
 </changeStreams>`. 
 
 To open a change stream, call the ``watch()`` method on an instance of a
-``MongoCollection``, ``MongoDatabase`` or ``MongoClient``. 
+``MongoCollection``, ``MongoDatabase``, or ``MongoClient``. 
 You can pass an aggregation pipeline to this method to notify you as
 soon as a change occurs.
 
 .. note::
 
    Change streams don't support standalone MongoDB instances because
-   they don't have an oplog. 
+   standalone MongoDB instances don't have an oplog. 
 
 The instance you call the ``watch()`` method on determines the scope of
 events which the change stream listens for. If you call ``watch()`` on a
@@ -165,7 +165,7 @@ Example
 ~~~~~~~
 
 The owner would like to receive notifications for when customers submit new
-orders or update their orders from thier :ref:`paint_order collection <retrieve-paint-order-collection>`.
+orders or update their orders in the :ref:`paint_order collection <retrieve-paint-order-collection>`.
 
 To address this scenario, the owner:
 

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

@@ -54,7 +54,7 @@ within an aggregation pipeline. To sort your query results, use the
 aggregation pipeline, use the ``Aggregates.sort()`` static factory method. Both
 of these methods receive objects that implement the ``Bson`` interface as
 arguments. For more information, see our API Documentation for the 
-:java-docs:`Bson interface <apidocs/bson/org/bson/conversions/Bson.html>`
+:java-docs:`Bson interface <apidocs/bson/org/bson/conversions/Bson.html>`.
 
 You can use the ``sort()`` method of a ``FindIterable`` instance as follows:
 
@@ -133,7 +133,7 @@ To specify an ascending sort, use the ``Sorts.ascending()`` static
 factory method. Pass the ``Sorts.ascending()`` method
 the name of the field you need to sort in ascending order.
 
-You can use pass the ``sort()`` method the output of the ``Sorts.ascending()``
+You can pass the ``sort()`` method the output of the ``Sorts.ascending()``
 method to specify an ascending sort on a field as follows:
 
 .. code-block:: java

source/fundamentals/crud/write-operations.txt

@@ -9,6 +9,7 @@ Write Operations
 - :doc:`/fundamentals/crud/write-operations/change-a-document`
 - :doc:`/fundamentals/crud/write-operations/embedded-arrays`
 - :doc:`/fundamentals/crud/write-operations/upsert`
+- :doc:`/fundamentals/crud/write-operations/bulk`
 
 .. toctree::
    :caption: Write Operations
@@ -18,3 +19,4 @@ Write Operations
    /fundamentals/crud/write-operations/change-a-document
    /fundamentals/crud/write-operations/embedded-arrays
    /fundamentals/crud/write-operations/upsert
+   /fundamentals/crud/write-operations/bulk

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

@@ -16,10 +16,10 @@ Overview
 In this guide, you can learn how to use bulk operations in the
 MongoDB Java Driver. 
 
-To perform a create, replace, update or delete (CRUD) operation, you
-use their corresponding method. For example, to insert one document,
+To perform a create, replace, update, or delete operation,
+use its corresponding method. For example, to insert one document,
 update multiple documents, and delete one document in your collection,
-you use the ``insertOne()``, ``updateMany()`` and ``deleteOne()`` methods. 
+use the ``insertOne()``, ``updateMany()`` and ``deleteOne()`` methods. 
 
 The ``MongoClient`` performs these operations by making a call for each
 operation to the database. You can reduce the number of calls to the
@@ -28,10 +28,10 @@ database to one by using bulk operations.
 Performing Bulk Operations
 --------------------------
 
-Bulk operations consist of a large number of CRUD operations. To perform
-the bulk operation, pass a ``List`` of ``WriteModel`` documents  to the
+Bulk operations consist of a large number of write operations. To perform
+a bulk operation, pass a ``List`` of ``WriteModel`` documents  to the
 ``bulkWrite()`` method. A ``WriteModel`` is a model that represents any
-of the CRUD operations. 
+of the write operations. 
 
 The following sections show how to create and use each ``WriteModel``
 document. The examples in each section contain the following documents
@@ -60,7 +60,7 @@ Example
 ```````
 
 The following example creates an ``InsertOneModel`` for two documents
-where the ``_id`` is "3" and "4": 
+where the ``_id`` values are "3" and "4": 
 
 .. literalinclude:: /includes/fundamentals/code-snippets/BulkWrite.java
    :language: java
@@ -87,7 +87,7 @@ where the ``_id`` is "3" and "4":
 
    .. code-block:: shell
 
-      A MongoBulkWriteException occured with the following message:  
+      A MongoBulkWriteException occurred with the following message:  
       Bulk write operation error on server sample-shard-00-02.pw0q4.mongodb.net:27017. 
       Write errors: [BulkWriteError{index=0, code=11000, message='E11000 duplicate key 
       error collection: crudOps.bulkWrite index: _id_ dup key: { _id: 1 }', details={}}].
@@ -104,7 +104,7 @@ Replace Operation
 ~~~~~~~~~~~~~~~~~
 
 To perform a replace operation, create a ``ReplaceOneModel`` specifying
-a query filter for document you want to replace with the replacement
+a query filter for the document you want to replace with the replacement
 document. 
 
 .. note::
@@ -185,7 +185,7 @@ match your query filter.
 .. note::
 
    When performing a ``bulkWrite()``, the ``DeleteOneModel`` and
-   ``DeleteOneModel`` do not delete any documents if there are no matches
+   ``DeleteManyModel`` do not delete any documents if there are no matches
    to your query filter. 
 
 Example
@@ -251,8 +251,8 @@ Unordered Execution
 
 You can also execute bulk operations in any order by specifying "false"
 to the ``order()`` method on ``BulkWriteOptions``. This means that
-all the bulk operations execute regardless if an error occurs and
-reports the errors at the end, if any. 
+all the write operations execute regardless of errors and if any errors occur
+the bulk operation reports them at the end. 
 
 Adding to the example above, including the following specifies the bulk
 operations to execute in any order: 
@@ -268,7 +268,7 @@ operations to execute in any order:
    Unordered bulk operations do not guarantee order of execution. The
    order may differ from the way you list them to optimize the runtime.
 
-   In the exampel above, if the ``bulkWrite()`` method decided to
+   In the example above, if the ``bulkWrite()`` method decided to
    perform the insert operation after the update operation, nothing
    changes with the update operation because the document does not exist
    at that point in time. Your collection then contains the following

source/fundamentals/crud/write-operations/change-a-document.txt

@@ -40,7 +40,7 @@ current inventory:
 Update
 ------
 
-Update operations can change the fields and values. They apply changes
+Update operations can change fields and values. They apply changes
 specified in an update document to one or more documents that match your
 query filter. 
 
@@ -61,6 +61,9 @@ You can call the ``updateOne()`` and ``updateMany()`` methods on a
 Update Operation Parameters
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
+The ``updateOne()`` and ``updateMany()`` methods both have the following
+parameters:
+
 - ``query`` specifies a query filter with the criteria to match documents to update in your collection
 - ``updateDocument`` specifies the fields and values to change in the matching document or documents. For this example, we use the :doc:`Updates builder </fundamentals/builders/updates>` to create the update document.
 
@@ -146,6 +149,8 @@ instance as follows:
 Replace Operation Parameters
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
+The ``replaceOne()`` method has the following parameters:
+
 - ``query`` specifies a query filter with the criteria to match a document to replace in your collection
 - ``replacementDocument`` specifies fields and values of a new ``Document`` object to replace in the matched document 
 
@@ -158,8 +163,8 @@ thought was 20 cans of pink paint is actually 25 cans of orange paint.
 To update the inventory, call the ``replaceOne()`` method specifying the
 following:
 
-- A query filter that matches the ``color`` is "pink" 
-- A replacement document that contains: ``color`` is "orange" and ``qty`` is "25"
+- A query filter that matches documents where the ``color`` is "pink" 
+- A replacement document where the ``color`` is "orange" and the ``qty`` is "25"
 
 .. literalinclude:: /includes/fundamentals/code-snippets/Update.java
    :language: java

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

@@ -133,7 +133,7 @@ deleted document:
 .. note::
 
     If there are no matches to your query filter, no document gets
-    deleted and the method returns null. 
+    deleted and the method returns ``null``. 
 
 The following shows the documents remaining in the ``paint_inventory``
 collection:

source/fundamentals/crud/write-operations/embedded-arrays.txt

@@ -182,5 +182,5 @@ The example above updates the original document to the following state:
 For more information about the methods and operators mentioned in this section,
 see the following resources: 
 
-- :manual:`Positional $[\<identifier\>] Operator </reference/operator/update/positional-filtered/>` Server Manual Entry
+- :manual:`Filtered Positional $[\<identifier\>] Operator </reference/operator/update/positional-filtered/>` Server Manual Entry
 - :java-docs:`inc() <apidocs/mongodb-driver-core/com/mongodb/client/model/Updates.html#inc(java.lang.String,java.lang.Number)>` API Documentation