edit pass: apache-domain-joined-run

Author: paulth1

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

@@ -1,5 +1,5 @@
 ---
-title: Apache HBase & Enterprise Security Package - Azure HDInsight
+title: Tutorial - Apache HBase & Enterprise Security Package - Azure HDInsight
 description: Tutorial - Learn how to configure Apache Ranger policies for HBase in Azure HDInsight with Enterprise Security Package.
 ms.service: hdinsight
 ms.topic: tutorial
@@ -13,51 +13,49 @@ Learn how to configure Apache Ranger policies for Enterprise Security Package (E
 In this tutorial, you learn how to:
 
 > [!div class="checklist"]
-> * Create domain users
-> * Create Ranger policies
-> * Create tables in an HBase cluster
-> * Test Ranger policies
+> * Create domain users.
+> * Create Ranger policies.
+> * Create tables in an HBase cluster.
+> * Test Ranger policies.
 
 ## Before you begin
 
 * If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/).
-
 * Sign in to the [Azure portal](https://portal.azure.com/).
-
-* Create a [HDInsight HBase cluster with Enterprise Security Package](apache-domain-joined-configure-using-azure-adds.md).
+* Create an [HDInsight HBase cluster with Enterprise Security Package](apache-domain-joined-configure-using-azure-adds.md).
 
 ## Connect to Apache Ranger Admin UI
 
-1. From a browser, connect to the Ranger Admin user interface using the URL `https://<ClusterName>.azurehdinsight.net/Ranger/`. Remember to change `<ClusterName>` to the name of your HBase cluster.
+1. From a browser, connect to the Ranger Admin user interface (UI) by using the URL `https://<ClusterName>.azurehdinsight.net/Ranger/`. Remember to change `<ClusterName>` to the name of your HBase cluster.
 
-    > [!NOTE]  
-    > Ranger credentials are not the same as Hadoop cluster credentials. To prevent browsers from using cached Hadoop credentials, use a new InPrivate browser window to connect to the Ranger Admin UI.
+    > [!NOTE]
+    > Ranger credentials aren't the same as Hadoop cluster credentials. To prevent browsers from using cached Hadoop credentials, use a new InPrivate browser window to connect to the Ranger Admin UI.
 
-2. Sign in using your Microsoft Entra admin credentials. The Microsoft Entra admin credentials aren't the same as HDInsight cluster credentials or Linux HDInsight node SSH credentials.
+1. Sign in by using your Microsoft Entra admin credentials. The Microsoft Entra admin credentials aren't the same as HDInsight cluster credentials or Linux HDInsight node Secure Shell (SSH) credentials.
 
 ## Create domain users
 
-Visit [Create a HDInsight cluster with Enterprise Security Package](./apache-domain-joined-configure-using-azure-adds.md), to learn how to create the **sales_user1** and **marketing_user1** domain users. In a production scenario, domain users come from your Active Directory tenant.
+To learn how to create the **sales_user1** and **marketing_user1** domain users, see [Create an HDInsight cluster with Enterprise Security Package](./apache-domain-joined-configure-using-azure-adds.md). In a production scenario, domain users come from your Active Directory tenant.
 
 ## Create HBase tables and import sample data
 
 You can use SSH to connect to HBase clusters and then use [Apache HBase Shell](https://hbase.apache.org/0.94/book/shell.html) to create HBase tables, insert data, and query data. For more information, see [Use SSH with HDInsight](../hdinsight-hadoop-linux-use-ssh-unix.md).
 
-### To use the HBase shell
+### Use the HBase shell
 
 1. From SSH, run the following HBase command:
 
     ```bash
     hbase shell
     ```
 
-2. Create an HBase table `Customers` with two-column families: `Name` and `Contact`.
+1. Create an HBase table `Customers` with two column-families: `Name` and `Contact`.
 
     ```hbaseshell   
     create 'Customers', 'Name', 'Contact'
     list
     ```
-3. Insert some data:
+1. Insert some data:
 
     ```hbaseshell   
     put 'Customers','1001','Name:First','Alice'
@@ -75,29 +73,29 @@ You can use SSH to connect to HBase clusters and then use [Apache HBase Shell](h
     put 'Customers','1002','Contact:State','WA'
     put 'Customers','1002','Contact:ZipCode','98008'
     ```
-4. View the contents of the table:
+1. View the contents of the table:
 
     ```hbaseshell
     scan 'Customers'
     ```
 
-    :::image type="content" source="./media/apache-domain-joined-run-hbase/hbase-shell-scan-table.png" alt-text="HDInsight Hadoop HBase shell output" border="true":::
+    :::image type="content" source="./media/apache-domain-joined-run-hbase/hbase-shell-scan-table.png" alt-text="Screenshot that shows the HDInsight Hadoop HBase shell output." border="true":::
 
 ## Create Ranger policies
 
 Create a Ranger policy for **sales_user1** and **marketing_user1**.
 
-1. Open the **Ranger Admin UI**. Click **\<ClusterName>_hbase** under **HBase**.
+1. Open the **Ranger Admin UI**. Under **HBase**, select **\<ClusterName>_hbase**.
 
-   :::image type="content" source="./media/apache-domain-joined-run-hbase/apache-ranger-admin-login.png" alt-text="HDInsight Apache Ranger Admin UI" border="true":::
+   :::image type="content" source="./media/apache-domain-joined-run-hbase/apache-ranger-admin-login.png" alt-text="Screenshot that shows the HDInsight Apache Ranger Admin UI." border="true":::
 
-2. The **List of Policies** screen will display all Ranger policies created for this cluster. One pre-configured policy may be listed. Click **Add New Policy**.
+1. The **List of Policies** screen shows all Ranger policies created for this cluster. One preconfigured policy might be listed. Select **Add New Policy**.
 
-    :::image type="content" source="./media/apache-domain-joined-run-hbase/apache-ranger-hbase-policies-list.png" alt-text="Apache Ranger HBase policies list" border="true":::
+    :::image type="content" source="./media/apache-domain-joined-run-hbase/apache-ranger-hbase-policies-list.png" alt-text="Screenshot that shows the Apache Ranger HBase policies list." border="true":::
 
-3. On the **Create Policy** screen, enter the following values:
+1. On the **Create Policy** screen, enter the following values:
 
-   |**Setting**  |**Suggested value**  |
+   |Setting  |Suggested value  |
    |---------|---------|
    |Policy Name  |  sales_customers_name_contact   |
    |HBase Table   |  Customers |
@@ -112,16 +110,16 @@ Create a Ranger policy for **sales_user1** and **marketing_user1**.
    * `*` indicates zero or more occurrences of characters.
    * `?` indicates single character.
 
-   :::image type="content" source="./media/apache-domain-joined-run-hbase/apache-ranger-hbase-policy-create-sales.png" alt-text="Apache Ranger policy create sales" border="true":::
+   :::image type="content" source="./media/apache-domain-joined-run-hbase/apache-ranger-hbase-policy-create-sales.png" alt-text="Screenshot that shows the Apache Ranger policy Create sales." border="true":::
 
    >[!NOTE]
-   >Wait a few moments for Ranger to sync with Microsoft Entra ID if a domain user is not automatically populated for **Select User**.
+   >Wait a few moments for Ranger to sync with Microsoft Entra ID if a domain user isn't automatically populated for **Select User**.
 
-4. Click **Add** to save the policy.
+1. Select **Add** to save the policy.
 
-5. Click **Add New Policy** and then enter the following values:
+1. Select **Add New Policy** and then enter the following values:
 
-   |**Setting**  |**Suggested value**  |
+   |Setting  |Suggested value  |
    |---------|---------|
    |Policy Name  |  marketing_customers_contact   |
    |HBase Table   |  Customers |
@@ -131,13 +129,13 @@ Create a Ranger policy for **sales_user1** and **marketing_user1**.
    |Select User  | marketing_user1 |
    |Permissions  | Read |
 
-   :::image type="content" source="./media/apache-domain-joined-run-hbase/apache-ranger-hbase-policy-create-marketing.png" alt-text="Apache Ranger policy create marketing" border="true":::  
+   :::image type="content" source="./media/apache-domain-joined-run-hbase/apache-ranger-hbase-policy-create-marketing.png" alt-text="Screenshot that shows the Apache Ranger policy Create marketing." border="true":::
 
-6. Click **Add** to save the policy.
+1. Select **Add** to save the policy.
 
 ## Test the Ranger policies
 
-Based on the Ranger policies configured, **sales_user1** can view all of the data for the columns in both the `Name` and `Contact` column families. The **marketing_user1** can only view data in the `Contact` column family.
+Based on the Ranger policies configured, **sales_user1** can view all the data for the columns in both the `Name` and `Contact` column families. The **marketing_user1** can view data only in the `Contact` column family.
 
 ### Access data as sales_user1
 
@@ -147,20 +145,20 @@ Based on the Ranger policies configured, **sales_user1** can view all of the dat
    ssh [email protected]
    ```
 
-1. Use the kinit command to change to the context of our desired user.
+1. Use the `kinit` command to change to the context of the desired user:
 
    ```bash
    kinit sales_user1
    ```
 
-2. Open the HBase shell and scan the table `Customers`.
+1. Open the HBase shell and scan the table `Customers`:
 
    ```hbaseshell
    hbase shell
    scan `Customers`
    ```
 
-3. Notice that the sales user can view all columns of the `Customers` table including the two columns in the `Name` column-family, as well as the five columns in the `Contact` column-family.
+1. Notice that the sales user can view all columns of the `Customers` table. The user can see the two columns in the `Name` column-family and the five columns in the `Contact` column-family.
 
     ```hbaseshell
     ROW                                COLUMN+CELL
@@ -189,7 +187,7 @@ Based on the Ranger policies configured, **sales_user1** can view all of the dat
    ssh [email protected]
    ```
 
-1. Use the kinit command to change to the context of our desired user
+1. Use the `kinit` command to change to the context of our desired user:
 
    ```bash
    kinit marketing_user1
@@ -221,17 +219,17 @@ Based on the Ranger policies configured, **sales_user1** can view all of the dat
 
 1. View the audit access events from the Ranger UI.
 
-   :::image type="content" source="./media/apache-domain-joined-run-hbase/apache-ranger-admin-audit.png" alt-text="HDInsight Ranger UI Policy Audit" border="true":::
+   :::image type="content" source="./media/apache-domain-joined-run-hbase/apache-ranger-admin-audit.png" alt-text="Screenshot that shows the HDInsight Ranger UI Policy Audit." border="true":::
 
 ## Clean up resources
 
-If you're not going to continue to use this application, delete the HBase cluster that you created with the following steps:
+If you aren't going to continue to use this application, delete the HBase cluster that you created:
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).
-2. In the **Search** box at the top, type **HDInsight**. 
-1. Select **HDInsight clusters** under **Services**.
-1. In the list of HDInsight clusters that appears, click the **...** next to the cluster that you created for this tutorial. 
-1. Click **Delete**. Click **Yes**.
+1. In the **Search** box at the top, enter **HDInsight**.
+1. Under **Services**, select **HDInsight clusters**.
+1. In the list of HDInsight clusters that appears, select the **...** next to the cluster that you created for this tutorial.
+1. Select **Delete** > **Yes**.
 
 ## Next steps