PoliCheck updates

Author: damabe

docs/machine-learning/r/how-to-create-mdx-queries-using-olapr.md

@@ -88,7 +88,7 @@ WHERE [Sales Territory].[Sales Territory Country].[Australia]
 
 + On columns, you can specify multiple measures as elements of a comma-separated string.
 + The Row axis uses all possible values (all MEMBERS) of the "Product Line" dimension. 
-+ This query would return a table with three columns, containing a _rollup_ summary of Internet sales from all countries.
++ This query would return a table with three columns, containing a _rollup_ summary of Internet sales from all countries/regions.
 + The WHERE clause specifies the _slicer axis_. In this example, the slicer uses a member of the **SalesTerritory** dimension to filter the query so that only the sales from Australia are used in calculations.
 
 #### To build this query using the functions provided in olapR

docs/master-data-services/models-master-data-services.md

@@ -62,7 +62,7 @@ ms.author: jiwang6
 
 -   Customer, which could include entities such as gender, education, occupation, and marital status.  
 
--   Geography, which could include entities such as postal codes, cities, counties, states, provinces, regions, territories, countries, and continents.  
+-   Geography, which could include entities such as postal codes, cities, counties, states, provinces, territories, countries/regions, and continents.  
 
 ## Related Tasks  
 

docs/mdx/ancestor-mdx.md

@@ -73,7 +73,7 @@ SELECT {[Measures].[Internet Sales Amount], Measures.x} ON 0,
 FROM [Adventure Works]  
 ```  
 
- The following example uses a numeric expression and returns the Internet Sales Amount for each State-Province in Australia and its percent of the total Internet Sales Amount for all countries.  
+ The following example uses a numeric expression and returns the Internet Sales Amount for each State-Province in Australia and its percent of the total Internet Sales Amount for all countries/regions.  
 
 ```  
 WITH MEMBER Measures.x AS [Measures].[Internet Sales Amount] /   

docs/mdx/mdx-data-definition-create-session-cube.md

@@ -151,7 +151,7 @@ CREATE SESSION CUBE session_cube_name FROM <cube list> (<param list>)
 -   When performing grouping on a cube dimension in a server cube, the grouping affects all cube dimensions based on the same dimension.  
 
 ## Example  
- The following example demonstrates creating a session-scoped version of the Adventure Works cube that contains the Reseller Sales Amount measure, the Reseller dimension, the Product dimension, the Geography dimension, and the Date dimension. Within this session cube, two groups are created; one group contains countries in Europe and one group contains groups in North America. This sample is a simplified version of a CREATE SESSION CUBE statement issued by Microsoft Excel when a user creates a custom grouping of members.  
+ The following example demonstrates creating a session-scoped version of the Adventure Works cube that contains the Reseller Sales Amount measure, the Reseller dimension, the Product dimension, the Geography dimension, and the Date dimension. Within this session cube, two groups are created; one group contains countries/regions in Europe and one group contains groups in North America. This sample is a simplified version of a CREATE SESSION CUBE statement issued by Microsoft Excel when a user creates a custom grouping of members.  
 
 ```  
 CREATE SESSION CUBE [Adventure Works_XL_GROUPING1]   

docs/mdx/mdx-data-manipulation-drillthrough.md

@@ -73,7 +73,7 @@ DRILLTHROUGH[MAXROWSUnsigned_Integer]
  Returns the unary operator of the specified attribute member.  
 
 ## Example  
- The following example specifies cell for the month of July, 2007 for the reseller sales amount measure (the default measure) for the country of Australia. The RETURN clause specifies that the date of each sale, the product model name, the employee name, the sales amount, the tax amount and the product cost values that underlie this cell be returned.  
+ The following example specifies cell for the month of July, 2007 for the reseller sales amount measure (the default measure) for Australia. The RETURN clause specifies that the date of each sale, the product model name, the employee name, the sales amount, the tax amount and the product cost values that underlie this cell be returned.  
 
 ```  
 DRILLTHROUGH  

docs/mdx/mdx-data-manipulation-select.md

