Several quick fixes

Author: andynava

articles/aks/tutorial-kubernetes-prepare-acr.md

@@ -78,7 +78,7 @@ To get the login server address, use the [az acr list][az-acr-list] command and
 az acr list --resource-group myResourceGroup --query "[].{acrLoginServer:loginServer}" --output table
 ```
 
-Now, tag your local *azure-vote-front* image with the *acrloginServer* address of the container registry. To indicate the image version, add *:v1* to the end of the image name:
+Now, tag your local *azure-vote-front* image with the *acrLoginServer* address of the container registry. To indicate the image version, add *:v1* to the end of the image name:
 
 ```console
 docker tag azure-vote-front <acrLoginServer>/azure-vote-front:v1

articles/dev-spaces/quickstart-java.md

@@ -15,7 +15,7 @@ In this guide, you will learn how to:
 - Iteratively develop code in containers using Visual Studio Code.
 - Debug the code in your dev space from Visual Studio Code.
 
-Azure Dev Spaces also allows you debug and iterate using:
+Azure Dev Spaces also allows you to debug and iterate using:
 - [Node.js and Visual Studio Code](quickstart-nodejs.md)
 - [.NET Core and Visual Studio Code](quickstart-netcore.md)
 - [.NET Core and Visual Studio](quickstart-netcore-visualstudio.md)

articles/dev-spaces/quickstart-netcore.md

@@ -15,7 +15,7 @@ In this guide, you will learn how to:
 - Iteratively develop code in containers using Visual Studio Code.
 - Debug the code in your dev space from Visual Studio Code.
 
-Azure Dev Spaces also allows you debug and iterate using:
+Azure Dev Spaces also allows you to debug and iterate using:
 - [Java and Visual Studio Code](quickstart-java.md)
 - [Node.js and Visual Studio Code](quickstart-nodejs.md)
 - [.NET Core and Visual Studio](quickstart-netcore-visualstudio.md)
@@ -90,13 +90,13 @@ This command prepares your project to run in Azure Dev Spaces by generating a Do
 > [!TIP]
 > The [Dockerfile and Helm chart](how-dev-spaces-works.md#prepare-your-code) for your project is used by Azure Dev Spaces to build and run your code, but you can modify these files if you want to change how the project is built and ran.
 
-## Build and run code in Kubernetes from Visual Studio
+## Build and run code in Kubernetes from Visual Studio Code
 
 Click on the *Debug* icon on the left and click *.NET Core Launch (AZDS)* at the top.
 
 ![](media/get-started-netcore/debug-configuration.png)
 
-This command builds and runs your service in Azure Dev Spaces in debugging mode. The *Terminal* window at the bottom shows the build output and URLs for your service running Azure Dev Spaces. The *Debug Console* shows the log output.
+This command builds and runs your service in Azure Dev Spaces in debugging mode. The *Terminal* window at the bottom shows the build output and URLs for your service running in Azure Dev Spaces. The *Debug Console* shows the log output.
 
 > [!Note]
 > If you don't see any Azure Dev Spaces commands in the *Command Palette*, make sure you have installed the [Visual Studio Code extension for Azure Dev Spaces](https://marketplace.visualstudio.com/items?itemName=azuredevspaces.azds). Also verify you opened the *dev-spaces/samples/dotnetcore/getting-started/webfrontend* directory in Visual Studio Code.

articles/dev-spaces/quickstart-nodejs.md

@@ -15,7 +15,7 @@ In this guide, you will learn how to:
 - Iteratively develop code in containers using Visual Studio Code.
 - Debug the code in your dev space from Visual Studio Code.
 
-Azure Dev Spaces also allows you debug and iterate using:
+Azure Dev Spaces also allows you to debug and iterate using:
 - [Java and Visual Studio Code](quickstart-java.md)
 - [.NET Core and Visual Studio Code](quickstart-netcore.md)
 - [.NET Core and Visual Studio](quickstart-netcore-visualstudio.md)

articles/dev-spaces/quickstart-team-development.md

@@ -131,7 +131,7 @@ azds space select -n dev/azureuser1 -y
 azds space select -n dev/azureuser2 -y
 ```
 
-The above commands create two child spaces under *dev* named *azureuser1* and *azureuser2*. These two child spaces represent distinct dev spaces for the developers' *azureuser1* and *azureuser2* to use for making changes to the sample application.
+The above commands create two child spaces under *dev* named *azureuser1* and *azureuser2*. These two child spaces represent distinct dev spaces for developers *azureuser1* and *azureuser2* to use for making changes to the sample application.
 
 Use the `azds space list` command to list all the dev spaces and confirm *dev/azureuser2* is selected.