Improved Correctness Score

Author: Sreekanth Iyer (Ushta Te Consultancy Services)

articles/hdinsight/hdinsight-key-scenarios-to-monitor.md

@@ -60,7 +60,7 @@ For a more detailed look at your queues, from the Ambari dashboard, select the *
 
 In the Resource Manager UI, select **Scheduler** from the left-hand menu. You see a list of your queues underneath *Application Queues*. Here you can see the capacity used for each of your queues, how well the jobs are distributed between them, and whether any jobs are resource-constrained.
 
-:::image type="content" source="./media/hdinsight-key-scenarios-to-monitor/resource-manager-ui-menu.png" alt-text="Apache HAdoop Resource Manager UI menu.":::
+:::image type="content" source="./media/hdinsight-key-scenarios-to-monitor/resource-manager-ui-menu.png" alt-text="Apache Hadoop Resource Manager UI menu.":::
 
 ## Storage throttling
 

articles/hdinsight/interactive-query/hive-llap-sizing-guide.md

@@ -63,7 +63,7 @@ For D14 v2 worker nodes, the recommended value is **102400 MB**
 #### **3. Determining maximum amount of `vcores` per YARN container request**  
 Configuration: ***yarn.scheduler.maximum-allocation-vcores***  
 
-This value indicates the maximum number of virtual CPU cores for every container request at the Resource Manager. Requesting a higher number of `vcores` then this value won't take effect. It's a global property of the YARN scheduler. For LLAP daemon container, this value can be set to 75% of total available `vcores`. The remaining 25% should be reserved for NodeManager, DataNode, and other services running on the worker nodes.  
+This value indicates the maximum number of virtual CPU cores for every container request at the Resource Manager. Requesting a higher number of `vcores` than this value won't take effect. It's a global property of the YARN scheduler. For LLAP daemon container, this value can be set to 75% of total available `vcores`. The remaining 25% should be reserved for NodeManager, DataNode, and other services running on the worker nodes.  
 There are `16 vcores` on D14 v2 VMs and 75% of total `16 vcores` can be used by LLAP daemon container.  
 For D14 v2, the recommended value is **12**.  
 

articles/hdinsight/kafka/apache-kafka-azure-container-services.md

@@ -135,7 +135,7 @@ Use the following steps to configure Kafka to advertise IP addresses instead of
 
 9. To prevent errors when restarting Kafka, use the __Service Actions__ button and select __Turn On Maintenance Mode__. Select OK to complete this operation.
 
-    :::image type="content" source="./media/apache-kafka-azure-container-services/turn-on-maintenance-mode.png" alt-text="Service actions, with turn on maintenance highlighted." border="true":::
+    :::image type="content" source="./media/apache-kafka-azure-container-services/turn-on-maintenance-mode.png" alt-text="Service actions, with turn-on maintenance highlighted." border="true":::
 
 10. To restart Kafka, use the __Restart__ button and select __Restart All Affected__. Confirm the restart, and then use the __OK__ button after the operation is completed.