(DOCSP-19377) Section Title Audit (#195)

Author: biniona-mongodb

source/introduction/connect.txt

@@ -48,8 +48,8 @@ To learn more about this configuration option, see the following resources:
 - :doc:`Source connector configuration options </source-connector/configuration-properties/mongodb-connection/>`
 - :doc:`Sink connector configuration options </sink-connector/configuration-properties/mongodb-connection/>`
 
-Connection URI Options
-----------------------
+How to Configure Your Connection
+--------------------------------
 
 The {+mkc+} uses the **MongoDB Java driver** to parse your connection URI.
 The MongoDB Java driver is an artifact that enables Java applications like {+kc+}

source/introduction/install.txt

@@ -49,7 +49,7 @@ connector on Confluent Platform:
          <https://docs.confluent.io/home/connect/community.html>`__.
 
       2. Use the connector GitHub URL and uber JAR locations in the
-         :ref:`installation reference table <kafka-connector-installation-reference>`
+         :ref:`reference table <kafka-connector-installation-reference>`
          when appropriate in the Confluent manual installation instructions.
 
 .. _kafka-connector-install-apache:
@@ -58,8 +58,8 @@ Install the Connector on Apache Kafka
 -------------------------------------
 
 1. Locate and download the uber JAR to get all the dependencies required
-   for the connector. Refer to the
-   :ref:`installation reference table <kafka-connector-installation-reference>`
+   for the connector. Check the
+   :ref:`reference table <kafka-connector-installation-reference>`
    to find the uber JAR.
 
    .. note::
@@ -81,13 +81,13 @@ Install the Connector on Apache Kafka
    If you intend to run the connector as distributed worker processes, you
    must repeat this process for each server or virtual machine.
 
-.. _kafka-connector-installation-reference:
-
-Installation Reference Table
-----------------------------
+Download a Connector JAR File
+-----------------------------
 
 You can download the {+mkc+} source and JAR files from the following locations:
 
+.. _kafka-connector-installation-reference:
+
 .. list-table::
    :widths: 55 45
    :stub-columns: 1

source/quick-start.txt

@@ -34,8 +34,8 @@ Read the following sections to set up your sandbox and sample data pipeline.
    following the instructions in the :ref:`<kafka-quickstart-remove-the-sandbox>`
    section.
 
-Requirements
-------------
+Install the Required Packages
+-----------------------------
 
 .. include:: /includes/tutorials/pipeline-requirements.rst
 

source/sink-connector/configuration-properties/error-handling.txt

@@ -142,3 +142,4 @@ the dead letter queue messages should include context headers.
    errors.deadletterqueue.topic.name=example.deadletterqueue
    errors.deadletterqueue.context.headers.enable=true
 
+To learn more about dead letter queues, see :ref:`<kafka-sink-errors-dlq>`.

source/sink-connector/configuration-properties/time-series.txt

@@ -76,9 +76,9 @@ Settings
          a number. If the value is a string, the connector uses the
          setting in the following configuration to parse the date:
 
-        .. code-block:: none
+       .. code-block:: none
 
-           timeseries.timefield.auto.convert.date.format
+          timeseries.timefield.auto.convert.date.format
 
        | If the connector fails to convert the value, it sends the
          original value to the time series collection.

source/sink-connector/fundamentals/error-handling-strategies.txt

@@ -38,14 +38,14 @@ Handle Errors
 When your connector encounters an error, it needs to handle it in some way.
 Your sink connector can do the following in response to an error:
 
-- :ref:`Stop <kafka-sink-errors-stop>` *default*
-- :ref:`Tolerate Errors <kafka-sink-tolerate-errors>`
-- :ref:`Write Errant Messages to a Topic (Dead Letter Queue) <kafka-sink-errors-dlq>`
+- :ref:`<kafka-sink-errors-stop>` *default*
+- :ref:`<kafka-sink-tolerate-errors>`
+- :ref:`<kafka-sink-errors-dlq>`
 
 .. _kafka-sink-errors-stop:
 
-Stop
-~~~~
+Stop For All Errors
+~~~~~~~~~~~~~~~~~~~
 
 By default, your sink connector terminates and stops processing messages
 when it encounters an error. This is a good option for you if any error in
@@ -68,8 +68,8 @@ adding the following to your connector configuration:
 
 .. _kafka-sink-tolerate-errors:
 
-Tolerate Errors
-~~~~~~~~~~~~~~~
+Tolerate All Errors
+~~~~~~~~~~~~~~~~~~~
 
 You can configure your sink connector to tolerate all errors and never stop
 processing messages. This is a good option for getting your sink connector up and
@@ -85,10 +85,10 @@ option:
 
 .. _kafka-sink-errors-dlq:
 
-Dead Letter Queue
-~~~~~~~~~~~~~~~~~
+Write Errors and Errant Messages to a Topic
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-You can configure your sink connector to write errant messages to a 
+You can configure your sink connector to write errors and errant messages to a 
 topic, called a **dead letter queue**, for you to inspect or process further.
 A dead letter queue is a location in message queueing
 systems such as {+ak+} where the system routes errant messages instead of
@@ -131,6 +131,8 @@ errant message, use the following option:
 For more information, see Confluent's guide on 
 `Dead Letter Queues <https://docs.confluent.io/cloud/current/connectors/dead-letter-queue.html#dead-letter-queue>`__.
 
+To view another dead letter queue configuration example, see :ref:`<sink-dead-letter-queue-configuration-example>`.
+
 .. _kafka-sink-log-errors:
 
 Log Errors
@@ -172,8 +174,8 @@ For more information, see Confluent's guide on
 
 .. _kakfa-sink-connector-level:
 
-Connector Level Options
------------------------
+Handle Errors at the Connector Level
+------------------------------------
 
 The {+mkc+} provides options that allow you to configure error
 handling at the connector level. The options are as follows:

source/sink-connector/fundamentals/post-processors.txt

@@ -846,8 +846,8 @@ it outputs the following:
 
 .. _sink-post-processors-custom:
 
-Create A Custom Post Processor
-------------------------------
+How to Create a Custom Post Processor
+-------------------------------------
 
 If the built-in post processors do not cover your use case, you can create
 a custom post processor class using the following steps:

source/sink-connector/fundamentals/write-strategies.txt

@@ -285,8 +285,8 @@ your collection.
 
 .. _kafka-sink-write-model-create-custom-strategy:
 
-Create A Custom Write Model Strategy
-------------------------------------
+Custom Write Model Strategies
+-----------------------------
 
 If none of the pre-built write model strategies fit your use case, you can create
 your own.

source/source-connector/usage-examples/copy-existing-data.txt

@@ -96,8 +96,8 @@ To learn more about aggregation pipelines, see the following resources:
 - :manual:`Aggregation </aggregation>` in the MongoDB manual.
 
 
-Copy Data Configuration
-~~~~~~~~~~~~~~~~~~~~~~~
+Specify the Configuration
+~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Your source connector configuration to copy the ``customers`` collection should
 look like this:

source/source-connector/usage-examples/schema.txt

@@ -129,8 +129,8 @@ For more information on the ``fullDocument`` field, see the
 
 .. _usage-example-schema-config:
 
-Custom Schema Configuration
-~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Specify the Configuration
+~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Your custom schema connector configuration should resemble the following: