Merging changes synced from https://github.com/MicrosoftDocs/windows-dev-docs-pr (branch live)

Author: Learn Build Service GitHub App

hub/apps/design/accessibility/accessibility-overview.md

@@ -82,7 +82,7 @@ UI controls use a visual representation that is defined as part of a XAML resour
 
 When you design your apps, consider how they may be used by people with limited mobility, vision, and hearing. Because assistive technology products make extensive use of standard UI, it is particularly important to provide good keyboard and screen-reader support even if you make no other adjustments for accessibility.
 
-In many cases, you can convey essential information by using multiple techniques to widen your audience. For example, you can highlight information using both icon and color information to help users who are color blind, and you can display visual alerts along with sound effects to help users who are hearing impaired.
+In many cases, you can convey essential information by using multiple techniques to widen your audience. For example, you can highlight information using both icon and color information to help users who are color blind, and you can display visual alerts along with sound effects to help users who are deaf or hard of hearing.
 
 If necessary, you can provide alternative, accessible user interface elements that completely remove nonessential elements and animations, and provide other simplifications to streamline the user experience. The following code example demonstrates how to display one [**UserControl**](/uwp/api/Windows.UI.Xaml.Controls.UserControl) instance in place of another depending on a user setting.
 

hub/apps/design/accessibility/system-button-narration.md

@@ -16,7 +16,7 @@ Screen-readers, such as [Narrator](https://support.microsoft.com/help/22798/wind
 Beginning with Windows 10 version 2004, UWP applications can listen for and handle the **Fn** hardware system button events in the same way as other hardware buttons. Previously, this system button acted only as a modifier for how other hardware buttons reported their events and state.
 
 > [!NOTE]
-> Fn button support is OEM-specific and can include features such as the ability to toggle/lock on or off (vs. a press-and-hold key combination), along with a corresponding lock indicator light (which might not helpful to blind or vision-impaired users).
+> Fn button support is OEM-specific and can include features such as the ability to toggle/lock on or off (vs. a press-and-hold key combination), along with a corresponding lock indicator light (which might not be helpful to users who are blind or have a vision impairment).
 
 Fn button events are exposed through a new [SystemButtonEventController Class](/uwp/api/windows.ui.input.systembuttoneventcontroller) in the [Windows.UI.Input](/uwp/api/windows.ui.input) namespace. The SystemButtonEventController object supports the following events:
 

hub/apps/design/globalizing/adjust-layout-and-fonts--and-support-rtl.md

@@ -13,7 +13,7 @@ ms.localizationpriority: medium
 Design your app to support the layouts and fonts of multiple languages, including RTL (right-to-left) flow direction. Flow direction is the direction in which script is written and displayed, and the UI elements on the page are scanned by the eye.
 
 ## Layout guidelines
-Languages such as German and Finnish typically use more characters than English does. Far Eastern fonts typically require more height. And languages such as Arabic and Hebrew require that layout panels and text elements be laid out in right-to-left (RTL) reading order.
+Languages such as German and Finnish typically use more characters than English does. East Asian fonts typically require more height. And languages such as Arabic and Hebrew require that layout panels and text elements be laid out in right-to-left (RTL) reading order.
 
 Because of these variations in the metrics of translated text, we recommend that you don't bake absolute positioning, fixed widths, or fixed heights into your user interface (UI). Instead, take advantage of the dynamic layout mechanisms that are built into the Windows UI elements. For example, content controls (such as buttons), items controls (such as grid views and list views), and layout panels (such as grids and stackpanels) automatically resize and reflow by default to fit their content. Pseudo-localize your app to uncover any problematic edge cases where your UI elements don't size to content properly.
 

hub/apps/design/style/segoe-fluent-icons-font.md

@@ -39,7 +39,7 @@ All glyphs in **Segoe Fluent Icons** have the same fixed width with a consistent
 </Grid>
 ```
 
-Many of the icons also have mirrored forms available for use in languages that use right-to-left text directionality such as Arabic, Farsi, and Hebrew.
+Many of the icons also have mirrored forms available for use in languages that use right-to-left text directionality such as Arabic, Dari, Persian, and Hebrew.
 
 ## Using the icons
 

hub/apps/design/style/segoe-ui-symbol-font.md

@@ -37,7 +37,7 @@ All glyphs in **Segoe MDL2 Assets** have the same fixed width with a consistent
 
 ![using a zero-width glyph](images/segoe-ui-symbol-layering.png)
 
-Many of the icons also have mirrored forms available for use in languages that use right-to-left text directionality such as Arabic, Farsi, and Hebrew.
+Many of the icons also have mirrored forms available for use in languages that use right-to-left text directionality such as Arabic, Dari, Persian, and Hebrew.
 
 ## Using the icons
 If you are developing an app in C#/VB/C++ and XAML, you can use specified glyphs from Segoe MDL2 Assets with the [Symbol enumeration](/uwp/api/windows.ui.xaml.controls.symbol).