edit pass: acr-tasks

Author: ShawnJackson

articles/container-registry/buffer-gate-public-content.md

@@ -121,7 +121,7 @@ Developers of application images should ensure that their code references local
 
 ## Automate application image updates
 
-Expanding on image import, set up an [Azure Container Registry task](container-registry-tasks-overview.md) to automate application image builds when base images are updated. An automated build task can track both [base image updates](container-registry-tasks-base-images.md) and [source code updates](container-registry-tasks-overview.md#trigger-task-on-source-code-update).
+Expanding on image import, set up an [Azure Container Registry task](container-registry-tasks-overview.md) to automate application image builds when base images are updated. An automated build task can track both [base image updates](container-registry-tasks-base-images.md) and [source code updates](container-registry-tasks-overview.md#trigger-a-task-on-a-source-code-update).
 
 For a detailed example, see [How to consume and maintain public content with Azure Container Registry Tasks](tasks-consume-public-content.md). 
 

articles/container-registry/container-registry-intro.md

@@ -28,7 +28,7 @@ Developers can also push to a container registry as part of a container developm
 
 Configure Azure Container Registry tasks to automatically rebuild application images when their base images are updated, or automate image builds when your team commits code to a Git repository. Create multi-step tasks to automate building, testing, and patching container images in parallel in the cloud.
 
-Azure provides tooling like the Azure CLI, the Azure portal, and API support to manage your container registries. Optionally, install the [Docker Extension for Visual Studio Code](https://code.visualstudio.com/docs/azure/docker) and the [Azure Account](https://marketplace.visualstudio.com/items?itemName=ms-vscode.azure-account) extension to work with your container registries. Pull and push images to a container registry, or run Azure Container Registry tasks, all within Visual Studio Code.
+Azure provides tooling like the Azure CLI, the Azure portal, and API support to manage your container registries. Optionally, install the [Docker extension](https://code.visualstudio.com/docs/azure/docker) and the [Azure Account extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode.azure-account) for Visual Studio Code. You can use these extensions to pull images from a container registry, push images to a container registry, or run Azure Container Registry tasks, all within Visual Studio Code.
 
 ## Key features
 
@@ -47,7 +47,7 @@ Azure provides tooling like the Azure CLI, the Azure portal, and API support to
 
 * **Supported images and artifacts**: When images are grouped in a repository, each image is a read-only snapshot of a Docker-compatible container. Azure container registries can include both Windows and Linux images. You control image names for all your container deployments.
 
-  Use standard [Docker commands](https://docs.docker.com/engine/reference/commandline/) to push images into a repository, or pull an image from a repository. In addition to Docker container images, Azure Container Registry stores [related content formats](container-registry-image-formats.md) such as [Helm charts](container-registry-helm-repos.md) and images built to the [Open Container Initiative (OCI) Image Format Specification](https://github.com/opencontainers/image-spec/blob/master/spec.md).
+  Use standard [Docker commands](https://docs.docker.com/engine/reference/commandline/) to push images into a repository or pull an image from a repository. In addition to Docker container images, Azure Container Registry stores [related content formats](container-registry-image-formats.md) such as [Helm charts](container-registry-helm-repos.md) and images built to the [Open Container Initiative (OCI) Image Format Specification](https://github.com/opencontainers/image-spec/blob/master/spec.md).
 
 * **Automated image builds**: Use [Azure Container Registry tasks](container-registry-tasks-overview.md) to streamline building, testing, pushing, and deploying images in Azure. For example, use Azure Container Registry tasks to extend your development inner loop to the cloud by offloading `docker build` operations to Azure. Configure build tasks to automate your container OS and framework patching pipeline, and build images automatically when your team commits code to source control.
 

articles/container-registry/container-registry-service-tag.md

@@ -39,7 +39,7 @@ For detailed steps on creating a webhook setup, refer to the [Azure Container Re
 
 When you're using Azure Container Registry tasks, such as when you're building container images or automating workflows, the service tag represents the group of IP address prefixes that Azure Container Registry uses.
 
-During the execution of tasks, Azure Container Registry send requests to external resources through the IP addresses for service tags. If an external resource runs behind a firewall, it requires an inbound rule to allow these IP addresses. Applying these inbound rules is a common practice to help ensure security and proper access management in cloud environments.
+During the execution of tasks, Azure Container Registry sends requests to external resources through the IP addresses for service tags. If an external resource runs behind a firewall, it requires an inbound rule to allow these IP addresses. Applying these inbound rules is a common practice to help ensure security and proper access management in cloud environments.
 
 To learn more about Azure Container Registry tasks, see [Automate container image builds and maintenance with Azure Container Registry tasks](container-registry-tasks-overview.md). To learn how to use a service tag to set up firewall access rules for Azure Container Registry tasks, see [Configure rules to access an Azure container registry behind a firewall](container-registry-firewall-access-rules.md).
 

articles/container-registry/container-registry-tasks-overview.md

@@ -40,9 +40,9 @@ The *inner-loop* development cycle is the iterative process of writing code, bui
 
 The *quick task* feature in Azure Container Registry tasks can provide an integrated development experience by offloading your container image builds to Azure. You can build and push a single container image to a container registry on demand, in Azure, without needing a local Docker Engine installation. Think `docker build`, `docker push` in the cloud. With quick tasks, you can verify your automated build definitions and catch potential problems before committing your code.
 
-By using the familiar `docker build` format, the [az acr build][az-acr-build] command in the Azure CLI takes a [context](#context-locations), which is the set of files to build. The command then sends the context to Azure Container Registry and pushes the built image to its registry upon completion.
+By using the familiar `docker build` format, the [az acr build][az-acr-build] command in the Azure CLI takes a [context](#context-locations). The command then sends the context to Azure Container Registry and (by default) pushes the built image to its registry upon completion.
 
-Azure Container Registry tasks are designed as a container lifecycle primitive. For example, you can integrate Azure Container Registry tasks into your continuous integration and continuous delivery (CI/CD) solution. By running [az login][az-login] with a [service principal][az-login-service-principal], your CI/CD solution could then issue [az acr build][az-acr-build] commands to start image builds.
+Azure Container Registry tasks are designed as a container lifecycle primitive. For example, you can integrate Azure Container Registry tasks into your continuous integration and continuous delivery (CI/CD) solution. If you run [az login][az-login] with a [service principal][az-login-service-principal], your CI/CD solution can then issue [az acr build][az-acr-build] commands to start image builds.
 
 To learn how to use quick tasks, see the [quickstart](container-registry-quickstart-task-cli.md) and [tutorial](container-registry-tutorial-quick-task.md) for building and deploying container images by using Azure Container Registry tasks.
 
@@ -140,15 +140,15 @@ By default, Azure Container Registry tasks build images for the Linux OS and the
 
 ## Task output
 
-Each task run generates log output that you can inspect to determine whether the task steps ran successfully. When you trigger a task manually, log output for the task run is streamed to the console and stored for later retrieval. When a task is automatically triggered (for example, by a source code commit or a base image update), task logs are only stored. View the run logs in the Azure portal, or use the [az acr task logs](/cli/azure/acr/task#az-acr-task-logs) command.
+Each task run generates log output that you can inspect to determine whether the task steps ran successfully. When you trigger a task manually, log output for the task run is streamed to the console and stored for later retrieval. When a task is triggered automatically (for example, by a source code commit or a base image update), task logs are only stored. View the run logs in the Azure portal, or use the [az acr task logs](/cli/azure/acr/task#az-acr-task-logs) command.
 
 [Learn more about viewing and managing task logs](container-registry-tasks-logs.md).
 
 ## Related content
 
 - When you're ready to automate container image builds and maintenance in the cloud, see [Tutorial: Build and deploy container images in the cloud with Azure Container Registry tasks](container-registry-tutorial-quick-task.md).
 
-- Optionally, learn about the [Docker Extension for Visual Studio Code](https://code.visualstudio.com/docs/azure/docker) and the [Azure Account](https://marketplace.visualstudio.com/items?itemName=ms-vscode.azure-account) extension. You can use these extensions to pull and push images to a container registry, or run Azure Container Registry tasks, within Visual Studio Code.
+- Optionally, learn about the [Docker extension](https://code.visualstudio.com/docs/azure/docker) and the [Azure Account extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode.azure-account) for Visual Studio Code. You can use these extensions to pull images from a container registry, push images to a container registry, or run Azure Container Registry tasks, all within Visual Studio Code.
 
 <!-- LINKS - Internal -->
 [az-acr-build]: /cli/azure/acr#az-acr-build