Further edits

Author: gitName

learn-pr/azure/intro-to-containers/includes/3-exercise-deploy-docker-image-locally.md

@@ -33,7 +33,7 @@ In this exercise, you'll pull an image from Docker Hub and run it. You'll examin
     docker run -d -p 8080:8080 mcr.microsoft.com/dotnet/samples:aspnetapp
     ```
 
-1. Open a web browser and enter the URL for the sample web app: `http://localhost:8080`. You should see a page that looks like the following screenshot:
+1. Open a web browser and go to the URL for the sample web app: `http://localhost:8080`. You should get a page that looks like the following screenshot:
 
     :::image type="content" source="../media/3-sample-web-app.png" alt-text="Screenshot of the sample web app running in a browser." loc-scope="other"::: <!--no-loc -->
 

learn-pr/azure/intro-to-containers/includes/4-create-custom-docker-image.md

@@ -8,7 +8,7 @@ In this unit, you'll learn how to create a custom Docker image and how you can a
 
 To create a Docker image containing your application, you typically begin by identifying a *base image*, to which you add files and configuration information. The process of identifying a suitable base image usually starts with an image search on Docker Hub. You want an image that already contains an application framework and all the utilities and tools of a Linux distribution, like Ubuntu or Alpine. For example, if you have an ASP.NET Core application that you want to package into a container, Microsoft publishes an image called `mcr.microsoft.com/dotnet/core/aspnet` that already contains the ASP.NET Core runtime.
 
-You can customize an image by starting a container with the base image and making changes to it. Changes usually involve activities such as copying files into the container from the local filesystem and running various tools and utilities to compile code. When you're finished, you use the `docker commit` command to save the changes to a new image.
+You can customize an image by starting a container with the base image and making changes to it. Changes usually involve activities such as copying files into the container from the local filesystem and running various tools and utilities to compile code. When you're finished, you can use the `docker commit` command to save the changes to a new image.
 
 Manually completing the above process is time consuming and error prone. You could script it with a script language like Bash, but Docker provides a more effective way of automating image creation via a *Dockerfile*.
 
@@ -41,9 +41,9 @@ By convention, applications meant to be packaged as Docker images typically have
 
 The `docker build` command creates a new image by running a Dockerfile. This command's syntax has several parameters:
 
-- The *-f* flag indicates the name of the Dockerfile to use.
-- The *-t* flag specifies the name of the image to be created; in this example, *myapp:v1*.
-- The final parameter, *.*, provides the *build context* for the source files for the **COPY** command: the set of files on the host computer needed during the build process.
+- The `-f` flag indicates the name of the Dockerfile to use.
+- The `-t` flag specifies the name of the image to be created; in this example, *myapp:v1*.
+- The final parameter, `.`, provides the *build context* for the source files for the **COPY** command: the set of files on the host computer needed during the build process.
 
 ```bash
 docker build -t myapp:v1 .

learn-pr/azure/intro-to-containers/includes/5-exercise-create-custom-docker-image.md

@@ -104,7 +104,7 @@ In this exercise, you'll create a Dockerfile for an app that doesn't have one. T
     docker run -p 8080:80 -d --name reservations reservationsystem
     ```
 
-1. Start a web browser and navigate to `http://localhost:8080/api/reservations/1`. You should see a JSON object containing the data for reservation number 1 similar to the following output:
+1. Start a web browser and navigate to `http://localhost:8080/api/reservations/1`. You should get a JSON object containing the data for reservation number 1 similar to the following output:
 
     :::image type="content" source="../media/5-hotel-web-app.png" alt-text="Screenshot of the hotel reservations system web app running in a browser.":::
 

learn-pr/azure/intro-to-containers/includes/6-deploy-docker-image-to-container-instance.md

@@ -23,7 +23,7 @@ az group create --name mygroup --location westus
 az acr create --name <unique name> --resource-group mygroup --sku standard --admin-enabled true
 ```
 
-Different SKUs provide varying levels of scalability and storage.
+Different SKUs provide varying scalability and storage levels.
 
 Azure Container Registry repositories are private, meaning they don't support unauthenticated access. To pull images from an Azure Container Registry repository, use the `docker login` command and specify the URL of the login server for the registry. The login server URL for a registry in Azure Container Registry has the form \<*registry_name*\>.azurecr.io.
 
@@ -37,13 +37,13 @@ Docker login will prompt you for a username and password. To find this informati
 az acr credential show --name myregistry --resource-group mygroup
 ```
 
