Acrolynx

Author: LouisBerner

articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-powershell.md

@@ -26,8 +26,8 @@ The high-level deployment workflow of the VM deployment is as follows:
 1. Connect to the local Azure Resource Manager of your device.
 1. Identify the built-in subscription on the device.
 1. Bring your VM image.
-1. Create a resource group in the built-in subscription. The resource group will contain the VM and all the related resources.  
-1. Create a local storage account on the device to store the VHD that will be used to create a VM image.
+1. Create a resource group in the built-in subscription. The resource group contains the VM and all the related resources.  
+1. Create a local storage account on the device to store the VHD that is used to create a VM image.
 1. Upload a Windows/Linux source image into the storage account to create a managed disk.
 1. Use the managed disk to create a VM image.
 1. Enable compute on a device port to create a virtual switch.
@@ -188,7 +188,7 @@ Start by creating a new Azure resource group and use this as a logical container
     ```powershell
     $ResourceGroupName = "<Resource group name>" 
     ```
-1. Create a resource group for the resources that you'll create for the VM.
+1. Create a resource group for the resources that you create for the VM.
    
     ```powershell
     New-AzResourceGroup -Name $ResourceGroupName -Location DBELocal
@@ -332,7 +332,7 @@ C:\AzCopy.exe  cp "$VHDPath\$VHDFile" "$endPoint$ContainerName$StorageAccountSAS
 
 ## Create a managed disk from the VHD
 
-You will now create a managed disk from the uploaded VHD.
+You'll now create a managed disk from the uploaded VHD.
 
 ### [Az](#tab/az)
 
@@ -551,7 +551,7 @@ $aRmVN = Get-AzureRMVirtualNetwork -Name ASEVNET -ResourceGroupName ASERG
 
 ### Create a virtual network interface card
 
-You'll create a virtual network interface card by using the virtual network subnet ID.
+You create a virtual network interface card by using the virtual network subnet ID.
 
 ### [Az](#tab/az)
 
@@ -569,7 +569,7 @@ You'll create a virtual network interface card by using the virtual network subn
     $Nic = New-AzNetworkInterface -Name $NicName -ResourceGroupName $ResourceGroupName -Location DBELocal -IpConfiguration $IpConfig    
     ```
 
-    By default, an IP is dynamically assigned to your network interface from the network enabled for compute. Use the `-PrivateIpAddress parameter` if you are allocating a static IP to your network interface.         
+    By default, an IP is dynamically assigned to your network interface from the network enabled for compute. Use the `-PrivateIpAddress parameter` if you're allocating a static IP to your network interface.         
 
     Here's an example output:
     
@@ -647,7 +647,7 @@ $ipConfig = New-AzureRmNetworkInterfaceIpConfig -Name <IP config Name> -SubnetId
 $Nic = New-AzureRmNetworkInterface -Name <Nic name> -ResourceGroupName <Resource group name> -Location DBELocal -IpConfiguration $ipConfig
 ```
 
-By default, an IP is dynamically assigned to your network interface from the network enabled for compute. Use the `-PrivateIpAddress parameter` if you are allocating a static IP to your network interface. 
+By default, an IP is dynamically assigned to your network interface from the network enabled for compute. Use the `-PrivateIpAddress parameter` if you're allocating a static IP to your network interface. 
 
 Here's some example output:
 

articles/databox-online/azure-stack-edge-gpu-deploy-vm-specialized-image-powershell.md

@@ -39,7 +39,7 @@ The high-level workflow to deploy a VM from a specialized image is:
 
 Before you can deploy a VM on your device via PowerShell, make sure that:
 
-- You have access to a client that you'll use to connect to your device.
+- You have access to a client that you use to connect to your device.
     - Your client runs a [Supported OS](azure-stack-edge-gpu-system-requirements.md#supported-os-for-clients-connected-to-device).
     - Your client is configured to connect to the local Azure Resource Manager of your device as per the instructions in [Connect to Azure Resource Manager for your device](azure-stack-edge-gpu-connect-resource-manager.md).
 
@@ -53,7 +53,7 @@ Verify that your client can connect to the local Azure Resource Manager.
     Login-AzureRMAccount -EnvironmentName <Environment Name>
     ```
 
-2. Provide the username `EdgeArmUser` and the password to connect via Azure Resource Manager. If you do not recall the password, [Reset the password for Azure Resource Manager](azure-stack-edge-gpu-set-azure-resource-manager-password.md) and use this password to sign in.
+2. Provide the username `EdgeArmUser` and the password to connect via Azure Resource Manager. If you don't recall the password, [Reset the password for Azure Resource Manager](azure-stack-edge-gpu-set-azure-resource-manager-password.md) and use this password to sign in.
 
 ## Deploy VM from specialized image
 
@@ -65,7 +65,7 @@ Follow these steps to copy VHD to local storage account:
 
 1. Copy the source VHD to a local blob storage account on your Azure Stack Edge.
 
