Add "region(s)" to "country" and "countries"

Author: garycentric

docs/ado/reference/ado-api/filter-and-recordcount-properties-example-vb.md

@@ -99,7 +99,7 @@ End Sub
 ```  
 
 > [!NOTE]
->  When you know the data you want to select, it's usually more efficient to open a **Recordset** with an SQL statement. This example shows how you can create just one **Recordset** and obtain records from a particular country.  
+>  When you know the data you want to select, it's usually more efficient to open a **Recordset** with an SQL statement. This example shows how you can create just one **Recordset** and obtain records from a particular country/region.  
   
 ```  
 Attribute VB_Name = "Filter"  

docs/data-quality-services/using-the-dqs-default-knowledge-base.md

@@ -18,7 +18,7 @@ ms.topic: conceptual
 
 -   **Country/Region (three-letter leading)**: Contains the conventional long (official name as designated by the country/region) and short names (common name used in lists, on maps, and so on), two-letter abbreviation, three-letter abbreviation and three-digit code for each location.  Leading values is set to County three-letter abbreviation.  
 
--   **Country/Region (two-letter leading)**: Contains the conventional long (official name as designated by the country/region ) and short names (common name used in lists, on maps, etc. ), two-letter abbreviation, three-letter abbreviation and three-digit code for each location.  Leading value is set to the Country two-letter abbreviation.  
+-   **Country/Region (two-letter leading)**: Contains the conventional long (official name as designated by the country/region ) and short names (common name used in lists, on maps, etc. ), two-letter abbreviation, three-letter abbreviation and three-digit code for each location.  Leading value is set to the country/region two-letter abbreviation.  
 
 -   **US - Counties**: Contains a list of US counties.  
 

docs/machine-learning/r/ref-r-olapr.md

@@ -105,7 +105,7 @@ FROM [Analysis Services Tutorial]
 WHERE [Sales Territory].[Sales Territory Country].[Australia]
 ```
 
-Using an AdventureWorks OLAP cube from the [multidimensional cube tutorial](/analysis-services/multidimensional-tutorial/multidimensional-modeling-adventure-works-tutorial), this MDX query selects the internet sales count and sales amount and places them on the Column axis. On the Row axis it places all possible values of the "Product Line" dimension. Then, using the WHERE clause (which is the slicer axis in MDX queries), it filters the query so that only the sales from Australia matter. Without the slicer axis, we would roll up and summarize the sales from all countries.
+Using an AdventureWorks OLAP cube from the [multidimensional cube tutorial](/analysis-services/multidimensional-tutorial/multidimensional-modeling-adventure-works-tutorial), this MDX query selects the internet sales count and sales amount and places them on the Column axis. On the Row axis it places all possible values of the "Product Line" dimension. Then, using the WHERE clause (which is the slicer axis in MDX queries), it filters the query so that only the sales from Australia matter. Without the slicer axis, we would roll up and summarize the sales from all countries/regions.
 
  ## olapR examples
 

docs/master-data-services/recursive-hierarchies-master-data-services.md

@@ -42,7 +42,7 @@ ms.author: jiwang6
 
 ## Rules  
 
--   A derived hierarchy cannot contain more than one recursive relationship. It can, however, have other derived relationships (for example, a derived hierarchy that contains a recursive Manager to Employee relationship can also have Country to Manager and Employee to Store relationships).  
+-   A derived hierarchy cannot contain more than one recursive relationship. It can, however, have other derived relationships (for example, a derived hierarchy that contains a recursive Manager to Employee relationship can also have Country/Region to Manager and Employee to Store relationships).  
 
 -   You cannot assign member permissions (on the **Hierarchy Members** tab) to members in a recursive hierarchy.  
 

docs/mdx/max-mdx.md

@@ -36,7 +36,7 @@ Max( Set_Expression [ , Numeric_Expression ] )
 >  [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)] ignores nulls when calculating the maximum value in a set of numbers.  
   
 ## Example  
- The following example returns the maximum monthly sales for each quarter, subcategory, and country in the Adventure Works cube.  
+ The following example returns the maximum monthly sales for each quarter, subcategory, and country/region in the Adventure Works cube.  
 
 ```  
 WITH MEMBER Measures.x AS Max   

