On branch edburns-msft-em-4947-liberty-aks-quickstart-reza-reviews Apply suggestions from @m-reza-rahman

modified:   articles/aks/howto-deploy-java-liberty-app.md

- This needs to focus on local setup by default, not cloud shell.
- “Leave all other values at the defaults” – this statement is unclear.
- az group delete --name $RESOURCE_GROUP_NAME --yes --no-wait – this is broken. There is no such variable.

Signed-off-by: Ed Burns <[email protected]>

Author: edburns

articles/aks/howto-deploy-java-liberty-app.md

@@ -33,7 +33,9 @@ This article is intended to help you quickly get to deployment. Before going to
 * This article requires at least version 2.31.0 of Azure CLI. If using Azure Cloud Shell, the latest version is already installed.
 
 > [!NOTE]
-> This guidance can also be executed from a local developer command line with Azure CLI installed. To learn how to install the Azure CLI, see [How to install the Azure CLI](/cli/azure/install-azure-cli).
+> You can also execute this guidance from the [Azure Cloud Shell](/azure/cloud-shell/quickstart). This approach has all the prerequisite tools pre-installed, with the exception of Docker.
+>
+> [![Image of button to launch Cloud Shell in a new window.](../../includes/media/cloud-shell-try-it/hdi-launch-cloud-shell.png)](https://shell.azure.com)
 
 * If running the commands in this guide locally (instead of Azure Cloud Shell):
   * Prepare a local machine with Unix-like operating system installed (for example, Ubuntu, Azure Linux, macOS, Windows Subsystem for Linux).
@@ -54,12 +56,30 @@ The following steps guide you to create a Liberty runtime on AKS. After completi
 
    1. Create a new resource group. Because resource groups must be unique within a subscription, pick a unique name. An easy way to have unique names is to use a combination of your initials, today's date, and some identifier. For example, `ejb0913-java-liberty-project-rg`.
    1. Select *East US* as **Region**.
+   
+   Create environment variables in your shell for the resource group names for the cluster and the database.
 
-1. Select **Next**, enter the **AKS** pane. This pane allows you to select an existing AKS cluster and Azure Container Registry (ACR), instead of causing the deployment to create a new one, if desired. This capability enables you to use the sidecar pattern, as shown in the [Azure architecture center](/azure/architecture/patterns/sidecar). You can also adjust the settings for the size and number of the virtual machines in the AKS node pool. Leave all other values at the defaults.
+   ### [Bash](#tab/in-bash)
+
+   ```bash
+   export RESOURCE_GROUP_NAME=<your-resource-group-name>
+   export DB_RESOURCE_GROUP_NAME=<your-resource-group-name>
+   ```
+
+   ### [PowerShell](#tab/in-powershell)
+
+   ```powershell
+   $Env:RESOURCE_GROUP_NAME="<your-resource-group-name>"
+   $Env:DB_RESOURCE_GROUP_NAME="<your-resource-group-name>"
+   ```
+
+   ---
+
+1. Select **Next**, enter the **AKS** pane. This pane allows you to select an existing AKS cluster and Azure Container Registry (ACR), instead of causing the deployment to create a new one, if desired. This capability enables you to use the sidecar pattern, as shown in the [Azure architecture center](/azure/architecture/patterns/sidecar). You can also adjust the settings for the size and number of the virtual machines in the AKS node pool. The remaining values do not need to be changed from their default values.
 
 1. Select **Next**, enter the **Load Balancing** pane. Next to **Connect to Azure Application Gateway?** select **Yes**. This section lets you customize the following deployment options.
 
-   1. You can customize the **virtual network** and **subnet** into which the deployment will place the resources. Leave these values at their defaults.
+   1. You can customize the **virtual network** and **subnet** into which the deployment will place the resources. The remaining values do not need to be changed from their default values.
    1. You can provide the **TLS/SSL certificate** presented by the Azure Application Gateway. Leave the values at the default to cause the offer to generate a self-signed certificate. Don't go to production using a self-signed certificate. For more information about self-signed certificates, see [Create a self-signed public certificate to authenticate your application](../active-directory/develop/howto-create-self-signed-certificate.md).
    1. You can select **Enable cookie based affinity**, also known as sticky sessions. We want sticky sessions enabled for this article, so ensure this option is selected.
 
@@ -443,14 +463,14 @@ To avoid Azure charges, you should clean up unnecessary resources. When the clus
 
 ```bash
 az group delete --name $RESOURCE_GROUP_NAME --yes --no-wait
-az group delete --name <db-resource-group> --yes --no-wait
+az group delete --name $DB_RESOURCE_GROUP_NAME --yes --no-wait
 ```
 
 ### [PowerShell](#tab/in-powershell)
 
 ```powershell
 az group delete --name $Env:RESOURCE_GROUP_NAME --yes --no-wait
-az group delete --name <db-resource-group> --yes --no-wait
+az group delete --name $Env:DB_RESOURCE_GROUP_NAME --yes --no-wait
 ```
 
 ---