acrolinx changes

Author: axisc

articles/event-hubs/schema-registry-client-side-enforcement.md

@@ -11,12 +11,12 @@ ms.author: spelluru
 
 Client-side schema enforcement ensures that the data sent by the producer application and received by the consumer application is validated against the schemas defined in the Schema Registry on the client side itself (that is, rather than on the broker/server side).
 
-This is illustrated in the diagram below.
+This flow is illustrated as shown - 
 
 :::image type="content" source="./media/schema-registry-overview/information-flow.svg" alt-text="Image showing the Schema Registry information flow." border="false":::
 
 > [!NOTE]
-> While the above diagram showcases the information flow when event producers and consumers use Schema Registry with the **Kafka** protocol and **Avro** schema, it doesn't really change for other protocols and schema formats.
+> While the diagram showcases the information flow when event producers and consumers use Schema Registry with the **Kafka** protocol and **Avro** schema, it doesn't really change for other protocols and schema formats.
 >
 
 ### Producer