changes

Author: v-thepet

articles/batch/quick-create-cli.md

@@ -72,14 +72,15 @@ az batch account login \
 
 ## Create a pool of compute nodes
 
-Run the [az batch pool create](/cli/azure/batch/pool#az-batch-pool-create) command to create a pool of Linux compute nodes in your Batch account. The following example creates a pool named `myPool` that consists of two Standard_A1_v2 size VMs running Ubuntu 18.04 LTS OS. This node size offers a good balance of performance versus cost for this quickstart example.
+Run the [az batch pool create](/cli/azure/batch/pool#az-batch-pool-create) command to create a pool of Linux compute nodes in your Batch account. The following example creates a pool named `myPool` that consists of two Standard_A1_v2 size VMs running Ubuntu 20.04 LTS OS. This node size offers a good balance of performance versus cost for this quickstart example.
 
 ```azurecli-interactive
 az batch pool create \
-    --id myPool --vm-size Standard_A1_v2 \
+    --id myPool \
+    --image canonical:0001-com-ubuntu-server-focal:20_04-lts \
+    --node-agent-sku-id "batch.node.ubuntu 20.04" \
     --target-dedicated-nodes 2 \
-    --image canonical:ubuntuserver:18.04-LTS \
-    --node-agent-sku-id "batch.node.ubuntu 18.04"
+    --vm-size Standard_A1_v2
 ```
 
 Batch creates the pool immediately, but takes a few minutes to allocate and start the compute nodes. To see the pool status, use the [az batch pool show](/cli/azure/batch/pool#az-batch-pool-show) command. This command shows all the properties of the pool, and you can query for specific properties. The following command queries for the pool allocation state:

articles/batch/quick-create-portal.md

@@ -8,7 +8,7 @@ ms.custom: mvc, mode-ui
 
 # Quickstart: Use the Azure portal to create a Batch account and run a job
 
-This quickstart shows you how to get started with Azure Batch by using the Azure portal. You create a Batch account that has a pool of virtual machines, or compute nodes. You then create and run a job with tasks that run on the pool nodes.
+This quickstart shows you how to get started with Azure Batch by using the Azure portal. You create a Batch account that has a pool of virtual machines (VMs), or compute nodes. You then create and run a job with tasks that run on the pool nodes.
 
 After you complete this quickstart, you understand the [key concepts of the Batch service](batch-service-workflow-features.md) and are ready to use Batch with more realistic, larger scale workloads.
 
@@ -47,7 +47,7 @@ You need a Batch account to create pools and jobs. The following steps create an
 
 ## Create a pool of compute nodes
 
-Next, create a pool of Windows compute nodes in your Batch account. The following steps create a pool that consists of two Standard_A1_v2 size compute nodes running Windows Server 2019. This node size offers a good balance of performance versus cost for this quickstart.
+Next, create a pool of Windows compute nodes in your Batch account. The following steps create a pool that consists of two Standard_A1_v2 size VMs running Windows Server 2019. This node size offers a good balance of performance versus cost for this quickstart.
 
 1. On your Batch account page, select **Pools** from the left navigation.
 
@@ -65,7 +65,7 @@ Next, create a pool of Windows compute nodes in your Batch account. The followin
 
 1. Accept the defaults for the remaining settings, and select **OK** at the bottom of the page.
 
-Batch creates the pool immediately, but takes a few minutes to allocate and start the compute nodes. On the **Pools** page, select **myPool** to go to the **myPool** page and see the pool status of **Resizing** under **Essentials** > **Allocation state**. You can follow the next steps to create a job and tasks while the pool state is still resizing.
+Batch creates the pool immediately, but takes a few minutes to allocate and start the compute nodes. On the **Pools** page, you can select **myPool** to go to the **myPool** page and see the pool status of **Resizing** under **Essentials** > **Allocation state**. You can proceed to create a job and tasks while the pool state is still **Resizing** or **Starting**.
 
 After a few minutes, the **Allocation state** changes to **Steady**, and the nodes start. To check the state of the nodes, select **Nodes** in the **myPool** page left navigation. When a node's state is **Idle**, it's ready to run tasks.
 
@@ -101,29 +101,35 @@ The following procedure creates and runs two identical tasks in your job. Each t
 
 1. Repeat the preceding steps to create a second task, but enter *myTask2* for **Task ID**.
 
-After you create a task, Batch queues it to run on the pool. Once a node is available, the task runs on the node. In the quickstart example, if the first task is still running on one node, Batch starts the second task on the other node in the pool.
+After you create each task, Batch queues it to run on the pool. Once a node is available, the task runs on the node. In the quickstart example, if the first task is still running on one node, Batch starts the second task on the other node in the pool.
 
 ## View task output
 
-The tasks complete in a couple of minutes. You can select **Refresh** at the top of the **Tasks** page to view task status.
+The tasks should complete in a couple of minutes. To update task status, select **Refresh** at the top of the **Tasks** page.
 
-To view the output of a completed task, select the task from the **Tasks** page. On the task page, you can select the *stdout.txt* file to view the standard output of the task.
+To view the output of a completed task, you can select the task from the **Tasks** page. On the **myTask1** page, select the *stdout.txt* file to view the standard output of the task.
 
 :::image type="content" source="media/quick-create-portal/task-page.png" alt-text="Screenshot of a task page for a completed Batch job.":::
 
 The contents of the *stdout.txt* file are similar to the following example:
 
 :::image type="content" source="media/quick-create-portal/task-output.png" alt-text="Screenshot of the standard output file from a completed task.":::
 
-The standard output for this task shows the Azure Batch environment variables that are set on the node. You can refer to these environment variables in your Batch job task command lines, and in the apps and scripts the command lines run.
+The standard output for this task shows the Azure Batch environment variables that are set on the node. As long as this node exists, you can refer to these environment variables in Batch job task command lines, and in the apps and scripts the command lines run.
 
 ## Clean up resources
 
 If you want to continue with Batch tutorials and samples, you can use the Batch account and linked storage account that you created in this quickstart. There's no charge for the Batch account itself.
 
 Pools and nodes incur charges while the nodes are running, even if they aren't running jobs. When you no longer need a pool, delete it.
 
-To delete a pool, on your Batch account page, select **Pools** from the left navigation. Select the pool to delete on the **Pools** page, and then select **Delete** on the pool page. Deleting a pool deletes all task output on the nodes, and the nodes themselves.
+To delete a pool:
+
+1. On your Batch account page, select **Pools** from the left navigation.
+1. On the **Pools** page, select the pool to delete, and then select **Delete**.
+1. On the **Delete pool** screen, enter the name of the pool, and then select **Delete**.
+
+Deleting a pool deletes all task output on the nodes, and the nodes themselves.
 
 When you no longer need any of the resources you created for this quickstart, you can delete the resource group and all its resources, including the storage account, Batch account, and node pools. To delete the resource group, select **Delete resource group** at the top of the **qsBatch** resource group page. On the **Delete a resource group** screen, enter the resource group name *qsBatch*, and then select **Delete**.
 

articles/batch/quick-run-dotnet.md

@@ -25,7 +25,7 @@ After you complete this quickstart, you understand the [key concepts of the Batc
 
 - A Batch account with a linked Azure Storage account. You can create the accounts by using any of the following methods: [Azure CLI](quick-create-cli.md) | [Azure portal](quick-create-portal.md) | [Bicep](quick-create-bicep.md) | [ARM template](quick-create-template.md) | [Terraform](quick-create-terraform.md).
 
-- [Visual Studio 2017](https://www.visualstudio.com/vs) or later, or [.NET 6.0](https://dotnet.microsoft.com/download/dotnet) or later, for Linux or Windows.
+- [Visual Studio 2019](https://www.visualstudio.com/vs) or later, or [.NET 6.0](https://dotnet.microsoft.com/download/dotnet) or later, for Linux or Windows.
 
 ## Run the app