Merge pull request #3577 from amitkma/main

Fix typo in topics2TableMap to topic2TableMap in Kafka connect guide

Author: Blargian

docs/integrations/data-ingestion/kafka/kafka-clickhouse-connect-sink.md

@@ -348,7 +348,7 @@ or in the [Kafka documentation](https://kafka.apache.org/documentation/#consumer
 
 #### Multiple high throughput topics {#multiple-high-throughput-topics}
 
-If your connector is configured to subscribe to multiple topics, you're using `topics2TableMap` to map topics to tables, and you're experiencing a bottleneck at insertion resulting in consumer lag, consider creating one connector per topic instead. The main reason why this happens is that currently batches are inserted into every table [serially](https://github.com/ClickHouse/clickhouse-kafka-connect/blob/578ac07e8be1a920aaa3b26e49183595c3edd04b/src/main/java/com/clickhouse/kafka/connect/sink/ProxySinkTask.java#L95-L100).
+If your connector is configured to subscribe to multiple topics, you're using `topic2TableMap` to map topics to tables, and you're experiencing a bottleneck at insertion resulting in consumer lag, consider creating one connector per topic instead. The main reason why this happens is that currently batches are inserted into every table [serially](https://github.com/ClickHouse/clickhouse-kafka-connect/blob/578ac07e8be1a920aaa3b26e49183595c3edd04b/src/main/java/com/clickhouse/kafka/connect/sink/ProxySinkTask.java#L95-L100).
 
 Creating one connector per topic is a workaround that ensures that you get the fastest possible insert rate.
 
@@ -405,4 +405,4 @@ Kafka keys are not stored in the value field by default, but you can use the `Ke
 transforms=keyToValue
 transforms.keyToValue.type=com.clickhouse.kafka.connect.transforms.KeyToValue
 transforms.keyToValue.field=_key
-```
+```