updates

Author: hsrasheed

articles/hdinsight/domain-joined/apache-domain-joined-run-kafka.md

@@ -6,7 +6,7 @@ ms.author: hrasheed
 ms.reviewer: jasonh
 ms.service: hdinsight
 ms.topic: tutorial
-ms.date: 09/04/2019
+ms.date: 05/19/2020
 ---
 
 # Tutorial: Configure Apache Kafka policies in HDInsight with Enterprise Security Package (Preview)
@@ -142,7 +142,8 @@ Based on the Ranger policies configured, **sales_user** can produce/consume topi
 
 4. Follow Step 3 under **Build and deploy the example** in [Tutorial: Use the Apache Kafka Producer and Consumer APIs](../kafka/apache-kafka-producer-consumer-api.md#build-and-deploy-the-example) to ensure that the `kafka-producer-consumer.jar` is also available to **sales_user**.
 
-**Note:  For this tutorial, please use the kafka-producer-consumer.jar under "DomainJoined-Producer-Consumer" project (not the one under Producer-Consumer project, which is for non domain joined scenarios).**
+> [!NOTE]  
+> For this tutorial, please use the kafka-producer-consumer.jar under "DomainJoined-Producer-Consumer" project (not the one under Producer-Consumer project, which is for non domain joined scenarios).
 
 5. Verify that **sales_user1** can produce to topic `salesevents` by executing the following command:
 

articles/hdinsight/kafka/apache-kafka-producer-consumer-api.md

@@ -156,7 +156,7 @@ If you would like to skip this step, prebuilt jars can be downloaded from the `P
 
     > [!Note]  
     > This command requires Ambari access. If your cluster is behind an NSG, run this command from a machine that can access Ambari.
-    
+
 1. Create Kafka topic, `myTest`, by entering the following command:
 
     ```bash
@@ -211,19 +211,9 @@ Records stored in Kafka are stored in the order they're received within a partit
 
 ## Common Issues faced
 
-1. Topic creation fails
-
-
-    If your cluster is Enterprise Security Pack enabled, use the [pre-built JAR files for producer and consumer](https://github.com/Azure-Samples/hdinsight-kafka-java-get-started/blob/master/Prebuilt-Jars/kafka-producer-consumer-esp.jar).
-
-    
-The ESP jar can be built from from the code in the [`DomainJoined-Producer-Consumer` subdirectory](https://github.com/Azure-Samples/hdinsight-kafka-java-get-started/tree/master/DomainJoined-Producer-Consumer). Note that the producer and consumer properties ave an additional property `CommonClientConfigs.SECURITY_PROTOCOL_CONFIG` for ESP enabled clusters.
-
-    
-2. Facing issue with ESP enabled clusters
-
-If produce and consume operations fail and you are using an ESP enabled cluster, check that the user `kafka` is present in all Ranger policies. If it is not present, add it to all Ranger policies.      
+1. **Topic creation fails** If your cluster is Enterprise Security Pack enabled, use the [pre-built JAR files for producer and consumer](https://github.com/Azure-Samples/hdinsight-kafka-java-get-started/blob/master/Prebuilt-Jars/kafka-producer-consumer-esp.jar). The ESP jar can be built from from the code in the [`DomainJoined-Producer-Consumer` subdirectory](https://github.com/Azure-Samples/hdinsight-kafka-java-get-started/tree/master/DomainJoined-Producer-Consumer). Note that the producer and consumer properties ave an additional property `CommonClientConfigs.SECURITY_PROTOCOL_CONFIG` for ESP enabled clusters.
 
+2. **Facing issue with ESP enabled clusters** If produce and consume operations fail and you are using an ESP enabled cluster, check that the user `kafka` is present in all Ranger policies. If it is not present, add it to all Ranger policies.
 
 ## Clean up resources