@@ -114,7 +114,7 @@ FROM
  Calculated members can be included in \<SELECT query axis clause> whenever the connection was opened using the connection string parameter *subqueries=1*; see [Supported XMLA Properties &#40;XMLA&#41;](/analysis-services/xmla/xml-elements-properties/propertylist-element-supported-xmla-properties) and <xref:Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectionString%2A> for parameter usage. An example is provided on calculated members in subselects.  
 
 ## Autoexists  
- When two or more attributes of the dimension are used in a SELECT statement, Analysis Services evaluates the attributes' expressions to make sure that the members of those attributes are properly confined to meet the criteria of all other attributes. For example, suppose you are working with attributes from the Geography dimension. If you have one expression that returns all members from the City attribute, and another expression that confines members from the Country attribute to all countries in Europe, then this will result in the City members being confined to only those cities that belong to countries in Europe. This characteristic of Analysis Services is called Autoexists and applies only to attributes in the same dimension. Autoexists only applies to attributes from the same dimension because it tries to prevent the dimension records excluded in one attribute expression from being included by the other attribute expressions. Autoexists can also be understood as the resulting intersection of the different attributes expressions over the dimension records. See the following examples below:  
+ When two or more attributes of the dimension are used in a SELECT statement, Analysis Services evaluates the attributes' expressions to make sure that the members of those attributes are properly confined to meet the criteria of all other attributes. For example, suppose you are working with attributes from the Geography dimension. If you have one expression that returns all members from the City attribute, and another expression that confines members from the Country attribute to all countries/regions in Europe, then this will result in the City members being confined to only those cities that belong to countries/regions in Europe. This characteristic of Analysis Services is called Autoexists and applies only to attributes in the same dimension. Autoexists only applies to attributes from the same dimension because it tries to prevent the dimension records excluded in one attribute expression from being included by the other attribute expressions. Autoexists can also be understood as the resulting intersection of the different attributes expressions over the dimension records. See the following examples below:  
 
  `//Obtain the Top 10 best reseller selling products by Name`  
 

docs/mdx/strtoset-mdx.md

@@ -54,7 +54,7 @@ FROM [Adventure Works]
   
 ```  
 
- The following example returns the Reseller Sales Amount measure for the countries of Germany and Canada. The set specification provided in the specified string contains qualified member names, as required by the CONSTRAINED flag.  
+ The following example returns the Reseller Sales Amount measure for Germany and Canada. The set specification provided in the specified string contains qualified member names, as required by the CONSTRAINED flag.  
 
 ```  
 SELECT StrToSet ('{[Geography].[Geography].[Country].[Germany],[Geography].[Geography].[Country].[Canada]}', CONSTRAINED)  

docs/reporting-services/report-design/troubleshoot-reports-map-reports-report-builder-and-ssrs.md

@@ -112,7 +112,7 @@ ms.author: maggies
  To reload the spatial data and use the map view center saved in the report, right-click the map viewport, and then click **Reload**. After you enter the credentials for the spatial data source, the layer loads the spatial data and the map view is restored.  
 
 ## The center and view for a map layer option does not work.  
- When the viewport is set to center on the spatial data for a specific layer, and the center of the view does not appear to be the center for the layer, there are probably small islands or areas that are included in the spatial data that are too small to be seen in the viewport. For example, spatial data for a country might include small islands or other small territories as part of the territory. The viewport uses all spatial data to calculate the center for the layer.  
+ When the viewport is set to center on the spatial data for a specific layer, and the center of the view does not appear to be the center for the layer, there are probably small islands or areas that are included in the spatial data that are too small to be seen in the viewport. For example, spatial data for a country/region might include small islands or other small territories as part of the territory. The viewport uses all spatial data to calculate the center for the layer.  
 
  To override calculations for the layer, you can do one of the following:  
 

docs/samples/wide-world-importers-oltp-database-catalog.md

@@ -65,7 +65,7 @@ Details of parameters and people (users and contacts), along with common referen
 |People|Contains user names, contact information, for all who use the application, and for the people that the Wide World Importers deals with at customer organizations. This table includes staff, customers, suppliers, and any other contacts. For people who have been granted permission to use the system or website, the information includes login details.|
 |Cities|There are many addresses stored in the system, for people, customer organization delivery addresses, pickup addresses at suppliers, etc. Whenever an address is stored, there is a reference to a city in this table. There is also a spatial location for each city.|
 |StateProvinces|Cities are part of states or provinces. This table has details of those, including spatial data describing the boundaries each state or province.|
-|Countries|States or Provinces are part of countries/regions. This table has details of those, including spatial data describing the boundaries of each country.|
+|Countries|States or Provinces are part of countries/regions. This table has details of those, including spatial data describing the boundaries of each country/region.|
 |DeliveryMethods|Choices for delivering stock items (for example, truck/van, post, pickup, courier, etc.)|
 |PaymentMethods|Choices for making payments (for example, cash, check, EFT, etc.)|
 |TransactionTypes|Types of customer, supplier, or stock transactions (for example, invoice, credit note, etc.)|