[pulsar-site] branch main updated: Docs sync done from apache/pulsar (#2d205c9)

[ur...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

urfree pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git


The following commit(s) were added to refs/heads/main by this push:
     new 4f700d3672a Docs sync done from apache/pulsar (#2d205c9)
4f700d3672a is described below

commit 4f700d3672afd56b79732715a891be5150f71af9
Author: github-actions[bot] <41...@users.noreply.github.com>
AuthorDate: Wed Dec 7 07:08:45 2022 +0000

    Docs sync done from apache/pulsar (#2d205c9)
---
 site2/website-next/docs/io-debezium-source.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/site2/website-next/docs/io-debezium-source.md b/site2/website-next/docs/io-debezium-source.md
index 119a0929e2a..0095f006e2f 100644
--- a/site2/website-next/docs/io-debezium-source.md
+++ b/site2/website-next/docs/io-debezium-source.md
@@ -185,7 +185,7 @@ This example shows how to change the data of a MySQL table using the Pulsar Debe
        - One topic (`offset.storage.topic`) for storing the offset metadata messages. The connector saves the last successfully-committed offsets on this topic.
        - One per-table topic. The connector writes change events for all operations that occur in a table to a single Pulsar topic that is specific to that table.
 
-     If the automatic topic creation is disabled on your broker, you need to manually create the above 4 types of topics and the destination topic.
+     If the automatic topic creation is disabled on your broker, you need to manually create the above 4 types of topics.
 
      :::
 
@@ -327,7 +327,7 @@ This example shows how to change the data of a PostgreSQL table using the Pulsar
        - One topic (`offset.storage.topic`) for storing the offset metadata messages. The connector saves the last successfully-committed offsets on this topic.
        - One per-table topic. The connector writes change events for all operations that occur in a table to a single Pulsar topic that is specific to that table.
 
-     If the automatic topic creation is disabled on your broker, you need to manually create the above 4 types of topics and the destination topic.
+     If the automatic topic creation is disabled on your broker, you need to manually create the above 4 types of topics.
 
      :::
 
@@ -487,7 +487,7 @@ This example shows how to change the data of a MongoDB table using the Pulsar De
        - One topic (`offset.storage.topic`) for storing the offset metadata messages. The connector saves the last successfully-committed offsets on this topic.
        - One per-table topic. The connector writes change events for all operations that occur in a table to a single Pulsar topic that is specific to that table.
 
-     If the automatic topic creation is disabled on your broker, you need to manually create the above 4 types of topics and the destination topic.
+     If the automatic topic creation is disabled on your broker, you need to manually create the above 4 types of topics.
 
      :::