Update kafka-faq.yml

Author: v-akarnase

articles/hdinsight/kafka/kafka-faq.yml

@@ -71,7 +71,7 @@ sections:
       - question: |
           Can a Kafka cluster work with Databricks? 
         answer: |
-          Yes, Kafka clusters can work with Databricks so long as they are in the same VNet. To use a Kafka cluster with Databricks, create a VNet with an HDInsight Kafka cluster in it, then specify that VNet when you create your Databricks workspace and use VNet injection. For more information, see [Deploy Azure Databricks in your Azure Virtual Network (VNet Injection)](/azure/databricks/administration-guide/cloud-configurations/azure/vnet-inject). You will need to provide the bootstrap broker names of the Kafka cluster when creating the Databricks workspace. For information on retrieving the Kafka broker names, see [Get the Apache Zookeeper and Broker host information](./apache-kafka-get-started.md#getkafkainfo).
+          Yes, Kafka clusters can work with Databricks so long as they are in the same VNet. To use a Kafka cluster with Databricks, create a VNet with an HDInsight Kafka cluster in it, then specify that VNet when you create your Databricks workspace and use VNet injection. For more information, see [Deploy Azure Databricks in your Azure Virtual Network (VNet Injection)](/azure/databricks/administration-guide/cloud-configurations/azure/vnet-inject). You need to provide the bootstrap broker names of the Kafka cluster when creating the Databricks workspace. For information on retrieving the Kafka broker names, see [Get the Apache Zookeeper and Broker host information](./apache-kafka-get-started.md#getkafkainfo).
           
       - question: |
           How can I have maximum data durability?
@@ -81,7 +81,7 @@ sections:
           * use a minimum replication factor of 3 in most regions
           * use a minimum replication factor of 4 in regions with only two fault domains
           * disable unclean leader elections
-          * set **min.insync.replicas** to 2 or more - this changes the number of replicas which must be completely in sync with the leader before a write can proceed
+          * set **min.insync.replicas** to 2 or more - this changes the number of replicas, which must be completely in sync with the leader before a write can proceed
           * set the **acks** property to **all** - this property requires all replicas to acknowledge all messages
           
           Configuring Kafka for higher data consistency affects the availability of brokers to produce requests.