Acrolinx edits

Author: sdwheeler

articles/cloud-shell/vnet/overview.md

@@ -11,7 +11,7 @@ By default, Azure Cloud Shell sessions run in a container in a Microsoft network
 from your resources. Commands that run inside the container can't access resources in a private
 virtual network. For example, you can't use Secure Shell (SSH) to connect from Cloud Shell to a
 virtual machine that has only a private IP address, or use `kubectl` to connect to a Kubernetes
-cluster that has locked down access.
+cluster with locked-down access.
 
 To provide access to your private resources, you can deploy Cloud Shell into an Azure virtual
 network that you control. This technique is called _virtual network isolation_.
@@ -56,13 +56,13 @@ The following diagram shows the resource architecture that you must build to ena
 ## Pricing
 
 Cloud Shell requires a new or existing Azure Files share to be mounted to persist files across
-sessions. Storage incurs regular costs. If you have deployed Azure Cloud Shell in a private virtual
+sessions. Storage incurs regular costs. When you deploy Azure Cloud Shell in a private virtual
 network, you pay for network resources. For pricing information, see
 [Pricing of Azure Cloud Shell][01].
 
 ## Next steps
 
-When you are ready to deploy your own instance of Cloud Shell, see
+When you're ready to deploy your own instance of Cloud Shell, see
 [Deploy Azure Cloud Shell in a virtual network with quickstart templates][03].
 
 <!-- link references -->

articles/cloud-shell/vnet/troubleshooting.md

@@ -13,7 +13,7 @@ This article provides instructions for troubleshooting a private virtual network
 Cloud Shell. For best results, and to be supportable, following the deployment instructions in the
 [Deploy Azure Cloud Shell in a virtual network using quickstart templates][03] article.
 
-## Verify you have set the correct permissions
+## Verify you have the correct permissions
 
 To configure Azure Cloud Shell in a virtual network, you must have the **Owner** role assignment on
 the subscription. To view and assign roles, see [List owners of a subscription][01].
@@ -109,7 +109,7 @@ The following list provides a description of the resources created by the deploy
 - A **Relay** resource with the name of the relay namespace you provided in the deployment template.
 - A **Storage account** resource with the name you provided in the deployment template.
 
-Once you have removed the resources, you can redeploy Cloud Shell by following the steps in the
+After you remove the resources, you can redeploy Cloud Shell by following the steps in the
 [Deploy Azure Cloud Shell in a virtual network using quickstart templates][03] article.
 
 You can find these resources by viewing the resource group in the Azure portal.