Resolved Review Comments

Author: Sreekanth Iyer (Ushta Te Consultancy Services)

articles/hdinsight/hdinsight-custom-ambari-db.md

@@ -58,7 +58,7 @@ When you host your Apache Ambari DB in an external database, remember the follow
 
 ## Deploy clusters with a custom Ambari DB
 
-To create a HDInsight cluster that uses your own external Ambari database, use the [custom Ambari DB Quickstart template](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.hdinsight/hdinsight-custom-ambari-db).
+To create an HDInsight cluster that uses your own external Ambari database, use the [custom Ambari DB Quickstart template](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.hdinsight/hdinsight-custom-ambari-db).
 
 Edit the parameters in the `azuredeploy.parameters.json` to specify information about your new cluster and the database that holds Ambari.
 

articles/hdinsight/hdinsight-hadoop-provision-linux-clusters.md

@@ -22,7 +22,7 @@ If you're using multiple clusters together, you want to create a virtual network
 
 ## Cluster setup methods
 
-The following table shows the different methods you can use to set up a HDInsight cluster.
+The following table shows the different methods you can use to set up an HDInsight cluster.
 
 | Clusters created with | Web browser | Command line | REST API | SDK |
 | --- |:---:|:---:|:---:|:---:|
@@ -33,7 +33,7 @@ The following table shows the different methods you can use to set up a HDInsigh
 | [cURL](hdinsight-hadoop-create-linux-clusters-curl-rest.md) |  |✅ |✅ |  |
 | [Azure Resource Manager templates](hdinsight-hadoop-create-linux-clusters-arm-templates.md) |  |✅ |  |  |
 
-This article walks you through setup in the [Azure portal](https://portal.azure.com), where you can create a HDInsight cluster.
+This article walks you through setup in the [Azure portal](https://portal.azure.com), where you can create an HDInsight cluster.
 
 ## Basics
 
@@ -136,9 +136,9 @@ For more information, see [Use external metadata stores in Azure HDInsight](./hd
 
 #### SQL database for Hive
 
-If you want to retain your Hive tables after you delete a HDInsight cluster, use a custom metastore. You can then attach the metastore to another HDInsight cluster.
+If you want to retain your Hive tables after you delete an HDInsight cluster, use a custom metastore. You can then attach the metastore to another HDInsight cluster.
 
-A HDInsight metastore that is created for one HDInsight cluster version can't be shared across different HDInsight cluster versions. For a list of HDInsight versions, see [Supported HDInsight versions](hdinsight-component-versioning.md#supported-hdinsight-versions).
+An HDInsight metastore that is created for one HDInsight cluster version can't be shared across different HDInsight cluster versions. For a list of HDInsight versions, see [Supported HDInsight versions](hdinsight-component-versioning.md#supported-hdinsight-versions).
 
 You can use Managed Identity to authenticate with SQL database for Hive. For more information, see [Use Managed Identity for SQL Database authentication in Azure HDInsight](./use-managed-identity-for-sql-database-authentication-in-azure-hdinsight.md)
 

articles/hdinsight/hdinsight-use-external-metadata-stores.md

@@ -57,7 +57,7 @@ HDInsight also supports custom metastores, which are recommended for production
 
 ### Create and config Azure SQL Database for the custom metastore
 
-Create or have an existing Azure SQL Database before setting up a custom Hive metastore for a HDInsight cluster.  For more information, see [Quickstart: Create a single database in Azure SQL Database](/azure/azure-sql/database/single-database-create-quickstart?tabs=azure-portal).
+Create or have an existing Azure SQL Database before setting up a custom Hive metastore for an HDInsight cluster.  For more information, see [Quickstart: Create a single database in Azure SQL Database](/azure/azure-sql/database/single-database-create-quickstart?tabs=azure-portal).
 
 When you create the cluster, HDInsight service needs to connect to the external metastore and verify your credentials. Configure Azure SQL Database firewall rules to allow Azure services and resources to access the server. Enable this option in the Azure portal by selecting **Set server firewall**. Then select **No** underneath **Deny public network access**, and **Yes** underneath **Allow Azure services and resources to access this server** for Azure SQL Database. For more information, see [Create and manage IP firewall rules](/azure/azure-sql/database/firewall-configure#use-the-azure-portal-to-manage-server-level-ip-firewall-rules)
 

articles/hdinsight/media/use-managed-identity-for-sql-database-authentication-in-azure-hdinsight/basic-tab.png

@@ -11,7 +11,7 @@ ms.date: 01/09/2025
 
 HDInsight added the Managed Identity option for authenticating SQL databases within its cluster offerings and providing a more secure authentication mechanism. 
 
-This article outlines the process of using the Managed Identity (MSI) option for SQL Database authentication when creating a HDInsight cluster. 
+This article outlines the process of using the Managed Identity (MSI) option for SQL Database authentication when creating an HDInsight cluster. 
 
 The Managed Identity (MI) option is available for the following Databases:
 
@@ -23,12 +23,12 @@ The Managed Identity (MI) option is available for the following Databases:
 |Ranger (ESP)|❌ | ❌ |
 
 > [!NOTE]
-> 1. Managed Identity (MI) is currently available only in public regions. It will be rolled out to other regions in future releases.
-> 2. MI option isn't enabled by default. To get it enabled, submit a [support ticket](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview) with your subscription and region details.
+> * Managed Identity (MI) is currently available only in public regions.
+> * MI option isn't enabled by default. To get it enabled, submit a [support ticket](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview) with your subscription and region details.
 
 > [!IMPORTANT]
-> 1. It's recommended not to update the Managed Identity after cluster recreation as it can disrupt cluster operation.
-> 2. When you recreate an MSI with the same name, users must recreate the contained user and reassign roles, as the new MSI will have different object and client IDs even if the name remains unchanged.
+> * It's recommended not to update the Managed Identity after cluster recreation as it can disrupt cluster operation.
+> *  When you recreate an MSI with the same name, users must recreate the contained user and reassign roles, as the new MSI will have different object and client IDs even if the name remains unchanged.
 
 
 ## Steps to Use Managed Identity during cluster creation in Azure portal
@@ -52,7 +52,7 @@ Object ID of managed identity can be obtained from portal on the managed identit
    >
    > For example: 
    > * MSI Name: contosoMSI 
-   > * Object ID: `2ba6c-1111-2222-3333-cccccccccccc`
+   > * Object ID: `aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb`
    > * user_name could be `contosoMSI-2ba6c`