quickstart edits

Author: schaffererin

articles/hdinsight/hadoop/apache-hadoop-linux-tutorial-get-started-bicep.md

@@ -6,7 +6,7 @@ ms.author: v-eschaffer
 ms.service: hdinsight
 ms.topic: quickstart
 ms.custom: subject-armqs, mode-arm
-ms.date: 04/08/2022
+ms.date: 04/14/2022
 #Customer intent: As a data analyst, I need to create a Hadoop cluster in Azure HDInsight using Bicep
 ---
 
@@ -54,10 +54,19 @@ Two Azure resources are defined in the Bicep file:
 
     ---
 
-    > [!NOTE]
-    > Replace **\<cluster-name\>** with the name of the HDInsight cluster to create. Replace **\<cluster-type\>** with the type of the HDInsight cluster to create. Allowed strings include: `hadoop`, `interactivehive`, `hbase`, `storm`, and `spark`. Replace **\<cluster-username\>** with the credentials used to submit jobs to the cluster and to log in to cluster dashboards. Replace **\<ssh-username\>** with the credentials used to remotely access the cluster. The username cannot be admin. You'll be prompted to enter **clusterLoginPassword**, which must be at least 10 characters long and contain one digit, one uppercase letter, one lowercase letter, and one non-alphanumeric character except single-quote, double-quote, backslash, right-bracket, full-stop. It also must not contain three consecutive characters from the cluster username or SSH username. You'll also be prompted to enter **sshPassword**, which must be 6-72 characters long and must contain at least one digit, one uppercase letter, and one lowercase letter. It must not contain any three consecutive characters from the cluster login name.
+    You need to provide values for the parameters:
+
+    * Replace **\<cluster-name\>** with the name of the HDInsight cluster to create.
+    * Replace **\<cluster-type\>** with the type of the HDInsight cluster to create. Allowed strings include: `hadoop`, `interactivehive`, `hbase`, `storm`, and `spark`.
+    * Replace **\<cluster-username\>** with the credentials used to submit jobs to the cluster and to log in to cluster dashboards. Replace **\<ssh-username\>** with the credentials used to remotely access the cluster. The username cannot be admin.
+
+    You'll also be prompted to enter the following:
 
-    When the deployment finishes, you should see a message indicating the deployment succeeded.
+    * **clusterLoginPassword**, which must be at least 10 characters long and contain one digit, one uppercase letter, one lowercase letter, and one non-alphanumeric character except single-quote, double-quote, backslash, right-bracket, full-stop. It also must not contain three consecutive characters from the cluster username or SSH username.
+    * **sshPassword**, which must be 6-72 characters long and must contain at least one digit, one uppercase letter, and one lowercase letter. It must not contain any three consecutive characters from the cluster login name.
+
+    > [!NOTE]
+    > When the deployment finishes, you should see a message indicating the deployment succeeded.
 
 ## Review deployed resources