DOCSP-30350 Adding descriptions and editing

Author: mballard-mdb

source/crud/bulk.txt

@@ -623,6 +623,8 @@ Even though the write operation inserting a document with a duplicate key result
 in an error, the other operations are executed because the write operation is
 unordered.
 
+.. _java-bulk-insert-troubleshooting:
+
 Troubleshooting
 ---------------
 
@@ -631,7 +633,7 @@ Troubleshooting
 Bulk Write Exception
 ~~~~~~~~~~~~~~~~~~~~
 
-The driver creates write exceptions when a ``WriteError`` object is created. If an
+The driver creates a write exception when a ``WriteError`` object is created. If an
 error is detected during a bulk write operation, a `MongoBulkWriteException
 <{+core-api+}/MongoBulkWriteException.html>`__ is thrown.
 
@@ -643,7 +645,7 @@ Example
 '''''''
 
 For example, the driver raises a ``MongoBulkWriteException`` if your bulk insert
-contains two documents into a collection that violate the collection's schema
+contains two documents that violate the collection's schema
 validation rules. Suppose the collection has a rule where the value of the
 ``quantity`` field must be an ``int`` type. If your bulk insert contains a
 document with a ``quantity`` of ``"three"`` and another with a ``quantity`` of
@@ -674,11 +676,15 @@ document with a ``quantity`` of ``"three"`` and another with a ``quantity`` of
    com.mongodb.internal.connection.ProtocolHelper.getBulkWriteException(ProtocolHelper.java:254)
    ... 19 more    
 
-This exception message contains a list of the two ``WriteError`` objects. The
-description in the ``MongoBulkWriteException`` object is vague as
-documents associated with the same bulk operation could produce different error
-types. Refer to the individual ``WriteError`` objects' ``message`` fields to
-determine the cause of each error.
+
+In the preceding error message, the ``MongoBulkWriteException`` object provides
+a vague description of the error, as documents associated with the same bulk
+operation could produce different error types. Instead, refer to the
+``WriteError`` objects' ``message`` fields to determine the cause of each error.
+Refer to the ``WriteError`` objects' ``details`` field for more specific
+information, such as the schema rules and the offending documents. To address
+this error, you must either revise the document to adhere to the schema
+validation rules or bypass validation.
 
 Additional Information
 ----------------------

source/crud/insert.txt

@@ -189,6 +189,8 @@ operation and an insert many operation:
       insertOne() document id: BsonObjectId{value=...}
       insertMany() document ids: {0=BsonObjectId{value=...}, 1=BsonObjectId{value=...}}
 
+.. _java-insert-troubleshooting:
+
 Troubleshooting
 ---------------
 
@@ -197,7 +199,7 @@ Troubleshooting
 Write Exception
 ~~~~~~~~~~~~~~~
 
-The driver creates write exceptions when a ``WriteError`` object is created. The
+The driver creates a write exception when a ``WriteError`` object is created. The
 driver raises a `MongoWriteException <{+core-api+}/MongoWriteException.html>`__
 for any write errors that occur when performing single write operations.
 

source/includes/crud/write-error.rst

@@ -1,13 +1,13 @@
 .. _java_write_error:
 
-This section describes write exceptions you might encounter when
-using the {+driver-long+} to perform MongoDB write operations. Once you
-understand the types of write exceptions that the driver raises, you can take
-appropriate actions to either handle them or correct the error-causing code.
+This section explains write exceptions you might encounter when using the
+{+driver-long+} to perform MongoDB write operations. Once you learn how to
+understand the write exceptions that the driver raises, you can take appropriate
+actions to either handle them or correct the error-causing code.
 
 .. note::
 
-   This page addresses only write exception handling. If you encounter
+   This section addresses only write exception handling. If you encounter
    any other issues with MongoDB or the driver, visit the following
    resources: