Merge pull request #5278 from damabe/vdamabe-policheck1

Policheck Update - Mar 20 | Bulk Update

Author: GrantMeStrength

hub/apps/design/accessibility/designing-inclusive-software.md

@@ -94,7 +94,7 @@ In summary, follow these seven steps to ensure your software is inclusive.
 3.	Design a logical hierarchy for your product, noting where the standard controls, any custom controls, and keyboard focus are in the UI.  
 4.	Design useful system settings (such as keyboard navigation, high contrast, and high dpi) into your product.  
 5.	Implement your design, using the [Microsoft accessibility developer hub](https://developer.microsoft.com/windows/accessible-apps) and your framework’s accessibility specification as a reference point.  
-6.	Test your product with users who have special needs to ensure they will be able to take advantage of the inclusive design techniques implemented in it.  
+6.	Test your product with users who have functional needs to ensure they will be able to take advantage of the inclusive design techniques implemented in it.  
 7.	Deliver your finished product and document your implementation for those who may work on the project after you.  
 
 ## Related topics  

hub/apps/design/controls/forms.md

@@ -121,7 +121,7 @@ Control | Use | Example
 ### Lists
 Control | Use | Example
 - | - | -
-[ComboBox](combo-box.md) | Start in compact state and expand to show list of selectable items | Select from a long list of items, such as states or countries
+[ComboBox](combo-box.md) | Start in compact state and expand to show list of selectable items | Select from a long list of items, such as states or countries/regions
 [ListView](./lists.md#list-view) | Categorize items and assign group headers, drag and drop items, curate content, and reorder items | Rank options
 [GridView](./lists.md#grid-view) | Arrange and browse image-based collections | Pick a photo, color, display theme
 

hub/apps/design/globalizing/guidelines-and-checklist-for-globalizing-your-app.md

@@ -20,7 +20,7 @@ Design and develop your app in such a way that it functions appropriately on sys
 | Appropriately format numbers, dates, times, addresses, and phone numbers. | These formats vary between cultures, regions, languages, and markets. If you're displaying these data then use [**Globalization**](/uwp/api/Windows.Globalization?branch=live) APIs to get the format appropriate for a particular audience. See [Globalize your date/time/number formats](use-global-ready-formats.md). The order in which family and given names are displayed, and the format of addresses, can differ as well. Use standard date, time, and number displays. Use standard date and time picker controls. Use standard address information. |
 | Support international units of measurement and currency. | Different units and scales are used in different countries, although the most popular are the metric system and the imperial system. Be sure to support the correct system measurement if you deal with measurements such as length, temperature, and area. Use the [**GeographicRegion.CurrenciesInUse**](/uwp/api/windows.globalization.geographicregion.CurrenciesInUse) property to get the set of currencies in use in a region. |
 | Use Unicode for character encoding. | By default, Microsoft Visual Studio uses Unicode character encoding for all documents. If you're using a different editor, be sure to save source files in the appropriate Unicode character encodings. All Windows Runtime APIs return UTF-16 encoded strings. |
-| Support international paper sizes. | The most common paper sizes differ between countries, so if you include features that depend on paper size, such as printing, be sure to support and test common international sizes. |
+| Support international paper sizes. | The most common paper sizes differ between countries/regions, so if you include features that depend on paper size, such as printing, be sure to support and test common international sizes. |
 | Record the language of the keyboard or IME. | When your app asks the user for text input, record the language tag for the currently enabled keyboard layout or Input Method Editor (IME). This ensures that when the input is displayed later it's presented to the user with the appropriate formatting. Use the [**Language.CurrentInputMethodLanguageTag**](/uwp/api/windows.globalization.language.CurrentInputMethodLanguageTag) property to get the current input language. |
 | Don't use language to assume a user's region; and don't use region to assume a user's language. | Language and region are separate concepts. A user can speak a particular regional variant of a language, like en-GB for English as spoken in the UK, but the user might be in an entirely different country or region. Consider whether your app requires knowledge about the user's language (for UI text, for example), or region (for licensing, for example). For more info, see [Understand user profile languages and app manifest languages](manage-language-and-region.md). |
 | The rules for comparing language tags are non-trivial. | [BCP-47 language tags](https://tools.ietf.org/html/bcp47) are complex. There are a number of issues when comparing language tags, including issues with matching script information, legacy tags, and multiple regional variants. The Resource Management System in Windows takes care of matching for you. You can specify a set of resources in any languages, and the system chooses the appropriate one for the user and the app. See [App resources and the Resource Management System](/windows/uwp/app-resources/index) and [How the Resource Management System matches language tags](/windows/uwp/app-resources/how-rms-matches-lang-tags). |

hub/apps/design/globalizing/use-global-ready-formats.md

@@ -108,7 +108,7 @@ To ensure that the preferred calendar format is used, you can use the standard [
 
 ## Format phone numbers appropriately
 
-Phone numbers are formatted differently across regions. The number of digits, how the digits are grouped, and the significance of certain parts of the phone number vary between countries. Starting in Windows 10, version 1607, you can use classes in the [**PhoneNumberFormatting**](/uwp/api/windows.globalization.phonenumberformatting?branch=live) namespace to format phone numbers appropriately for the current region.
+Phone numbers are formatted differently across regions. The number of digits, how the digits are grouped, and the significance of certain parts of the phone number vary between countries/regions. Starting in Windows 10, version 1607, you can use classes in the [**PhoneNumberFormatting**](/uwp/api/windows.globalization.phonenumberformatting?branch=live) namespace to format phone numbers appropriately for the current region.
 
 [**PhoneNumberInfo**](/uwp/api/windows.globalization.phonenumberformatting.phonenumberinfo?branch=live) parses a string of digits and allows you to: determine whether the digits are a valid phone number in the current region; compare two numbers for equality; and to extract the different functional parts of the phone number, such as country code or geographical area code.
 

hub/apps/design/input/guidelines-for-optical-zoom.md

@@ -42,7 +42,7 @@ Optical zoom shouldn't be confused with [Semantic Zoom](../controls/semantic-zoo
 Use the following guidelines for apps that support either resizing or optical zooming:
 
 -   If maximum and minimum size constraints or boundaries are defined, use visual feedback to demonstrate when the user reaches or exceeds those boundaries.
--   Use snap points to influence zooming and resizing behavior by providing logical points at which to stop the manipulation and ensure a specific subset of content is displayed in the viewport. Provide snap points for common zoom levels or logical views to make it easier for a user to select those levels. For example, photo apps might provide a resizing snap point at 100% or, in the case of mapping apps, snap points might be useful at city, state, and country views.
+-   Use snap points to influence zooming and resizing behavior by providing logical points at which to stop the manipulation and ensure a specific subset of content is displayed in the viewport. Provide snap points for common zoom levels or logical views to make it easier for a user to select those levels. For example, photo apps might provide a resizing snap point at 100% or, in the case of mapping apps, snap points might be useful at city, state, and country/region views.
 
     Snap points enable users to be imprecise and still achieve their goals. If you're using XAML, see the snap points properties of [**ScrollViewer**](/uwp/api/Windows.UI.Xaml.Controls.ScrollViewer).
 

hub/apps/publish/analyze-msi-exe/ratings-reviews-performance.md

@@ -21,7 +21,7 @@ The total count of ratings and rating score are specific to a user’s country a
 
 ## Analyzing ratings and reviews
 
-Analyze ratings and reviews with the Ratings and reviews report in Partner Center. This helps developers monitor the performance of their products over time. For more details, developers can also analyze ratings and reviews by country, device type, OS, and more.
+Analyze ratings and reviews with the Ratings and reviews report in Partner Center. This helps developers monitor the performance of their products over time. For more details, developers can also analyze ratings and reviews by country/region, device type, OS, and more.
 
 ## Ratings and reviews report
 

hub/apps/publish/publish-your-app/add-on/schedule-pricing-changes.md

@@ -21,7 +21,7 @@ The **Pricing** section of the [Pricing and availability](./price-and-availabili
 
 When you select your app's **Base price**, that price will be used in every market where your app is sold, unless you override the base price in any market(s).
 
-You can set the **Base price** to **Free**, or you can choose an available price tier, which sets the price in all the countries where you choose to distribute your app. Price tiers start at 0.99 USD, with additional tiers available at increasing increments (1.09 USD, 1.19 USD, and so on). The increments generally increase as the price gets higher.
+You can set the **Base price** to **Free**, or you can choose an available price tier, which sets the price in all the countries/regions where you choose to distribute your app. Price tiers start at 0.99 USD, with additional tiers available at increasing increments (1.09 USD, 1.19 USD, and so on). The increments generally increase as the price gets higher.
 
 > [!NOTE]
 > These price tiers also apply to add-ons.
@@ -258,7 +258,7 @@ Below is a table that shows what specific time zones are used in each market, so
 | Kiribati                                     | (UTC+14:00) Kiritimati Island                                 |
 | Korea                                        | (UTC+09:00) Seoul                                             |
 | Kuwait                                       | (UTC+04:00) Abu Dhabi, Muscat                                 |
-| Kyrgyzstan                                   | (UTC+06:00) Nur-Sultan                                        |
+| Kyrgyzstan                                   | (UTC+06:00) Astana                                         |
 | Laos                                         | (UTC+07:00) Bangkok, Hanoi, Jakarta                           |
 | Latvia                                       | (UTC+02:00) Chisinau                                          |
 | Lesotho                                      | (UTC+02:00) Harare, Pretoria                                  |

hub/apps/publish/publish-your-app/msix/schedule-pricing-changes.md

@@ -18,7 +18,7 @@ The **Pricing** section of the [Pricing and availability](./price-and-availabili
 
 When you select your app's **Base price**, that price will be used in every market where your app is sold, unless you override the base price in any market(s).
 
-You can set the **Base price** to **Free**, or you can choose an available price tier, which sets the price in all the countries where you choose to distribute your app. Price tiers start at 0.99 USD, with additional tiers available at increasing increments (1.09 USD, 1.19 USD, and so on). The increments generally increase as the price gets higher.
+You can set the **Base price** to **Free**, or you can choose an available price tier, which sets the price in all the countries/regions where you choose to distribute your app. Price tiers start at 0.99 USD, with additional tiers available at increasing increments (1.09 USD, 1.19 USD, and so on). The increments generally increase as the price gets higher.
 
 > [!NOTE]
 > These price tiers also apply to add-ons.
@@ -256,7 +256,7 @@ Below is a table that shows what specific time zones are used in each market, so
 | Kiribati                                     | (UTC+14:00) Kiritimati Island                                 |
 | Korea                                        | (UTC+09:00) Seoul                                             |
 | Kuwait                                       | (UTC+04:00) Abu Dhabi, Muscat                                 |
-| Kyrgyzstan                                   | (UTC+06:00) Nur-Sultan                                        |
+| Kyrgyzstan                                   | (UTC+06:00) Astana                                         |
 | Laos                                         | (UTC+07:00) Bangkok, Hanoi, Jakarta                           |
 | Latvia                                       | (UTC+02:00) Chisinau                                          |
 | Lesotho                                      | (UTC+02:00) Harare, Pretoria                                  |

hub/apps/publish/publish-your-app/pwa/schedule-pricing-changes.md

@@ -18,7 +18,7 @@ The **Pricing** section of the [Pricing and availability](./price-and-availabili
 
 When you select your app's **Base price**, that price will be used in every market where your app is sold, unless you override the base price in any market(s).
 
-You can set the **Base price** to **Free**, or you can choose an available price tier, which sets the price in all the countries where you choose to distribute your app. Price tiers start at 0.99 USD, with additional tiers available at increasing increments (1.09 USD, 1.19 USD, and so on). The increments generally increase as the price gets higher.
+You can set the **Base price** to **Free**, or you can choose an available price tier, which sets the price in all the countries/regions where you choose to distribute your app. Price tiers start at 0.99 USD, with additional tiers available at increasing increments (1.09 USD, 1.19 USD, and so on). The increments generally increase as the price gets higher.
 
 > [!NOTE]
 > These price tiers also apply to add-ons.

uwp/gaming/monetization-for-games.md

@@ -33,7 +33,7 @@ Here are some important concepts regarding the pricing of your game in the Store
 ### Base price
 
 The base price of the game is what determines whether your game is categorized as _paid_ or _free_. You can use [Partner Center](https://partner.microsoft.com/dashboard) to configure the base price based on country and region.
-The process of determining the price may include your [tax responsibilities when selling to different countries](/partner-center/tax-details-marketplace)
+The process of determining the price may include your [tax responsibilities when selling to different countries/regions](/partner-center/tax-details-marketplace)
 and [cost considerations for specific markets](/windows/apps/publish/publish-your-app/market-selection?pivots=store-installer-msix). You can also [set custom prices for specific markets](/windows/apps/publish/publish-your-app/schedule-pricing-changes?pivots=store-installer-msix#override-base-price-for-specific-markets).
 
 ### Sale price