finished adding content and acrolinx fixes

Author: asudbring

articles/virtual-network/deploy-container-networking-docker-linux.md

@@ -74,7 +74,7 @@ It can take a few minutes for the Bastion host to deploy. You can continue with
 
 ## Create virtual machine
 
-In this section, you'll create a Ubuntu virtual machine for the stand-alone Docker host. Ubuntu is used for the example in this article. The CNI plug-in supports Windows and other Linux distributions.
+In this section, you'll create an Ubuntu virtual machine for the stand-alone Docker host. Ubuntu is used for the example in this article. The CNI plug-in supports Windows and other Linux distributions.
 
 1. In the search box at the top of the portal, enter **Virtual machine**. Select **Virtual machines** in the search results.
 
@@ -100,7 +100,7 @@ In this section, you'll create a Ubuntu virtual machine for the stand-alone Dock
     | Authentication type | Select **Password**. |
     | Username | Enter a username. |
     | Password | Enter a password. |
-    | Confirm password | Re-enter password. |
+    | Confirm password | Reenter password. |
     | **Inbound port rules** |   |
     | Public inbound ports | Select **None**. |
 
@@ -121,17 +121,17 @@ In this section, you'll create a Ubuntu virtual machine for the stand-alone Dock
 
 ## Add IP configuration
 
-The Azure CNI plugin allocates IP addresses to containers based on a pool of IP addresses you create on the virtual network interface of the virtual machine. For every container on the host, a IP configuration must exist on the virtual network interface. If the number of containers on the server outnumber the IP configurations on the virtual network interface, the container will start but won't have an IP address. 
+The Azure CNI plugin allocates IP addresses to containers based on a pool of IP addresses you create on the virtual network interface of the virtual machine. For every container on the host, an IP configuration must exist on the virtual network interface. If the number of containers on the server outnumber the IP configurations on the virtual network interface, the container will start but won't have an IP address. 
 
-In this section you'll add an IP configuration to the virtual network interface of the virtual machine you created previously.
+In this section, you'll add an IP configuration to the virtual network interface of the virtual machine you created previously.
 
 1. In the search box at the top of the portal, enter **Virtual machine**. Select **Virtual machines** in the search results.
 
 2. Select **myVM**.
 
 3. In **Settings**, select **Networking**.
 
-4. Select the name of the network interface next to **Network Interface:**. The network interface is named **myvm** with a random number. In this example it's **myvm27**.
+4. Select the name of the network interface next to **Network Interface:**. The network interface is named **myvm** with a random number. In this example, it's **myvm27**.
 
 5. In **Settings** of the network interface, select **IP configurations**.
 
@@ -164,15 +164,15 @@ Repeat steps 1 through 13 to add as many configurations as containers you wish t
 
 The Docker container engine must be installed and configured on the virtual machine you created previously.
 
-For install instructions for Docker on a Ubuntu container host, see [Install Docker Engine on Ubuntu](https://docs.docker.com/engine/install/ubuntu/).
+For install instructions for Docker on an Ubuntu container host, see [Install Docker Engine on Ubuntu](https://docs.docker.com/engine/install/ubuntu/).
 
 After Docker is installed on the virtual machine, follow the instructions for the Linux post install. For instructions on the Linux post install, see [Docker Engine post-installation steps](https://docs.docker.com/engine/install/linux-postinstall/).
 
 After Docker is installed on your virtual machine, continue with the steps in this article.
 
-## Install CNI plugin
+## Install CNI plugin and create a test container
 
-The Azure CNI plugin is maintained as a Github project and is available for download from the project's Github page. For the purpose of this article, we will use **`git`** within the virtual machine to clone the repository for the plugin and then install and configure the plugin.
+The Azure CNI plugin is maintained as a GitHub project and is available for download from the project's GitHub page. For this article, you'll use **`git`** within the virtual machine to clone the repository for the plugin and then install and configure the plugin.
 
 For more information about the Azure CNI plugin, see [Microsoft Azure Container Networking](https://github.com/Azure/azure-container-networking).
 
@@ -201,19 +201,20 @@ For more information about the Azure CNI plugin, see [Microsoft Azure Container
 8. Configure permissions and install the CNI plugin. The install script command requires a version number for the CNI plugin. At the time of the writing of this article, the newest version is **`v1.4.39`**. To obtain the latest version number of the plugin or previous versions, see [Releases](https://github.com/Azure/azure-container-networking/releases).
 
     ```bash
+    cd azure-container-networking
     cd scripts
     chmod u+x install-cni-plugin.sh
     sudo ./install-cni-plugin.sh v1.4.39
     chmod u+x docker-run.sh
     ```
 
-9. To start a container with the CNI plugin, you must use a special script that comes with the plugin to create and start the container. The following example will create an Ubuntu container with the CNI plugin script:
+9. To start a container with the CNI plugin, you must use a special script that comes with the plugin to create and start the container. The following example will create an Alpine container with the CNI plugin script:
 
     ```bash
-    sudo ./docker-run.sh vnetdocker1 default ubuntu
+    sudo ./docker-run.sh vnetdocker1 default alpine
     ```
 
-10. To verify that the container received the IP address you previously configured for the network interface, you'll connect to the container and view the IP:
+10. To verify that the container received the IP address you previously configured, connect to the container and view the IP:
 
     ```bash
     sudo docker exec -it vnetdocker1 /bin/sh
@@ -223,13 +224,12 @@ For more information about the Azure CNI plugin, see [Microsoft Azure Container
 
     ```bash
     ifconfig
-    
     ```
-## Create test container
+    :::image type="content" source="./media/deploy-container-networking-docker-linux/ifconfig-output.png" alt-text="Screenshot of ifconfig output in Bash prompt of test container.":::
 
 ## Clean up resources
 
-If you're not going to continue to use this application, delete the virtual network, DDoS protection plan, and Route Server with the following steps:
+If you're not going to continue to use this application, delete the virtual network and virtual machine with the following steps:
 
 1. In the search box at the top of the portal, enter **Resource group**. Select **Resource groups** in the search results.
 
@@ -241,13 +241,12 @@ If you're not going to continue to use this application, delete the virtual netw
 
 5. Select **Delete**.
 
-
 ## Next steps
-<!-- Add a context sentence for the following links -->
-- [Write how-to guides](contribute-how-to-write-howto.md)
-- [Links](links-how-to.md)
-
-<!--
-Remove all the comments in this template before you sign-off or merge to the 
-main branch.
--->
+
+In this article, you learned how to install the Azure CNI plugin and create a test container.
+
+For more information about Azure container networking and Azure Kubernetes service, see:
+
+- [Deploy the Azure Virtual Network container network interface plug-in](deploy-container-networking.md)
+
+- [What is Azure Kubernetes Service?](/azure/aks/intro-kubernetes)