Merge pull request #180497 from spelluru/ehubssr1119

fixed the flow

Author: PRMerger8

articles/event-hubs/schema-registry-overview.md

@@ -33,15 +33,18 @@ The following diagram shows how the information flows when event producers and c
 
 :::image type="content" source="./media/schema-registry-overview/information-flow.svg" lightbox="./media/schema-registry-overview/information-flow.svg" alt-text="Image showing the Schema Registry information flow.":::
 
-- The Kafka producer application uses ``KafkaAvroSerializer`` to serialize event data using the schema specified at the client side. 
-- Producer application must provide details of the schema registry endpoint and other optional parameters that are required for schema validation. 
-- The serializer does a lookup in the schema registry using the schema content that producer uses to serialize event data. 
-- If it finds such a schema, then the corresponding schema ID is returned. You can configure the producer application to If the schema doesn't exist, the producer application can configure schema registry client to auto register the schema. 
-- Then the serializer uses that schema ID and prepends that to the serialized data that is published to the Event Hubs. 
-- At the consumer side, ``KafkaAvroDeserializer`` uses the schema ID to retrieve the schema content from Schema Registry. 
-- The de-serializer then uses the schema content to deserialize event data that it read from the Event Hub. 
-- Schema registry clients use caching to prevent redundant schema registry lookups.  
+### Producer  
 
+1. Kafka producer application uses `KafkaAvroSerializer` to serialize event data using the specified schema. Producer application provides details of the schema registry endpoint and other optional parameters that are required for schema validation. 
+1. The serializer looks for the schema in the schema registry to serialize event data. If it finds the schema, then the corresponding schema ID is returned. You can configure the producer application to auto register the schema with the schema registry if it doesn't exist. 
+1. Then the serializer prepends the schema ID to the serialized data that is published to the Event Hubs. 
+
+### Consumer 
+
+1. Kafka consumer application uses `KafkaAvroDeserializer` to deserialize data that it receives from the event hub.
+1. The deserializer uses the schema ID (prepended by the producer) to retrieve schema from the schema registry.
+1. The de-serializer uses the schema to deserialize event data that it receives from the event hub. 
+1. The schema registry client uses caching to prevent redundant schema registry lookups in the future.  
 
 ## Schema Registry elements