Merge pull request #99388 from dlepow/acifresh5

[ACI freshness] Tutorial prepare reg

Author: PRMerger20

articles/container-instances/container-instances-tutorial-prepare-acr.md

@@ -2,18 +2,18 @@
 title: Tutorial - Prepare container registry to deploy image
 description: Azure Container Instances tutorial part 2 of 3 - Prepare an Azure container registry and push an image
 ms.topic: tutorial
-ms.date: 03/21/2018
+ms.date: 12/18/2019
 ms.custom: "seodec18, mvc"
 ---
 
-# Tutorial: Deploy an Azure container registry and push a container image
+# Tutorial: Create an Azure container registry and push a container image
 
 This is part two of a three-part tutorial. [Part one](container-instances-tutorial-prepare-app.md) of the tutorial created a Docker container image for a Node.js web application. In this tutorial, you push the image to Azure Container Registry. If you haven't yet created the container image, return to [Tutorial 1 – Create container image](container-instances-tutorial-prepare-app.md).
 
-Azure Container Registry is your private Docker registry in Azure. In this tutorial, you create an Azure Container Registry instance in your subscription, then push the previously created container image to it. In this article, part two of the series, you:
+Azure Container Registry is your private Docker registry in Azure. In this tutorial, part two of the series, you:
 
 > [!div class="checklist"]
-> * Create an Azure Container Registry instance
+> * Create an Azure Container Registry instance with the Azure CLI
 > * Tag a container image for your Azure container registry
 > * Upload the image to your registry
 
@@ -36,16 +36,15 @@ az group create --name myResourceGroup --location eastus
 Once you've created the resource group, create an Azure container registry with the [az acr create][az-acr-create] command. The container registry name must be unique within Azure, and contain 5-50 alphanumeric characters. Replace `<acrName>` with a unique name for your registry:
 
 ```azurecli
-az acr create --resource-group myResourceGroup --name <acrName> --sku Basic --admin-enabled true
+az acr create --resource-group myResourceGroup --name <acrName> --sku Basic
 ```
 
 Here's example output for a new Azure container registry named *mycontainerregistry082* (shown here truncated):
 
 ```console
-$ az acr create --resource-group myResourceGroup --name mycontainerregistry082 --sku Basic --admin-enabled true
+$ az acr create --resource-group myResourceGroup --name mycontainerregistry082 --sku Basic
 ...
 {
-  "adminUserEnabled": true,
   "creationDate": "2018-03-16T21:54:47.297875+00:00",
   "id": "/subscriptions/<Subscription ID>/resourceGroups/myResourceGroup/providers/Microsoft.ContainerRegistry/registries/mycontainerregistry082",
   "location": "eastus",
@@ -114,7 +113,7 @@ REPOSITORY          TAG       IMAGE ID        CREATED           SIZE
 aci-tutorial-app    latest    5c745774dfa9    39 minutes ago    68.1 MB
 ```
 
-Tag the *aci-tutorial-app* image with the loginServer of your container registry. Also, add the `:v1` tag to the end of the image name to indicate the image version number. Replace `<acrLoginServer>` with the result of the [az acr show][az-acr-show] command you executed earlier.
+Tag the *aci-tutorial-app* image with the login server of your container registry. Also, add the `:v1` tag to the end of the image name to indicate the image version number. Replace `<acrLoginServer>` with the result of the [az acr show][az-acr-show] command you executed earlier.
 
 ```bash
 docker tag aci-tutorial-app <acrLoginServer>/aci-tutorial-app:v1
@@ -131,7 +130,7 @@ mycontainerregistry082.azurecr.io/aci-tutorial-app    v1        5c745774dfa9
 
 ## Push image to Azure Container Registry
 
-Now that you've tagged the *aci-tutorial-app* image with the full login server name of your private registry, you can push it to the registry with the [docker push][docker-push] command. Replace `<acrLoginServer>` with the full login server name you obtained in the earlier step.
+Now that you've tagged the *aci-tutorial-app* image with the full login server name of your private registry, you can push the image to the registry with the [docker push][docker-push] command. Replace `<acrLoginServer>` with the full login server name you obtained in the earlier step.
 
 ```bash
 docker push <acrLoginServer>/aci-tutorial-app:v1
@@ -188,7 +187,7 @@ v1
 In this tutorial, you prepared an Azure container registry for use with Azure Container Instances, and pushed a container image to the registry. The following steps were completed:
 
 > [!div class="checklist"]
-> * Deployed an Azure Container Registry instance
+> * Created an Azure Container Registry instance with the Azure CLI
 > * Tagged a container image for Azure Container Registry
 > * Uploaded an image to Azure Container Registry
 

includes/container-instances-tutorial-prerequisites.md

@@ -17,7 +17,7 @@ You must satisfy the following requirements to complete this tutorial:
 
 **Docker**: This tutorial assumes a basic understanding of core Docker concepts like containers, container images, and basic `docker` commands. For a primer on Docker and container basics, see the [Docker overview][docker-get-started].
 
-**Docker Engine**: To complete this tutorial, you need Docker Engine installed locally. Docker provides packages that configure the Docker environment on [macOS][docker-mac], [Windows][docker-windows], and [Linux][docker-linux].
+**Docker**: To complete this tutorial, you need Docker installed locally. Docker provides packages that configure the Docker environment on [macOS][docker-mac], [Windows][docker-windows], and [Linux][docker-linux].
 
 > [!IMPORTANT]
 > Because the Azure Cloud shell does not include the Docker daemon, you *must* install both the Azure CLI and Docker Engine on your *local computer* to complete this tutorial. You cannot use the Azure Cloud Shell for this tutorial.