(DOCSP-19182) Replace "Link Only" TODOs + Remove "Remove TODO" TODOs (#186)

Author: biniona-mongodb

source/includes/steps-cdc-tutorial.yaml

@@ -26,8 +26,9 @@ content: |
   connector writes change event documents corresponding to the ``Source``
   collection in the ``CDCTutorial`` database to a Kafka topic. The configuration
   for the source connector is as follows:
-  <TODO: Link to Source - Fundamentals - Change Streams page>
-    
+
+  .. _cdc-tutorial-source-connector:
+
   .. code-block:: properties
      :copyable: false
 
@@ -105,6 +106,8 @@ content: |
   Your upper terminal window is now listening to the ``CDCTutorial.Source`` Kafka
   topic. Changes to your topic will print in this terminal window.
 
+  To learn more about ``kafkacat``, see the :github:`kcat repository <edenhill/kcat>` on GitHub.
+
 ---
 title: Configure Sink Connector
 ref: cdc-tutorial-configure-sink
@@ -174,6 +177,8 @@ content: |
 
      rs0 [primary] test> 
 
+  .. _cdc-tutorial-change-data-insert:
+
   Insert a document into the ``Source`` collection of the ``CDCTutorial`` database
   with the following commands:
 
@@ -250,17 +255,25 @@ content: |
 
      exit
 
-  Try and explore the CDC handler on your own. Here are some challenges to get
+  Explore the sample pipeline on your own. Here are some challenges to get
   you started:
 
-  - Add a second source connector that writes to the ``CDCTutorial.Source``
-    topic. Use a pipeline to have this connector only write insert events.
-  - Remove the ``change.data.capture.handler`` from your sink connector. What
-    do your documents look like?
-  - Use ``kafkacat`` to upload a message to the ``CDCTutorial.Source`` topic
-    that isn't a MongoDB Change Event document. What happens?
-
-  <TODO: Link to relevant docs sections from the explore list above >
+  - Add a new source connector that writes to the ``CDCTutorial.Source``
+    topic. Configure your new connector to write insert events. To
+    learn how to filter event types in your connector, see the
+    :ref:`<source-usage-example-custom-pipeline>` guide.
+  - Add a new source connector configured with the ``publish.full.document.only=true``
+    option that writes to the ``CDCTutorial.Source`` topic. Publish a document with
+    your new source connector. This produces an error in your sink connector and your
+    sink connector stops. Configure your sink connector to write errant messages
+    to a topic rather than stop. To learn how to write errant messages to a topic,
+    see :ref:`<kafka-sink-errors-dlq>`.
+  - Remove the ``change.data.capture.handler`` from your sink connector.
+    Add the :ref:`source connector from the tutorial <cdc-tutorial-source-connector>` to {+kc+}
+    if its not already added. Insert a document into MongoDB
+    :ref:`as done in the tutorial <cdc-tutorial-change-data-insert>`.
+    Look at the :ref:`change event document <source-connector-fundamentals-change-event>`
+    your sink connector inserts into MongoDB.
 
 ---
 title: Stop the Pipeline

source/introduction/connect.txt

@@ -1,3 +1,5 @@
+.. _kafka-intro-connect:
+
 ==================
 Connect to MongoDB
 ==================

source/introduction/converters.txt

@@ -22,8 +22,6 @@ Converters are programs that translate between bytes and
 Converters pass data between {+kc+} and Apache Kafka. The {+mkc+} passes data
 between MongoDB and {+kc+}. The following diagram shows these relationships:
 
-<TODO: Design Look At Diagram>
-
 .. figure:: /includes/figures/converters.png
    :alt: Diagram illustrating converters' role in Kafka Connect  
 
@@ -45,8 +43,6 @@ format, the {+mkc+} works with all available converters.
    For example, if your source connector writes to a topic using Protobuf, your
    sink connector must use Protobuf to read from the topic.
 
-   < TODO: Link "topic" to our glossary page entry on "topics" >
-
 To learn what converter to use, `see this page from Confluent <https://docs.confluent.io/platform/current/schema-registry/connect.html>`__.
 
 Converters with Schemas
@@ -55,16 +51,12 @@ Converters with Schemas
 If you use a schema-based converter such as the converter for Avro, Protobuf, or
 JSON Schema, you should define a schema in your {+mkc+} source connector. 
 
-To learn more, see our 
-:doc:`guide on applying a schema in a {+mkc+} source connector </source-connector/fundamentals>`.
-
-.. TODO: Link to correct page once available
+To learn how to specify a schema, see the 
+:ref:`<kafka-source-apply-schemas>` guide.
 
 Connector Configuration
 -----------------------
 
-<TODO: Move this content into a reference Section as per https://jira.mongodb.org/browse/DOCSP-18435>
-
 This section provides templates for properties files to configure the following
 converters in a {+mkc+} pipeline:
 

source/introduction/data-formats.txt

@@ -59,8 +59,9 @@ Raw JSON is a data format that consists of JSON objects written as strings. You
 
    "{\"company\":\"MongoDB\"}"
 
-You use Raw JSON when you specify a String Converter on a
-source or sink connector. <TODO: Link to Converters page when it is ready>
+You use Raw JSON when you specify a String converter on a
+source or sink connector. To view connector configurations that specify a 
+String converter, see the :ref:`Converters <string-converter-sample-properties>` guide.
 
 .. _kafka-df-bson:
 
@@ -115,7 +116,10 @@ with JSON Schema like this:
    }
 
 You use JSON Schema when you apply JSON Schema converters to your connectors.
-<TODO: Link to this section of converters page>  
+To view connector configurations that specify a 
+JSON Schema converter, see the :ref:`Converters <json-schema-converter-sample-properties>`
+guide.
+
 
 For more information, see the official 
 `JSON Schema website <https://json-schema.org/>`__.
@@ -200,8 +204,10 @@ like this:
 
    \x0eMongoDB
 
-You use Avro binary encoding when you specify an Avro Converter on a
-source or sink connector. <TODO: Link to Converters page when its ready>. 
+You use Avro binary encoding when you specify an Avro converter on a
+source or sink connector. To view connector configurations that specify an
+Avro converter, see the :ref:`Converters <avro-converter-sample-properties>`
+guide. 
 
 To learn more about Avro binary encoding, see
 `this section of the Avro specification <https://avro.apache.org/docs/current/spec.html#Data+Serialization+and+Deserialization>`__. 
@@ -217,5 +223,5 @@ You can represent the sample document as a byte array using any of the encodings
 mentioned above.
 
 You use byte arrays when your converters send data to or receive data
-from {+ak+}. For more information on converters, see our guide on converters.
-<TODO: link to converters page>
+from {+ak+}. For more information on converters, see the
+:ref:`<intro-converters>` guide.