Updated docs based on Pavithra's feedback.

Author: Heidilohr

articles/virtual-desktop/configure-host-pool-load-balancing.md

@@ -19,9 +19,7 @@ Configuring the load-balancing method for a host pool allows you to adjust the W
 
 ## Prerequisites
 
-This article assumes you've followed the instructions in [Set up the Windows Virtual Desktop PowerShell module]() to download and install the PowerShell module and sign in to your Azure account.
-
-<!--->This needs a link<--->
+This article assumes you've followed the instructions in [Set up the Windows Virtual Desktop PowerShell module](powershell-module.md) to download and install the PowerShell module and sign in to your Azure account.
 
 ## Configure breadth-first load balancing
 
@@ -36,7 +34,7 @@ Update-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname>
 After that, to make sure you've set the breadth-first load balancing method, run the following cmdlet: 
 
 ```powershell
-Update-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> | format-list Name, LoadBalancerType 
+Get-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> | format-list Name, LoadBalancerType 
 
 Name             : hostpoolname 
 LoadBalancerType : BreadthFirst
@@ -61,7 +59,7 @@ Update-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname>
 To make sure the setting has updated, run this cmdlet:
 
 ```powershell
-Update-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> | format-list Name, LoadBalancerType, MaxSessionLimit 
+Get-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> | format-list Name, LoadBalancerType, MaxSessionLimit 
 
 Name             : hostpoolname
 LoadBalancerType : DepthFirst

articles/virtual-desktop/configure-host-pool-personal-desktop-assignment-type.md

@@ -33,9 +33,6 @@ Automatic assignment is the default assignment type for new personal desktop hos
 
 To automatically assign users, first assign them to the personal desktop host pool so that they can see the desktop in their feed. When an assigned user launches the desktop in their feed, they will claim an available session host if they have not already connected to the host pool, which completes the assignment process.
 
-> [!NOTE]
-> Make sure you've installed Windows Virtual Desktop PowerShell module version 1.0.1534.2001 or later before following these instructions.
-
 To configure a host pool to automatically assign users to VMs, run the following PowerShell cmdlet:
 
 ```powershell

articles/virtual-desktop/create-validation-host-pool.md

@@ -27,28 +27,28 @@ You can debug issues in the validation host pool with either [the diagnostics fe
 >[!NOTE]
 > We recommend that you leave the validation host pool in place to test all future updates.
 
-## Prerequisites
+>[!IMPORTANT]
+>The Windows Virtual Desktop Spring 2020 release currently has trouble enabling and disabling validation environment. We'll update this article when we've resolved the issue.
 
-Before you begin, follow the instructions in [Set up the Windows Virtual Desktop PowerShell module]() to set up your PowerShell module and sign in to Azure.
+## Prerequisites
 
-<!-->Create link to this page when article is ready<--->
+Before you begin, follow the instructions in [Set up the Windows Virtual Desktop PowerShell module](powershell-module.md) to set up your PowerShell module and sign in to Azure.
 
 ## Create your host pool
 
 You can create a host pool by following the instructions in any of these articles:
 - [Tutorial: Create a host pool with Azure Marketplace](create-host-pools-azure-marketplace.md)
-- [Create a host pool with an Azure Resource Manager template](./virtual-desktop-fall-2019/create-host-pools-arm-template.md)
 - [Create a host pool with PowerShell](create-host-pools-powershell.md)
 
 ## Define your host pool as a validation host pool
 
-Run the following PowerShell cmdlets to define the new host pool as a validation host pool. Replace the values in quotes by the values relevant to your session:
+Run the following PowerShell cmdlets to define the new host pool as a validation host pool. Replace the values in brackets with the values relevant to your session:
 
 ```powershell
 Update-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> -ValidationEnvironment:$true
 ```
 
-Run the following PowerShell cmdlet to confirm that the validation property has been set. Replace the values in quotes by the values relevant to your session.
+Run the following PowerShell cmdlet to confirm that the validation property has been set. Replace the values in brackets with the values relevant to your session.
 
 ```powershell
 Get-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> | Format-List

articles/virtual-desktop/customize-feed-for-virtual-desktop-users.md

@@ -34,7 +34,7 @@ To retrieve a list of published RemoteApps for an app group, run the following P
 Get-AzWvdApplication -ResourceGroupName <resourcegroupname> -ApplicationGroupName <appgroupname>
 ```
 
-To assign a friendly name to a RemoteApp, run the following PowerShell cmdlet:
+To assign a friendly name to a RemoteApp, run the following cmdlet with the required parameters:
 
 ```powershell
 Update-AzWvdApplication -ResourceGroupName <resourcegroupname> -ApplicationGroupName <appgroupname> -Name <applicationname> -FriendlyName <newfriendlyname>
