030121 Fix RST build errors (#86)

* fix line blocks and changelog link

Author: Chris Cho

source/index.txt

@@ -52,6 +52,6 @@ This guide is divided into the following topics:
 - :doc:`Kafka Docker Example </kafka-docker-example>`
 - :doc:`Migrate from Kafka Connect </kafka-connect-migration>`
 - :doc:`Compatibility </kafka-compatibility>`
-- :doc:`Changelog <https://github.com/mongodb/mongo-kafka/blob/master/CHANGELOG.md>`
+- `Changelog <https://github.com/mongodb/mongo-kafka/blob/master/CHANGELOG.md>`__
 - :doc:`Issues and Help </issues-and-help>`   
 

source/kafka-sink-properties.txt

@@ -42,10 +42,7 @@ data to sink to MongoDB. For an example configuration file, see
    * - topics.regex
      - string
      - | A regular expression that matches the Kafka topics that the sink connector should watch.
-
-       The following regex matches topics such as
-       "activity.landing.clicks" and "activity.support.clicks",
-       but not "activity.landing.views" or "activity.clicks":
+       | The following regex matches topics such as "activity.landing.clicks" and "activity.support.clicks", but not "activity.landing.views" or "activity.clicks":
 
        .. code-block:: none
 
@@ -58,13 +55,12 @@ data to sink to MongoDB. For an example configuration file, see
    * - connection.uri
      - string
      - | A :manual:`MongoDB connection URI string </reference/connection-string/#standard-connection-string-format>`.
-
+       
        .. code-block:: none
 
           mongodb://username:password@localhost/
 
-       | For additional information, see the
-       | :doc:`Connect your Kafka Connector to MongoDB section </kafka-connection-mongodb>`.
+       | For additional information, see the :doc:`Connect your Kafka Connector to MongoDB section </kafka-connection-mongodb>`.
 
        .. include:: /includes/externalize-secrets.rst
 
@@ -87,18 +83,14 @@ data to sink to MongoDB. For an example configuration file, see
 
    * - namespace.mapper
      - string
-     - | The class name of the class that specifies which database or
-         collection in which to sink the data. The
-         ``DefaultNamespaceMapper`` uses the ``database`` and ``collection``
-         settings.
+     - | The class name of the class that specifies which database or collection in which to sink the data. The ``DefaultNamespaceMapper`` uses the ``database`` and ``collection`` settings.
 
-         .. seealso::
+       .. seealso::
 
-            - :ref:`FieldPathNamespaceMapper settings <fieldpathnamespacemapper-settings>`
+          - :ref:`FieldPathNamespaceMapper settings <fieldpathnamespacemapper-settings>`
 
        | **Default**: ``com.mongodb.kafka.connect.sink.namespace.mapping.DefaultNamespaceMapper``
-       | **Accepted Values**: A fully qualified Java class name of a class
-         that implements the ``NamespaceMapper`` interface.
+       | **Accepted Values**: A fully qualified Java class name of a class that implements the ``NamespaceMapper`` interface.
 
    * - document.id.strategy
      - string
@@ -229,9 +221,7 @@ data to sink to MongoDB. For an example configuration file, see
 
    * - writemodel.strategy
      - string
-     - | The class that specifies the ``WriteModel`` to use for :manual:`Bulk
-         Writes </core/bulk-write-operations/index.html>`. See :ref:`Custom
-         Write Model Strategy <custom-write-model-strategy>` for more information.
+     - | The class that specifies the ``WriteModel`` to use for :manual:`Bulk Writes </core/bulk-write-operations/index.html>`. See :ref:`Custom Write Model Strategy <custom-write-model-strategy>` for more information.
        |
        | **Default**: ``com.mongodb.kafka.connect.sink.writemodel.strategy.ReplaceOneDefaultStrategy``
        | **Accepted Values**: A fully qualified Java class name of a class that implements ``WriteModelStrategy``
@@ -252,7 +242,7 @@ data to sink to MongoDB. For an example configuration file, see
      - int
      - | The maximum number of tasks that should be created for this connector. The connector may create fewer tasks if it cannot handle the specified level of parallelism.
 
-       .. important:: Messages May Be Processed Out of Order For Values Greater Than 1
+       .. important:: Messages May Be Processed Out of Order for Values Greater Than 1
 
           If you specify a value greater than ``1``, the connector
           enables parallel processing of the tasks. If your topic has
@@ -264,22 +254,14 @@ data to sink to MongoDB. For an example configuration file, see
 
    * - heartbeat.interval.ms
      - int
-     - | The length of time in milliseconds between sending heartbeat
-         messages. Heartbeat messages contain the post batch resume token
-         and are sent when no source records have been published in the
-         specified interval. This improves the resumability of the
-         connector for low volume namespaces. Use ``0`` to disable.
+     - | The length of time in milliseconds between sending heartbeat messages. Heartbeat messages contain the post batch resume token and are sent when no source records have been published in the specified interval. This improves the resumability of the connector for low volume namespaces. Use ``0`` to disable.
        |
        | **Default**: ``0``
        | **Accepted Values**: An integer
 
    * - heartbeat.topic.name
      - string
-     - | The name of the topic to publish heartbeat messages to. To enable
-         the heartbeat feature, you must provide a positive value in the
-         ``heartbeat.interval.ms`` setting. The user must consume
-         messages on this topic to track the latest offset (post batch
-         resume token).
+     - | The name of the topic to publish heartbeat messages to. To enable the heartbeat feature, you must provide a positive value in the ``heartbeat.interval.ms`` setting. The user must consume messages on this topic to track the latest offset (post batch resume token).
        |
        | **Default**: ``__mongodb_heartbeats``
        | **Accepted Values**: A valid Kafka topic name
@@ -360,33 +342,25 @@ You can use the following settings to customize the behavior of the
 
    * - namespace.mapper.key.database.field
      - string
-     - | The name of the key document field that specifies the name of the
-         database to write to.
+     - | The name of the key document field that specifies the name of the database to write to.
 
    * - namespace.mapper.key.collection.field
      - string
-     - | The name of the key document field that specifies the name of the
-         collection to write to.
+     - | The name of the key document field that specifies the name of the collection to write to.
 
    * - namespace.mapper.value.database.field
      - string
-     - | The name of the value document field that specifies the name of
-         the database to write to.
+     - | The name of the value document field that specifies the name of the database to write to.
 
    * - namespace.mapper.value.collection.field
      - string
-     - | The name of the value document field that specifies the name of
-         the collection to write to.
+     - | The name of the value document field that specifies the name of the collection to write to.
 
    * - namespace.mapper.error.if.invalid
      - boolean
-     - | Whether to throw an exception if the document is missing the
-         mapped field or if it contains an invalid BSON type.
-       | When set to ``true``, the connector does not process the record
-         and may halt or skip processing depending on the related settings.
-       | When set to ``false`` and a document is missing the mapped field
-         or if it contains an invalid BSON type, the connector defaults to
-         writing to the specified ``database`` and ``collection`` settings.
+     - | Whether to throw an exception if the document is missing the mapped field or if it contains an invalid BSON type.
+       | When set to ``true``, the connector does not process the record and may halt or skip processing depending on the related settings.
+       | When set to ``false`` and a document is missing the mapped field or if it contains an invalid BSON type, the connector defaults to writing to the specified ``database`` and ``collection`` settings.
        |
        | **Default**: ``false``
        | **Accepted Values**: ``true`` or ``false``
@@ -423,18 +397,13 @@ letter queue.
    :stub-columns: 1
    :widths: 2 1 4
 
-
    * - Name
      - Type
      - Description
 
    * - errors.tolerance
      - string
-     - | Whether to continue processing messages if an error is encountered.
-         When set to ``none``, the connector reports an error and blocks
-         further processing of the rest of the records when it encounters
-         an error. When set to ``all``, the connector silently ignores any bad
-         messages.
+     - | Whether to continue processing messages if an error is encountered. When set to ``none``, the connector reports an error and blocks further processing of the rest of the records when it encounters an error. When set to ``all``, the connector silently ignores any bad messages.
        |
        | **Default:** "none"
        | **Accepted Values**: "none" or "all"