-1. Take note of the resulting URI. You'll use this URI in a later step.
+1. Take note of the resulting URI. You use this URI in a later step.
 
     To create and access a local storage account, see the sections [Create a storage account](azure-stack-edge-gpu-deploy-virtual-machine-powershell.md#create-a-local-storage-account) through [Upload a VHD](azure-stack-edge-gpu-deploy-virtual-machine-powershell.md#upload-a-vhd) in the article: [Deploy VMs on your Azure Stack Edge device via Azure PowerShell](azure-stack-edge-gpu-deploy-virtual-machine-powershell.md). 
 
@@ -80,7 +80,7 @@ Follow these steps to create a managed disk from a VHD that you uploaded to the
     $DiskRG = <managed disk resource group>
     $DiskName = <managed disk name>    
     ```
-    Here is an example output.
+    Here's an example output.
 
     ```powershell
     PS C:\WINDOWS\system32> $VHDURI = "https://myasevmsa.blob.myasegpudev.wdshcsso.com/vhds/WindowsServer2016Datacenter.vhd"
@@ -96,7 +96,7 @@ Follow these steps to create a managed disk from a VHD that you uploaded to the
 
     ```
 
-    Here is an example output. The location here is set to the location of the local storage account and is always `DBELocal` for all local storage accounts on your Azure Stack Edge Pro GPU device. 
+    Here's an example output. The location here is set to the location of the local storage account and is always `DBELocal` for all local storage accounts on your Azure Stack Edge Pro GPU device. 
 
     ```powershell
     PS C:\WINDOWS\system32> $DiskConfig = New-AzureRmDiskConfig -Location DBELocal -CreateOption Import -SourceUri $VHDURI
@@ -123,7 +123,7 @@ Follow these steps to create a VM from a managed disk:
     >[!NOTE]
     > The `PrivateIP` parameter is optional. Use this parameter to assign a static IP else the default is a dynamic IP using DHCP.
 
-    Here is an example output. In this example, the same resource group is specified for all the VM resources though you can create and specify separate resource groups for the resources if needed.
+    Here's an example output. In this example, the same resource group is specified for all the VM resources though you can create and specify separate resource groups for the resources if needed.
 
     ```powershell
     PS C:\WINDOWS\system32> $NicRG = "myasevm1rg"
@@ -137,15 +137,15 @@ Follow these steps to create a VM from a managed disk:
 
 1. Get the virtual network information and create a new network interface.
 
-    This sample assumes you are creating a single network interface on the default virtual network `ASEVNET` that is associated with the default resource group `ASERG`. If needed, you could specify an alternate virtual network, or create multiple network interfaces. For more information, see [Add a network interface to a VM via the Azure portal](azure-stack-edge-gpu-manage-virtual-machine-network-interfaces-portal.md).
+    This sample assumes you're creating a single network interface on the default virtual network `ASEVNET` that is associated with the default resource group `ASERG`. If needed, you could specify an alternate virtual network, or create multiple network interfaces. For more information, see [Add a network interface to a VM via the Azure portal](azure-stack-edge-gpu-manage-virtual-machine-network-interfaces-portal.md).
 
     ```powershell
     $armVN = Get-AzureRMVirtualNetwork -Name ASEVNET -ResourceGroupName ASERG
     $ipConfig = New-AzureRmNetworkInterfaceIpConfig -Name $IPConfigName -SubnetId $armVN.Subnets[0].Id [-PrivateIpAddress $PrivateIP]
     $nic = New-AzureRmNetworkInterface -Name $NicName -ResourceGroupName $NicRG -Location DBELocal -IpConfiguration $ipConfig
     ```
 
-    Here is an example output.
+    Here's an example output.
 
     ```powershell
     PS C:\WINDOWS\system32> $armVN = Get-AzureRMVirtualNetwork -Name ASEVNET -ResourceGroupName ASERG
@@ -172,15 +172,15 @@ Follow these steps to create a VM from a managed disk:
     ```powershell
     $vm = Set-AzureRmVMOSDisk -VM $vm -ManagedDiskId $disk.Id -StorageAccountType StandardLRS -CreateOption Attach –[Windows/Linux]
     ```
-    The last flag in this command will be either `-Windows` or `-Linux` depending on which OS you are using for your VM.
+    The last flag in this command will be either `-Windows` or `-Linux` depending on which OS you're using for your VM.
 
 1. Create the VM.
 
     ```powershell
     New-AzureRmVM -ResourceGroupName $VMRG -Location DBELocal -VM $vm 
     ```
 
-    Here is an example output. 
+    Here's an example output. 
 
     ```powershell
     PS C:\WINDOWS\system32> $vmConfig = New-AzureRmVMConfig -VMName $VMName -VMSize $VMSize
@@ -197,14 +197,14 @@ Follow these steps to create a VM from a managed disk:
 
 ## Delete VM and resources
 
-This article used only one resource group to create all the VM resource. Deleting that resource group will delete the VM and all the associated resources. 
+This article used only one resource group to create all the VM resource. Deleting that resource group deletes the VM and all the associated resources. 
 
 1. First view all the resources created under the resource group.
 
     ```powershell
     Get-AzureRmResource -ResourceGroupName <Resource group name>
     ```
-    Here is an example output.
+    Here's an example output.
     
     ```powershell
     PS C:\WINDOWS\system32> Get-AzureRmResource -ResourceGroupName myasevm1rg
@@ -246,7 +246,7 @@ This article used only one resource group to create all the VM resource. Deletin
     ```powershell
     Remove-AzureRmResourceGroup -ResourceGroupName <Resource group name>
     ```
-    Here is an example output.
+    Here's an example output.
     
     ```powershell
     PS C:\WINDOWS\system32> Remove-AzureRmResourceGroup -ResourceGroupName myasevm1rg
@@ -263,7 +263,7 @@ This article used only one resource group to create all the VM resource. Deletin
     ```powershell
     Get-AzureRmResourceGroup
     ```
-    Here is an example output.
+    Here's an example output.
 
     ```powershell
     PS C:\WINDOWS\system32> Get-AzureRmResourceGroup