remove en-us in links

Author: Saisang

docs/advanced-analytics/r/data-exploration-and-predictive-modeling-with-r.md

@@ -84,7 +84,7 @@ When using the RevoScaleR package to connect to [!INCLUDE[ssNoVersion](../../inc
 For examples of how to create and work with data sources and execution contexts,  see these tutorials:
 
 + [Data Science Deep Dive](../../advanced-analytics/tutorials/deepdive-data-science-deep-dive-using-the-revoscaler-packages.md)  
-+  [Data Analysis using Microsoft R](https://msdn.microsoft.com/en-us/microsoft-r/data-analysis-in-microsoft-r)
++  [Data Analysis using Microsoft R](https://msdn.microsoft.com/microsoft-r/data-analysis-in-microsoft-r)
 
 ## Deploy R Code to Production
 

docs/advanced-analytics/tutorials/walkthrough-deploy-and-use-the-model.md

@@ -184,7 +184,7 @@ The stored procedure *PredictTipSingleMode* demonstrates this approach. It takes
     ```
 
     >[!TIP]
-    > R Tools for Visual Studio (RTVS) provides great integration with both SQL Server and R. See this article for more examples of using RODBC with a SQL Server connection: [Working with SQL Server and R](https://docs.microsoft.com/en-us/visualstudio/rtvs/sql-server)
+    > R Tools for Visual Studio (RTVS) provides great integration with both SQL Server and R. See this article for more examples of using RODBC with a SQL Server connection: [Working with SQL Server and R](https://docs.microsoft.com/visualstudio/rtvs/sql-server)
 
 ## Summary
 

docs/analysis-services/data-mining/data-mining-concepts.md

@@ -148,7 +148,7 @@ manager: kfile
 
 -   Embed data mining functionality directly into an application. You can include Analysis Management Objects (AMO), which contains a set of objects that your application can use to create, alter, process, and delete mining structures and mining models. Alternatively, you can send XML for Analysis (XMLA) messages directly to an instance of [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)]. For more information, see [Development (Analysis Services - Data Mining)](https://technet.microsoft.com/library/bb522473\(v=sql.110\).aspx).  
 
--   Use [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] to create a package in which a mining model is used to intelligently separate incoming data into multiple tables. For example, if a database is continually updated with potential customers, you could use a mining model together with [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] to split the incoming data into customers who are likely to purchase a product and customers who are likely to not purchase a product. For more information, see [Typical Uses of Integration Services](http://msdn.microsoft.com/en-us/3b97897a-d418-4ef4-b5a4-5aabf4fa6bca).  
+-   Use [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] to create a package in which a mining model is used to intelligently separate incoming data into multiple tables. For example, if a database is continually updated with potential customers, you could use a mining model together with [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] to split the incoming data into customers who are likely to purchase a product and customers who are likely to not purchase a product. For more information, see [Typical Uses of Integration Services](http://msdn.microsoft.com/3b97897a-d418-4ef4-b5a4-5aabf4fa6bca).  
 
 -   Create a report that lets users directly query against an existing mining model. For more information, see [Reporting Services in SQL Server Data Tools (SSDT)](../../reporting-services/tools/reporting-services-in-sql-server-data-tools-ssdt.md).  
 

docs/analysis-services/power-pivot-sharepoint/create-and-configure-power-pivot-service-application-in-ca.md

@@ -100,9 +100,9 @@ manager: kfile
 
 9. In Data Refresh, in **Business Hours**, you can specify a range of hours that defines a business day. Data refresh schedules can run after the close of a business day to pick up transactional data that was generated during normal business hours.  
 
-10. In **[!INCLUDE[ssGemini](../../includes/ssgemini-md.md)] Unattended Data Refresh Account**, you can specify a predefined Secure Store Service target application that stores a predefined account for running [!INCLUDE[ssGemini](../../includes/ssgemini-md.md)] data refresh jobs. Be sure to specify the target application name, and not the ID. The target application for unattended data refresh is created automatically if you used the New Server option in SQL Server Setup to install [!INCLUDE[ssGemini](../../includes/ssgemini-md.md)] for SharePoint. Otherwise, you must create the target application manually. For instructions on how to configure the account, see [Configure the Power Pivot Unattended Data Refresh Account (Power Pivot for SharePoint)](http://msdn.microsoft.com/en-us/81401eac-c619-4fad-ad3e-599e7a6f8493).  
+10. In **[!INCLUDE[ssGemini](../../includes/ssgemini-md.md)] Unattended Data Refresh Account**, you can specify a predefined Secure Store Service target application that stores a predefined account for running [!INCLUDE[ssGemini](../../includes/ssgemini-md.md)] data refresh jobs. Be sure to specify the target application name, and not the ID. The target application for unattended data refresh is created automatically if you used the New Server option in SQL Server Setup to install [!INCLUDE[ssGemini](../../includes/ssgemini-md.md)] for SharePoint. Otherwise, you must create the target application manually. For instructions on how to configure the account, see [Configure the Power Pivot Unattended Data Refresh Account (Power Pivot for SharePoint)](http://msdn.microsoft.com/81401eac-c619-4fad-ad3e-599e7a6f8493).  
 
-11. In **Allow users to enter custom Windows credentials**, you can select or clear the checkbox to specify whether schedule owners can enter arbitrary Windows credentials to run a data refresh schedule. If you select this checkbox, [!INCLUDE[ssGemini](../../includes/ssgemini-md.md)] service application will create and manage a target application each set of stored credentials. For more information, see [Configure Stored Credentials for Power Pivot Data Refresh (Power Pivot for SharePoint)](http://msdn.microsoft.com/en-us/987eff0f-bcfe-4bbd-81e0-9aca993a2a75).  
+11. In **Allow users to enter custom Windows credentials**, you can select or clear the checkbox to specify whether schedule owners can enter arbitrary Windows credentials to run a data refresh schedule. If you select this checkbox, [!INCLUDE[ssGemini](../../includes/ssgemini-md.md)] service application will create and manage a target application each set of stored credentials. For more information, see [Configure Stored Credentials for Power Pivot Data Refresh (Power Pivot for SharePoint)](http://msdn.microsoft.com/987eff0f-bcfe-4bbd-81e0-9aca993a2a75).  
 
 12. In **Maximum Processing History Length**, you can specify how long to retain a historical record of data refresh processing. This information appears in data refresh history pages that are kept for each workbook that uses data refresh. It also appears in the [!INCLUDE[ssGemini](../../includes/ssgemini-md.md)] Management Dashboard.  
 

docs/analysis-services/power-pivot-sharepoint/deploy-power-pivot-solutions-to-sharepoint.md

@@ -42,7 +42,7 @@ Get-spwebapplication http://<top-level site name> | format-list UseClaimsAuthent
  The return value should be **false**. If it is **true**, you cannot access [!INCLUDE[ssGemini](../../includes/ssgemini-md.md)] data with this web application.  
 
 ##  <a name="bkmk_farm"></a> Step 1: Deploy the Farm Solution  
- This section shows you how to deploy solutions using PowerShell, but you can also use the [!INCLUDE[ssGemini](../../includes/ssgemini-md.md)] Configuration Tool to complete this task. For more information, see [Configure or Repair Power Pivot for SharePoint 2010 (Power Pivot Configuration Tool)](http://msdn.microsoft.com/en-us/d61f49c5-efaa-4455-98f2-8c293fa50046).  
+ This section shows you how to deploy solutions using PowerShell, but you can also use the [!INCLUDE[ssGemini](../../includes/ssgemini-md.md)] Configuration Tool to complete this task. For more information, see [Configure or Repair Power Pivot for SharePoint 2010 (Power Pivot Configuration Tool)](http://msdn.microsoft.com/d61f49c5-efaa-4455-98f2-8c293fa50046).  
 
  This task only needs to be performed once, after you install [!INCLUDE[ssGemini](../../includes/ssgemini-md.md)] for SharePoint.  
 
@@ -113,7 +113,7 @@ Get-spwebapplication http://<top-level site name> | format-list UseClaimsAuthent
   
 3.  Click **Retract Solution**.  
   
- If you encounter server deployment issues that you trace back to the farm solution, you can redeploy it by running the **Repair** option in the [!INCLUDE[ssGemini](../../includes/ssgemini-md.md)] Configuration Tool. Repair operations via the tool is preferred because it requires fewer steps on your part. For more information, see [Configure or Repair Power Pivot for SharePoint 2010 (Power Pivot Configuration Tool)](http://msdn.microsoft.com/en-us/d61f49c5-efaa-4455-98f2-8c293fa50046).  
+ If you encounter server deployment issues that you trace back to the farm solution, you can redeploy it by running the **Repair** option in the [!INCLUDE[ssGemini](../../includes/ssgemini-md.md)] Configuration Tool. Repair operations via the tool is preferred because it requires fewer steps on your part. For more information, see [Configure or Repair Power Pivot for SharePoint 2010 (Power Pivot Configuration Tool)](http://msdn.microsoft.com/d61f49c5-efaa-4455-98f2-8c293fa50046).  
   
  If you still want to re-deploy all solutions, be sure to do so in this order:  
   

docs/analysis-services/tabular-models-scripting-language-objects/datasources-object-tmsl.md

@@ -23,7 +23,7 @@ manager: kfile
  The type of DataSource. At present, the only valid value is Provider (1) - Normal connection string.  
 
  connectionString  
- The connection string that minimally specifies the server and database, but can also include other properties supported by the external RDBMS, such as a data provider or user account. This value is required. See [SqlConnectionStringBuilder Class](https://msdn.microsoft.com/en-us/library/ms254500\(v=vs.110\).aspx) for details about SQL Server database connection string properties.  
+ The connection string that minimally specifies the server and database, but can also include other properties supported by the external RDBMS, such as a data provider or user account. This value is required. See [SqlConnectionStringBuilder Class](https://msdn.microsoft.com/library/ms254500\(v=vs.110\).aspx) for details about SQL Server database connection string properties.  
 
  impersonationMode  
  Specifies whether Analysis Services should impersonate the identity of the user requesting the query. This property is a numeric value that specifies the credentials to use for impersonation. The enumeration values are as follows:  

docs/analysis-services/tabular-models/data-types-supported-ssas-tabular.md

@@ -53,7 +53,7 @@ When you import data or use a value in a formula, even if the original data sour
 >  You cannot import from a **varchar(max)** column that contains a string length of more than 131,072 characters.  
   
 ### Table data type  
- In addition, DAX uses a *table* data type. This data type is used by DAX in many functions, such as aggregations and time intelligence calculations. Some functions require a reference to a table; other functions return a table that can then be used as input to other functions. In some functions that require a table as input, you can specify an expression that evaluates to a table; for some functions, a reference to a base table is required. For information about the requirements of specific functions, see [DAX Function Reference](http://msdn.microsoft.com/en-us/4dbb28a1-dd1a-4fca-bcd5-e90f74864a7b).  
+ In addition, DAX uses a *table* data type. This data type is used by DAX in many functions, such as aggregations and time intelligence calculations. Some functions require a reference to a table; other functions return a table that can then be used as input to other functions. In some functions that require a table as input, you can specify an expression that evaluates to a table; for some functions, a reference to a base table is required. For information about the requirements of specific functions, see [DAX Function Reference](http://msdn.microsoft.com/4dbb28a1-dd1a-4fca-bcd5-e90f74864a7b).  
 
 ##  <a name="bkmk_implicit"></a> Implicit and explicit data type conversion in DAX Formulas
 
@@ -151,5 +151,5 @@ Only a limited set of mixed data-type combinations for comparison operations is
 |BLANK OR BLANK|BLANK|Error|  
 |BLANK AND BLANK|BLANK|Error|  
 
- For details on how a particular function or operator handles blanks, see the individual topics for each DAX function, in the section, [DAX Function Reference](http://msdn.microsoft.com/en-us/4dbb28a1-dd1a-4fca-bcd5-e90f74864a7b).  
+ For details on how a particular function or operator handles blanks, see the individual topics for each DAX function, in the section, [DAX Function Reference](http://msdn.microsoft.com/4dbb28a1-dd1a-4fca-bcd5-e90f74864a7b).  
 

docs/analysis-services/tabular-models/dax-formula-compatibility-in-directquery-mode-ssas-2016.md

@@ -39,7 +39,7 @@ These functions have not been optimized to work with DirectQuery. These function
 
 The reasons a particular function might not be optimized for DirectQuery is because the underlying relational engine cannot perform calculations equivalent to those performed by the xVelocity engine, or the formula cannot be converted to an equivalent SQL expression. In other cases, the performance of the converted expression and the resulting calculations may be unacceptable.
 
-To learn about all DAX functions, see the [DAX Function Reference].(https://msdn.microsoft.com/en-us/library/ee634396.aspx)
+To learn about all DAX functions, see the [DAX Function Reference].(https://msdn.microsoft.com/library/ee634396.aspx)
 
 ## DAX operators in DirectQuery mode
 All DAX comparison and arithmetic operators are fully supported in DirectQuery mode. To learn more, see [DAX Operator Reference](https://msdn.microsoft.com/library/ee634237.aspx).
@@ -111,7 +111,7 @@ In DirectQuery mode, casts from string representations of dates and times to act
 Models that use the in-memory data store support a more limited range of text formats for dates than the string formats for dates that are supported by SQL Server. However, DAX supports custom date and time formats.  
 
 **Cast from string to other non Boolean values**  
-When casting from strings to non-Boolean values, DirectQuery mode behaves the same as SQL Server. For more information, see [CAST and CONVERT (Transact-SQL)](http://msdn.microsoft.com/en-us/a87d0850-c670-4720-9ad5-6f5a22343ea8).  
+When casting from strings to non-Boolean values, DirectQuery mode behaves the same as SQL Server. For more information, see [CAST and CONVERT (Transact-SQL)](http://msdn.microsoft.com/a87d0850-c670-4720-9ad5-6f5a22343ea8).  
 
 **Cast from numbers to string not allowed**  
 EXAMPLE: `CONCATENATE(102,”,345”)`  
@@ -336,7 +336,7 @@ In an in-memory model, the result terminates at the last string character, with
 
 
 ## See also  
-[DirectQuery Mode](http://msdn.microsoft.com/en-us/45ad2965-05ec-4fb1-a164-d8060b562ea5)  
+[DirectQuery Mode](http://msdn.microsoft.com/45ad2965-05ec-4fb1-a164-d8060b562ea5)  
 
 
 

docs/analysis-services/tabular-models/directquery-mode-ssas-tabular.md

@@ -45,7 +45,7 @@ Tabular models in DirectQuery mode have some restrictions. Before switching mode
 |**Calculated tables**|Calculated tables are not supported in DirectQuery models, but calculated columns are. If you try to convert a tabular model that contains a calculated table, an error will occur stating that the model cannot contain pasted data.|  
 |**Query limits**|Default row limit is one million rows, which you can increase by specifying **MaxIntermediateRowSize** in the msmdsrv.ini file. See [DAX Properties](../../analysis-services/server-properties/dax-properties.md) for details.
 |**DAX formulas**|When querying a tabular model in DirectQuery mode, [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)] converts DAX formulas and measure definitions into SQL statements. DAX formulas containing elements that cannot be converted into SQL syntax will return validation errors on the model.<br /><br /> This restriction is mostly limited to certain DAX functions. For measures, DAX formulas are converted to set-based operations against the relational data store. This means that all measures created implicitly are supported. <br /><br /> When a validation error occurs, you'll need to re-write the formula, substituting a different function, or workaround it by using derived columns in the data source.  If a tabular model includes formulas containing incompatible functions will be reported when you switch to DirectQuery mode in the designer. <br /><br />**Note:**  Some formulas in the model might validate when you switch the model to DirectQuery mode, but return different results when executed against the cache vs. the relational data store. This is because calculations against the cache use the semantics of the in-memory analytics (engine, which contains features meant to emulate the behavior of Excel, whereas queries against data stored in the relational data source use the semantics of SQL Server.<br /><br /> SQL Stored  <br /><br /> To learn more, see [DAX formula compatibility in DirectQuery mode](../../analysis-services/tabular-models/dax-formula-compatibility-in-directquery-mode-ssas-2016.md).|  
-|**Formula consistency**|In certain cases, the same formula can return different results in a cached model compared to a DirectQuery model that uses only the relational data store. These differences are a consequence of the semantic differences between the in-memory analytics engine and SQL Server.<br /><br /> For a complete list of compatibility issues, including functions that might return different results when the model is deployed to real-time, see [DAX formula compatibility in DirectQuery mode (SQL Server Analysis Services)](http://msdn.microsoft.com/en-us/981b6a68-434d-4db6-964e-d92f8eb3ee3e).|  
+|**Formula consistency**|In certain cases, the same formula can return different results in a cached model compared to a DirectQuery model that uses only the relational data store. These differences are a consequence of the semantic differences between the in-memory analytics engine and SQL Server.<br /><br /> For a complete list of compatibility issues, including functions that might return different results when the model is deployed to real-time, see [DAX formula compatibility in DirectQuery mode (SQL Server Analysis Services)](http://msdn.microsoft.com/981b6a68-434d-4db6-964e-d92f8eb3ee3e).|  
 |**MDX limitations**|No relative object names. All object names must be fully qualified.<br /><br /> No session-scope MDX statements (named sets, calculated members, calculated cells, visual totals, default members, and so forth), but you can use query-scope constructs, such as the 'WITH' clause.<br /><br /> No tuples with members from different levels in MDX subselect clauses.<br /><br /> No user-defined hierarchies.<br /><br /> No native SQL queries (normally, Analysis Services supports a T-SQL subset, but not for DirectQuery models).|  
 
 ## Data sources supported for DirectQuery