-You *push* an image from your local computer to a Docker registry by using the `docker push` command. Before you push an image, you must create an alias for the image that specifies the repository and tag that the Docker registry creates. The repository name must be of the form \*<login_server\>/<*image_name*\>:<*tag*/>. Use the `docker tag` command to perform this operation. The following example creates an alias for the *reservationsystem* image.
+You can *push* an image from your local computer to a Docker registry by using the `docker push` command. Before you push an image, you must create an alias for the image that specifies the repository and tag that the Docker registry creates. The repository name must be of the form \*<login_server\>/<*image_name*\>:<*tag*/>. Use the `docker tag` command to perform this operation. The following example creates an alias for the *reservationsystem* image.
 
 ```bash
 docker tag reservationsystem myregistry.azurecr.io/reservationsystem:v2
 ```
 
-If you run `docker image ls`, you'll see two entries for the image: one with the original name and the second with the new alias.
+If you run `docker image ls`, you'll get two entries for the image: one with the original name and the second with the new alias.
 
 After you run the tag command, you can upload the image to the registry in Azure Container Registry using the following command.
 
@@ -70,7 +70,7 @@ az acr repository show --repository reservationsystem --name myregistry --resour
 
 The Azure Container Instance service can load an image from Azure Container Registry and run it in Azure.
 
-You create a container instance and start the image running by using the `az container create` command. Provide the username and password for the registry in the `registry-username` and `registry-password` parameters. The instance will be allocated an IP address. You access the instance with this IP address. You can optionally specify a DNS name if you prefer to reference the instance through a more user-friendly label. Notice that you specify the image as a URL that references your registry (*myregistry*) in the Azure Container Registry service (*azurecr.io*). If you're using Docker Hub or some other registry, replace this URL with the URL of your image in that registry.
+You can create a container instance and start the image running by using the `az container create` command. Provide the username and password for the registry in the `registry-username` and `registry-password` parameters. The instance will be allocated an IP address. You access the instance with this IP address. You can optionally specify a DNS name if you prefer to reference the instance through a more user-friendly label. Notice that you specify the image as a URL that references your registry (*myregistry*) in the Azure Container Registry service (*azurecr.io*). If you're using Docker Hub or some other registry, replace this URL with the URL of your image in that registry.
 
 ```azurecli
 az container create --resource-group mygroup --name myinstance --image myregistry.azurecr.io/myapp:latest --dns-name-label mydnsname --registry-username <username> --registry-password <password>

learn-pr/azure/intro-to-containers/includes/7-exercise-deploy-docker-image-to-container-instance.md

@@ -12,7 +12,7 @@ In this exercise, you'll learn how to rebuild the image for the web app and uplo
 
 1. On the resource menu or from the **Home** page, select **Create a resource**. The **Create a resource** pane appears.
 
-1. In the menu, search for and select **Container Registry**.
+1. In the menu, search for **Container Registry**. In the Container Registry search result, select **Create** > **Container Registry**.
 
     :::image type="content" source="../media/7-search-container-registry.png" alt-text="Screenshot that shows Create a resource with Container Registry.":::
 
@@ -83,7 +83,7 @@ In this exercise, you'll learn how to rebuild the image for the web app and uplo
     docker push <registry-name>.azurecr.io/reservationsystem:latest
     ```
 
-    Wait until the upload completes. This process will take several minutes to push all the objects of the image to your repository. You can observe the progress as each object advances from *Waiting* to *Preparing* to *Pushing* to *Pushed*.
+    Wait until the upload completes. This process takes several minutes to push all the objects of the image to your repository. You can observe the progress as each object advances from *Waiting* to *Preparing* to *Pushing* to *Pushed*.
 
 ## Verify the registry contents
 
@@ -101,7 +101,7 @@ For the remainder of the exercise, you'll return to the Azure portal.
 
 1. In the Azure portal, select **Create a resource**. The **Create a resource** pane appears.
 
-1. In the resource menu, select **Containers**, and then select **Container Instances**.
+1. In the resource menu, select **Containers**, and then select **Create** > **Container Instances** in the **Container Instances** search item.
 
     :::image type="content" source="../media/7-search-container-instance.png" alt-text="Screenshot showing Container Instances.":::
 

learn-pr/azure/intro-to-containers/includes/8-summary.md

@@ -14,7 +14,7 @@ In this module, you created resources by using your Azure subscription. You want
 
 ## Learn More
 
-- [Docker overview](https://docs.docker.com/guides/docker-overview/)
+- [Docker overview](https://docs.docker.com/get-started/docker-overview/)
 - [Install Docker Desktop on Windows](https://docs.docker.com/desktop/install/windows-install/)
 - [Docker reference documentation](https://docs.docker.com/reference/)
 - [Best practices for writing Dockerfiles](https://docs.docker.com/build/building/best-practices/)