Merge pull request #236105 from spelluru/ehubjson0427

JSON support is in preview

Author: v-regandowner

articles/event-hubs/TOC.yml

@@ -63,7 +63,7 @@
       items:
         - name: Create a schema registry - Azure portal
           href: create-schema-registry.md  
-        - name: Validate events using a schema (.NET + AMQP)
+        - name: Validate events using an Avro schema (.NET + AMQP)
           href: schema-registry-dotnet-send-receive-quickstart.md
     - name: Create a dedicated cluster
       href: event-hubs-dedicated-cluster-create-portal.md

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

@@ -9,7 +9,7 @@ ms.date: 11/03/2022
 [Apache Kafka Connect](https://kafka.apache.org/documentation/#connect) is a framework to connect and import/export data from/to any external system such as MySQL, HDFS, and file system through a Kafka cluster. This tutorial walks you through using Kafka Connect framework with Event Hubs.
 
 > [!NOTE]
-> This feature is currently in Preview. 
+> This feature is currently in Preview. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
 
 > [!WARNING]
 > Use of the Apache Kafka Connect framework and its connectors is **not eligible for product support through Microsoft Azure**.
@@ -129,7 +129,7 @@ This section walks you through spinning up FileStreamSource and FileStreamSink c
     ```bash
     curl -s -X POST -H "Content-Type: application/json" --data '{"name": "file-source","config": {"connector.class":"org.apache.kafka.connect.file.FileStreamSourceConnector","tasks.max":"1","topic":"connect-quickstart","file": "{YOUR/HOME/PATH}/connect-quickstart/input.txt"}}' http://localhost:8083/connectors
     ```
-    You should see the Event Hub `connect-quickstart` on your Event Hubs instance after running the above command.
+    You should see the event hub `connect-quickstart` on your Event Hubs instance after running the above command.
 4. Check status of source connector.
     ```bash
     curl -s http://localhost:8083/connectors/file-source/status
@@ -155,7 +155,7 @@ This section walks you through spinning up FileStreamSource and FileStreamSink c
     ```
 
 ### Cleanup
-Kafka Connect creates Event Hub topics to store configurations, offsets, and status that persist even after the Connect cluster has been taken down. Unless this persistence is desired, it is recommended that these topics are deleted. You may also want to delete the `connect-quickstart` Event Hub that were created during the course of this walkthrough.
+Kafka Connect creates Event Hubs topics to store configurations, offsets, and status that persist even after the Connect cluster has been taken down. Unless this persistence is desired, it is recommended that these topics are deleted. You may also want to delete the `connect-quickstart` Event Hubs that were created during the course of this walkthrough.
 
 ## Next steps
 

articles/event-hubs/schema-registry-dotnet-send-receive-quickstart.md

@@ -8,7 +8,7 @@ author: kasun04
 ms.author: kindrasiri
 ---
 
-# Validate schema when streaming events using Event Hubs .NET SDKs (AMQP) 
+# Validate using an Avro schema when streaming events using Event Hubs .NET SDKs (AMQP) 
 In this quickstart, you learn how to send events to and receive events from an event hub with schema validation using the **Azure.Messaging.EventHubs** .NET library. 
 
 > [!NOTE]

articles/event-hubs/schema-registry-json-schema-kafka.md

@@ -8,12 +8,16 @@ author: kasun04
 ms.author: kindrasiri
 ---
 
-# Use JSON Schema with Apache Kafka applications 
+# Use JSON Schema with Apache Kafka applications (Preview)
 This tutorial walks you through a scenario where you use JSON Schemas to serialize and deserialize event using Azure Schema Registry in Event Hubs.
 
 In this use case a Kafka producer application uses JSON schema stored in Azure Schema Registry to, serialize the event and publish them to a Kafka topic/event hub in Azure Event Hubs. The Kafka consumer deserializes the events that it consumes from Event Hubs. For that it uses schema ID of the event and JSON schema, which is stored in Azure Schema Registry. 
 :::image type="content" source="./media/schema-registry-overview/kafka-json-schema.png" alt-text="Diagram showing the schema serialization/de-serialization for Kafka applications using JSON schema." border="false":::
 
+> [!NOTE]
+> This feature is currently in preview. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
+
+
 ## Prerequisites
 If you're new to Azure Event Hubs, see [Event Hubs overview](event-hubs-about.md) before you do this quickstart.