docs/odbc/reference/appendixes/converting-data-from-c-to-sql-data-types.md

@@ -27,7 +27,7 @@ When an application calls **SQLExecute** or **SQLExecDirect**, the driver retrie
 
  The following table shows the supported conversions from ODBC C data types to ODBC SQL data types. A filled circle indicates the default conversion for an SQL data type (the C data type from which the data will be converted when the value of *ValueType* or the SQL_DESC_CONCISE_TYPE descriptor field is SQL_C_DEFAULT). A hollow circle indicates a supported conversion.  
 
- The format of the converted data is not affected by the Windows® country setting.  
+ The format of the converted data is not affected by the Windows® country or region setting.  
 
  ![Supported conversions: ODBC C to SQL data types](../../../odbc/reference/appendixes/media/apd1b.gif "apd1b")  
 

docs/odbc/reference/appendixes/converting-data-from-sql-to-c-data-types.md

@@ -29,7 +29,7 @@ When an application calls **SQLFetch**, **SQLFetchScroll**, or **SQLGetData**, t
 
  For an ODBC *3.x* application working with an ODBC *2.x* driver, conversion from driver-specific data types might not be supported.  
 
- The format of the converted data is not affected by the Windows® country setting.  
+ The format of the converted data is not affected by the Windows® country/region setting.  
 
  The tables in the following sections describe how the driver or data source converts data retrieved from the data source; drivers are required to support conversions to all ODBC C data types from the ODBC SQL data types that they support. For a given ODBC SQL data type, the first column of the table lists the legal input values of the *TargetType* argument in **SQLBindCol** and **SQLGetData**. The second column lists the outcomes of a test, often using the *BufferLength* argument specified in **SQLBindCol** or **SQLGetData**, which the driver performs to determine whether it can convert the data. For each outcome, the third and fourth columns list the values placed in the buffers specified by the *TargetValuePtr* and *StrLen_or_IndPtr* arguments specified in **SQLBindCol** or **SQLGetData** after the driver has attempted to convert the data. (The *StrLen_or_IndPtr* argument corresponds to the SQL_DESC_OCTET_LENGTH_PTR field of the ARD.) The last column lists the SQLSTATE returned for each outcome by **SQLFetch**, **SQLFetchScroll**, or **SQLGetData**.  
 

docs/odbc/reference/appendixes/sql-to-c-date.md

@@ -37,4 +37,4 @@ The identifier for the date ODBC SQL data type is:
 
  [c]   This is the size of the corresponding C data type.  
 
- When date SQL data is converted to character C data, the resulting string is in the "*yyyy*-*mm*-*dd*" format. This format is not affected by the Windows® country setting.
+ When date SQL data is converted to character C data, the resulting string is in the "*yyyy*-*mm*-*dd*" format. This format is not affected by the Windows® country/region setting.

docs/odbc/reference/appendixes/sql-to-c-time.md

@@ -39,4 +39,4 @@ The identifier for the time ODBC SQL data type is:
 
  [d]   This is the size of the corresponding C data type.  
 
- When time SQL data is converted to character C data, the resulting string is in the "*hh*:*mm*:*ss*" format. This format is not affected by the Windows® country setting.
+ When time SQL data is converted to character C data, the resulting string is in the "*hh*:*mm*:*ss*" format. This format is not affected by the Windows® country/region setting.

docs/relational-databases/hierarchical-data-sql-server.md

@@ -244,7 +244,7 @@ Converted Level  Level     Location         LocationType
 /3/1/            0x7AC0    McMurdo Station  City  
 ```  
   
- Notice that the hierarchy has a valid structure, even though it isn't internally consistent. Bahia is the only state. It appears in the hierarchy as a peer of the city Brasilia. Similarly, McMurdo Station does not have a parent country. Users must decide if this type of hierarchy is appropriate for their use.  
+ Notice that the hierarchy has a valid structure, even though it isn't internally consistent. Bahia is the only state. It appears in the hierarchy as a peer of the city Brasilia. Similarly, McMurdo Station does not have a parent country or region. Users must decide if this type of hierarchy is appropriate for their use.  
   
  Add another row and select the results.