@@ -107,7 +107,7 @@ You can change the display name for a published remote desktop by setting a frie
 
 3. Under Services, select **Windows Virtual Desktop**. 
 
-4. On the Windows Virtual Desktop page, select the application groups you want to edit on the left side of the screen. 
+4. On the Windows Virtual Desktop page, select **Application groups** on the left side of the screen, then select the name of the app group you want to edit. 
 
 5. Select **Applications** in the menu on the left side of the screen.
 

articles/virtual-desktop/customize-rdp-properties.md

@@ -18,15 +18,13 @@ manager: lizross
 > The Windows Virtual Desktop Spring 2020 update is currently in public preview. This preview version is provided without a service level agreement, and we don't recommend using it for production workloads. Certain features might not be supported or might have constrained capabilities. 
 > For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
-Customizing a host pool's Remote Desktop Protocol (RDP) properties, such as multi-monitor experience and audio redirection, lets you deliver an optimal experience for your users based on their needs. You can customize RDP properties in Windows Virtual Desktop by either using the Azure portal or by using the *-CustomRdpProperty* parameter in the **Get-AzWvdHostPool** cmdlet.
+Customizing a host pool's Remote Desktop Protocol (RDP) properties, such as multi-monitor experience and audio redirection, lets you deliver an optimal experience for your users based on their needs. You can customize RDP properties in Windows Virtual Desktop by either using the Azure portal or by using the *-CustomRdpProperty* parameter in the **Update-AzWvdHostPool** cmdlet.
 
 See [supported RDP file settings](https://docs.microsoft.com/windows-server/remote/remote-desktop-services/clients/rdp-files?context=/azure/virtual-desktop/context/context) for a full list of supported properties and their default values.
 
 ## Prerequisites
 
-Before you begin, follow the instructions in [Set up the Windows Virtual Desktop PowerShell module]() to set up your PowerShell module and sign in to Azure.
-
-<!-->Create link to this page when article is ready<--->
+Before you begin, follow the instructions in [Set up the Windows Virtual Desktop PowerShell module](powershell-module.md) to set up your PowerShell module and sign in to Azure.
 
 ## Default RDP properties
 
@@ -57,7 +55,7 @@ If there's a setting you want to edit that you don't see in the RDP settings men
 
 ## Add or edit a single custom RDP property
 
-To add or edit multiple custom RDP properties, run the following PowerShell cmdlets and enter the custom RDP properties as a semicolon-separated string:
+To add or edit a single custom RDP property, run the following PowerShell cmdlet:
 
 ```powershell
 Update-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> -CustomRdpProperty <property>
@@ -75,7 +73,7 @@ CustomRdpProperty : <customRDPpropertystring>
 For example, if you were checking for the "audiocapturemode" property on a host pool named 0301HP, you'd enter this cmdlet:
 
 ```powershell
-Get-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> | format-list Name, CustomRdpProperty
+Get-AzWvdHostPool -ResourceGroupName 0301rg -Name 0301hp | format-list Name, CustomRdpProperty
 
 Name              : 0301HP
 CustomRdpProperty : audiocapturemode:i:1;
@@ -102,7 +100,7 @@ CustomRdpProperty : <customRDPpropertystring>
 Based on our earlier cmdlet example, if you set up multiple RDP properties on the 0301HP host pool, your cmdlet would look like this:
 
 ```powershell
-Get-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> | format-list Name, CustomRdpProperty 
+Get-AzWvdHostPool -ResourceGroupName 0301rg -Name 0301hp | format-list Name, CustomRdpProperty 
 
 Name              : 0301HP 
 CustomRdpProperty : audiocapturemode:i:1;audiomode:i:0;

articles/virtual-desktop/media/all-applications-search.png

@@ -44,7 +44,7 @@ After you publish an app, it will have the default Windows app icon instead of i
 The process you use to publish Microsoft Edge is a little different from the publishing process for other apps. To publish Microsoft Edge with the default homepage, run this cmdlet:
 
 ```powershell
-New-AzWvdApplication -Name <applicationname> -ResourceGroupName <resourcegroupname> -ApplicationGroupName <appgroupname> -FilePath "shell:Appsfolder\Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge" -CommandLineSetting <Allow|Require|DoNotAllow> -IconIndex 0 -IconPath "shell:Appsfolder\Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge" -ShowInPortal:$true 
+New-AzWvdApplication -Name -ResourceGroupName -ApplicationGroupName -FilePath "shell:Appsfolder\Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge" -CommandLineSetting <Allow|Require|DoNotAllow> -iconPath "C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\microsoftedge.exe" -iconIndex 0 -ShowInPortal:$true 
 ```
 
 ## Next steps