Merge pull request #226297 from kasun04/main

Fix Kafka Connect docs

Author: prmerger-automator[bot]

articles/event-hubs/event-hubs-kafka-connect-tutorial.md

@@ -13,12 +13,8 @@ ms.date: 11/03/2022
 
 > [!WARNING]
 > Use of the Apache Kafka Connect framework and its connectors is **not eligible for product support through Microsoft Azure**.
->
-> Apache Kafka Connect assumes for its dynamic configuration to be held in compacted topics with otherwise unlimited retention. Azure Event Hubs [does not implement compaction as a broker feature](event-hubs-federation-overview.md#log-projections) and always imposes a time-based retention limit on retained events, rooting from the principle that Azure Event Hubs is a real-time event streaming engine and not a long-term data or configuration store.
->
-> While the Apache Kafka project might be comfortable with mixing these roles, Azure believes that such information is best managed in a proper database or configuration store.
->
-> Many Apache Kafka Connect scenarios will be functional, but these conceptual differences between Apache Kafka's and Azure Event Hubs' retention models may cause certain configurations to not work as expected. 
+> Kafka Connect feature relies on Kafka Log compaction feature to fully function. [Log Compaction](./log-compaction.md) feature is currently available as a preview. Hence, Kafka Connect support is also in the preview state. 
+
 
 This tutorial walks you through integrating Kafka Connect with an event hub and deploying basic FileStreamSource and FileStreamSink connectors. This feature is currently in preview. While these connectors are not meant for production use, they demonstrate an end-to-end Kafka Connect scenario where Azure Event Hubs acts as a Kafka broker.