Merge pull request #51177 from v-thpra/azure-triage-fix-1062859

Fix for  Customer Feedback 1062859: Incorrect Explanation of PORTS Field in "Deploy a Docker Image Locally" Module

Author: prmerger-automator[bot]

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

@@ -1,8 +1,8 @@
 A good starting point for building and running your own Docker images is to take an existing image from Docker Hub and run it locally on your computer.
 
-As a proof of concept for the company's applications, you decide to try running a sample image from Docker Hub. The image you've selected implements a basic .NET Core ASP.NET web app. Once you've established a process for deploying a Docker image, you'll be able to run one of your company's own web apps using Docker.
+As a proof of concept for the company's applications, you decide to try running a sample image from Docker Hub. The image you selected implements a basic .NET Core ASP.NET web app. Once you establish a process for deploying a Docker image, you're able to run one of your company's own web apps using Docker.
 
-In this exercise, you'll pull an image from Docker Hub and run it. You'll examine the local state of Docker to help understand the elements that are deployed. Finally, you'll remove the container and image from your computer.
+In this exercise, you pull an image from Docker Hub and run it. You examine the local state of Docker to help understand the elements that are deployed. Finally, you remove the container and image from your computer.
 
 > [!IMPORTANT]
 > This exercise takes place on your computer, not in Azure. You need a local installation of Docker to proceed with the exercise. Download: https://docs.docker.com/desktop/install/windows-install/
@@ -19,15 +19,15 @@ In this exercise, you'll pull an image from Docker Hub and run it. You'll examin
     docker pull mcr.microsoft.com/dotnet/samples:aspnetapp
     ```
 
-1. Enter the following code to verify that the image has been stored locally.
+1. Enter the following code to verify that the image was stored locally.
 
     ```bash
     docker image ls
     ```
 
     You should see a repository named *mcr.microsoft.com/dotnet/samples* with a tag of *aspnetapp*.
 
-1. Enter the following code to start the sample app. The *-d* flag is to run it as a background, non-interactive app. The *-p* flag is to map port 8080 in the container that's created to port 8080 locally. This setting is intended to avoid conflicts with any web apps already running on your computer. The command will respond with a lengthy hexadecimal identifier for the instance.
+1. Enter the following code to start the sample app. The `-d` flag is to run it as a background, non-interactive app. The `p` flag is to map port 8080 in the container that's created to port 8080 locally. This setting is intended to avoid conflicts with any web apps already running on your computer. The command responds with a lengthy hexadecimal identifier for the instance.
 
     ```bash
     docker run -d -p 8080:8080 mcr.microsoft.com/dotnet/samples:aspnetapp
@@ -45,14 +45,14 @@ In this exercise, you'll pull an image from Docker Hub and run it. You'll examin
    docker ps
    ```
 
-   The output should look similar to the following:
+   The output should look similar to the following example:
 
    ```console
    CONTAINER ID   IMAGE                                             COMMAND                  CREATED          STATUS          PORTS                  NAMES
    96c851831ade   mcr.microsoft.com/dotnet/samples:aspnetapp   "dotnet aspnetapp.dll"   22 minutes ago   Up 22 minutes   0.0.0.0:8080->80/tcp   eager_montalcini
    ```
 
-   The **COMMAND** field shows the container started by running the command *dotnet aspnetapp.dll*. This command invokes the .NET Core runtime to start the code in the aspnetapp.dll (the code for the sample web app). The *PORTS* field indicates that port 8080 in the image was mapped to port 8080 on your computer. The *STATUS* field shows the application is still running. Make a note of the container's *NAME*.
+   The **COMMAND** field shows the container started by running the command *dotnet aspnetapp.dll*. This command invokes the .NET Core runtime to start the code in the aspnetapp.dll (the code for the sample web app). The *PORTS* field indicates that port 8080 in the image was mapped to port 80 on your computer. The *STATUS* field shows the application is still running. Make a note of the container's *NAME*.
 
 1. Run the following command to stop the Docker container, replacing the placeholder `<NAME>` with the output name from the previous command.
 
@@ -76,7 +76,7 @@ In this exercise, you'll pull an image from Docker Hub and run it. You'll examin
     docker container rm <NAME>
     ```
 
-1. Verify that the container has been removed by running the following command. The command should no longer list the container.
+1. Verify that the container was removed by running the following command. The command should no longer list the container.
 
     ```bash
     docker ps -a
@@ -94,7 +94,7 @@ In this exercise, you'll pull an image from Docker Hub and run it. You'll examin
     docker image rm mcr.microsoft.com/dotnet/samples:aspnetapp
     ```
 
-1. The output should list numerous items that have been untagged and deleted. Run the following command to list the images again and verify that the image for the *microsoft/dotnet-samples* web app has disappeared.
+1. The output should list numerous items that were untagged and deleted. Run the following command to list the images again and verify that the image for the *microsoft/dotnet-samples* web app has disappeared.
 
     ```bash
     docker image ls