Skip to content

Commit cf84903

Browse files
committed
touchups
1 parent c6f63a7 commit cf84903

File tree

3 files changed

+10
-10
lines changed

3 files changed

+10
-10
lines changed

articles/batch/quick-create-cli.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,7 @@ This quickstart uses Azure CLI commands and scripts to create and manage Batch r
2020

2121
You can run the Azure CLI commands in this quickstart interactively in Azure Cloud Shell. To run the commands in the Cloud Shell, select **Open Cloudshell** at the upper-right corner of a code block. Select **Copy** to copy the code, and paste it into Cloud Shell to run it. You can also [run Cloud Shell from within the Azure portal](https://shell.azure.com). Cloud Shell always uses the latest version of the Azure CLI.
2222

23-
You can also [install Azure CLI locally](/cli/azure/install-azure-cli) to run the commands. The steps in this article require Azure CLI version 2.0.20 or later. Run [az version](/cli/azure/reference-index?#az-version) to see your installed version and dependent libraries, and run [az upgrade](/cli/azure/reference-index?#az-upgrade) to upgrade.
24-
25-
If you use a local installation, sign in to Azure by using the [az login](/cli/azure/reference-index#az-login) command.
23+
You can also [install Azure CLI locally](/cli/azure/install-azure-cli) to run the commands. The steps in this article require Azure CLI version 2.0.20 or later. Run [az version](/cli/azure/reference-index?#az-version) to see your installed version and dependent libraries, and run [az upgrade](/cli/azure/reference-index?#az-upgrade) to upgrade. If you use a local installation, sign in to Azure by using the [az login](/cli/azure/reference-index#az-login) command.
2624

2725
## Create a resource group
2826

@@ -60,7 +58,7 @@ az batch account create \
6058
--location eastus2
6159
```
6260

63-
Sign in to the new Batch account by running the [az batch account login](/cli/azure/batch/account#az-batch-account-login) command. After you authenticate with Batch, the rest of the `az batch` quickstart commands use this account context.
61+
Sign in to the new Batch account by running the [az batch account login](/cli/azure/batch/account#az-batch-account-login) command. After you authenticate your account with Batch, the rest of the `az batch` quickstart commands use this account context.
6462

6563
```azurecli-interactive
6664
az batch account login \

articles/batch/quick-create-portal.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ Next, create a pool of Windows compute nodes in your Batch account. The followin
6262

6363
1. Accept the defaults for the remaining settings, and select **OK** at the bottom of the page.
6464

65-
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 do the following steps to create a job and tasks while the pool state is still resizing.
65+
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.
6666

6767
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.
6868

@@ -82,7 +82,7 @@ Now create a job to run on the pool. A Batch job is a logical group of one or mo
8282

8383
## Create tasks
8484

85-
Jobs can contain multiple tasks that Batch queues and distributes to run on the compute nodes. When you create a task, you specify your app or script in a command line. Batch provides several ways to deploy apps and scripts to compute nodes.
85+
Jobs can contain multiple tasks that Batch queues and distributes to run on the compute nodes. Batch provides several ways to deploy apps and scripts to compute nodes. When you create a task, you specify your app or script in a command line.
8686

8787
The following procedure creates and runs two identical tasks in your job. Each task runs a command line that displays the Batch environment variables on the compute node, and then waits 90 seconds.
8888

@@ -126,7 +126,9 @@ When you no longer need any of the resources you created for this quickstart, yo
126126

127127
## Next steps
128128

129-
In this quickstart, you created a Batch account and pool, and created and ran a Batch job and tasks. You monitored node and task status, and viewed task output from the nodes. Now that you understand the key concepts of the Batch service, you're ready to use Batch with more realistic, larger scale workloads. To learn more about Azure Batch, continue to the Azure Batch tutorials.
129+
In this quickstart, you created a Batch account and pool, and created and ran a Batch job and tasks. You monitored node and task status, and viewed task output from the nodes.
130+
131+
Now that you understand the key concepts of the Batch service, you're ready to use Batch with more realistic, larger scale workloads. To learn more about Azure Batch, continue to the Azure Batch tutorials.
130132

131133
> [!div class="nextstepaction"]
132134
> [Azure Batch tutorials](./tutorial-parallel-dotnet.md)

articles/batch/quick-run-dotnet.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ In Visual Studio:
8181
8282
1. Once the build completes, select **BatchDotNetQuickstart** in the top menu bar to run the app.
8383

84-
Typical run time using the default configuration is approximately five minutes. Initial pool node setup takes the most time. To rerun the job, delete the job from the previous run, but don't delete the pool. On a preconfigured pool, the job completes in a few seconds.
84+
Typical run time with the default configuration is approximately five minutes. Initial pool node setup takes the most time. To rerun the job, delete the job from the previous run, but don't delete the pool. On a preconfigured pool, the job completes in a few seconds.
8585

8686
The app returns output similar to the following example:
8787

@@ -213,9 +213,9 @@ try
213213

214214
### Create tasks
215215

216-
The app creates a list of [CloudTask](/dotnet/api/microsoft.azure.batch.cloudtask) objects. Each task processes an input `ResourceFile` object by using a [CommandLine](/dotnet/api/microsoft.azure.batch.cloudtask.commandline) property. The Batch command line is where you specify your app or script. Batch provides several ways to deploy apps and scripts to compute nodes.
216+
This app creates a list of [CloudTask](/dotnet/api/microsoft.azure.batch.cloudtask) objects. Each task processes an input `ResourceFile` object by using a [CommandLine](/dotnet/api/microsoft.azure.batch.cloudtask.commandline) property. Batch provides several ways to deploy apps and scripts to compute nodes. The Batch command line is where you specify your app or script.
217217

218-
The following script runs the Windows `type` command to display the input files. Then, the app adds each task to the job with the [AddTask](/dotnet/api/microsoft.azure.batch.joboperations.addtask) method, which queues the task to run on the compute nodes.
218+
The command line in the following code runs the Windows `type` command to display the input files. Then, the app adds each task to the job with the [AddTask](/dotnet/api/microsoft.azure.batch.joboperations.addtask) method, which queues the task to run on the compute nodes.
219219

220220
```csharp
221221
for (int i = 0; i < inputFiles.Count; i++)

0 commit comments

Comments
 (0)