Fixing blocking issues

Author: dknappettmsft

articles/virtual-desktop/client-device-redirection-intune.md

@@ -29,17 +29,17 @@ These features enable you to achieve the following scenarios:
 If the redirection settings on a client device conflict with the host pool RDP properties and session host for Azure Virtual Desktop, or Cloud PC for Windows 365, the more restrictive setting between the two takes effect. For example, if the session host disallows drive redirection and the client device allowing drive redirection, drive redirection is disallowed. If the redirection settings on session host and client device are both the same, the redirection behavior is consistent.
 
 > [!IMPORTANT]
-> Configuring redirection settings on a client device isn't a substitute for correctly configuring your host pools and session hosts based on your requirements. Using Microsoft Intune to configure Windows App and the Remote Desktop app might not be suitable workloads requiring a higher level of security. 
+> Configuring redirection settings on a client device isn't a substitute for correctly configuring your host pools and session hosts based on your requirements. Using Microsoft Intune to configure Windows App and the Remote Desktop app might not be suitable for workloads requiring a higher level of security. 
 > 
 > Workloads with higher security requirements should continue to set redirection at the host pool or session host, where all users of the host pool would have the same redirection configuration. A Data Loss Protection (DLP) solution is recommended and redirection should be disabled on session hosts whenever possible to minimize the opportunities for data loss. 
 
 At a high-level, there are three areas to configure:
 
-1. **Intune app configuration policies**: used to manage redirection settings for Windows App and the Remote Desktop app on a client device. There are two types of app configuration policies; a managed apps policy is used to manage settings for an application, whether the client device is enrolled or unenrolled, and a managed devices policy is used in addition to manage settings on an enrolled device. Use filters to target users based on specific criteria.
+- **Intune app configuration policies**: used to manage redirection settings for Windows App and the Remote Desktop app on a client device. There are two types of app configuration policies; a managed apps policy is used to manage settings for an application, whether the client device is enrolled or unenrolled, and a managed devices policy is used in addition to manage settings on an enrolled device. Use filters to target users based on specific criteria.
 
-1. **Intune app protection policies**: used to specify security requirements that must be met by the application and the client device. Use filters to target users based on specific criteria.
+- **Intune app protection policies**: used to specify security requirements that must be met by the application and the client device. Use filters to target users based on specific criteria.
 
-1. **Conditional Access policies**: used to control access to Azure Virtual Desktop and Windows 365 based only if the criteria set in app configuration policies and app protection policies are met.
+- **Conditional Access policies**: used to control access to Azure Virtual Desktop and Windows 365 based only if the criteria set in app configuration policies and app protection policies are met.
 
 ## Supported platforms and enrollment types
 

articles/virtual-desktop/compare-remote-desktop-clients.md

@@ -27,7 +27,7 @@ The following table compares the features of each Remote Desktop client when con
 | Dynamic resolution | X | X |  |  | X | X | Resolution and orientation of local monitors is dynamically reflected in the remote session. If the client is running in windowed mode, the remote desktop is resized dynamically to the size of the client window. |
 | Smart sizing | X | X |  |  | X |  | Remote Desktop in Windowed mode is dynamically scaled to the window's size. |
 | Localization | X | X | English only | X |  | X | Client user interface is available in multiple languages. |
-| Multi-factor authentication | X | X | X | X | X | X | Supports multi-factor authentication for remote connections. |
+| Multifactor authentication | X | X | X | X | X | X | Supports multifactor authentication for remote connections. |
 | Teams optimization for Azure Virtual Desktop | X |  |  |  | X |  | Media optimizations for Microsoft Teams to provide high quality calls and screen sharing experiences. Learn more at [Use Microsoft Teams on Azure Virtual Desktop](./teams-on-avd.md). |
 
 ## Redirections comparison

articles/virtual-desktop/includes/include-whats-new-client-ios-ipados.md

@@ -372,7 +372,7 @@ In this release, we made the following changes:
 - For external mice, the client now supports left-click, left-drag, right-click, right-drag, middle-click, and vertical scrolling.
 - The client now supports keyboard shortcuts that use Ctrl, Alt, or Shift keys with the mouse or trackpad, including multi-select and range-select.
 - The client now supports the "Tap-to-Click" feature for the trackpad.
-- We updated the Mouse Pointer mode's right-click gesture to press-and-hold (not press-and-hold-and-release). On the iPhone client we thrown in some taptic feedback when we detect the right-click gesture.
+- We updated the Mouse Pointer mode's right-click gesture to press-and-hold (not press-and-hold-and-release). On the iPhone client we added taptic feedback when we detect the right-click gesture.
 - Added an option to disable NLA enforcement under **iOS Settings** > **RD Client**.
 - Mapped Control+Shift+Escape to Ctrl+Shift+Esc, where Escape is generated using a remapped key on iPadOS or Command+.
 - Mapped Command+F to Ctrl+F.
@@ -465,7 +465,7 @@ In this release, we made the following changes:
 
 *Published: 12/20/19*
 
-We been working hard to fix bugs and add useful features. Here's what's new in this release:
+In this release, we made the following changes:
 
 - Support for Japanese and Chinese input on hardware keyboards.
 - The PC list view now shows the friendly name of the associated user account, if one exists.