Skip to content

Commit dd813b6

Browse files
Chris Choschmalliso
authored andcommitted
DOCS-13696: fix aggregation pipeline manual link (#20)
* DOCS-13696: fix aggregation pipeline manual link
1 parent 8098ebc commit dd813b6

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

source/kafka-configure-ssl.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ Key Store
4848
If your SSL/TLS configuration requires a client certificate to connect,
4949
generate a secure private key and provide the client certificate bundled
5050
with the intermediate authority certificate. You can use ``openssl`` to
51-
generate a :wikipedia:`pkcs12 </PKCS_12>` file to store this information
51+
generate a :wikipedia:`pkcs12 <PKCS_12>` file to store this information
5252
in your key store using the following command:
5353

5454
.. code-block:: none

source/kafka-connect-migration.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,8 +29,8 @@ Update Configuration Settings
2929

3030
- Replace any keys that were used to specify per-topic and collection
3131
overrides that contain the ``mongodb.collection`` prefix with the
32-
equivalent key in `Topic-Specific Configuration Settings
33-
<https://github.com/mongodb/mongo-kafka/blob/master/docs/sink.md#topic-specific-configuration-settings>`_.
32+
equivalent key in :ref:`Topic-Specific Configuration Settings
33+
<topic-specific-configuration>`.
3434

3535
.. _custom-class-changes:
3636

source/kafka-source.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -244,7 +244,7 @@ Custom Pipeline Example
244244
-----------------------
245245

246246
You can use the ``pipeline`` configuration setting to define a custom
247-
:manual:`aggregation pipeline <reference/operator/aggregation-pipeline/>`
247+
:manual:`aggregation pipeline </reference/operator/aggregation-pipeline/>`
248248
to filter or modify the change events output. In this example, we set the
249249
``pipeline`` configuration to observe only insert change events:
250250

0 commit comments

Comments
 (0)