Change database user to login for sqlrusergroup

.openpublishing.redirection.json

@@ -245,6 +245,11 @@
             "redirect_url": "/sql/advanced-analytics/security/add-sqlrusergroup-to-database",
             "redirect_document_id": false
         }, 
+        {
+            "source_path": "docs/advanced-analytics/security/add-sqlrusergroup-to-database.md",
+            "redirect_url": "/sql/advanced-analytics/security/create-a-login-for-sqlrusergroup.md",
+            "redirect_document_id": true
+        }, 
         {
             "source_path": "docs/advanced-analytics/r/differences-in-r-features-between-editions-of-sql-server.md",
             "redirect_url": "/sql/sql-server/editions-and-components-of-sql-server-2017",

docs/advanced-analytics/security/add-sqlrusergroup-to-database.md → docs/advanced-analytics/security/create-a-login-for-sqlrusergroup.md

@@ -1,26 +1,26 @@
 ---
-title: Add SQLRUserGroup as a SQL Server Login - SQL Server Machine Learning Services
-description: For loopback connections using implied authentication, add SQLRUserGroup as a SQL Server login so that a worker account can log in to the server, for identity conversion back to the calling user.
+title: Create a login for SQLRUserGroup - SQL Server Machine Learning Services
+description: For loopback connections using implied authentication, create a login in SQL Server for SQLRUserGroup, so that a worker account can log in to the server, for identity conversion back to the calling user.
 ms.prod: sql
 ms.technology: machine-learning
 
-ms.date: 10/17/2018  
+ms.date: 01/25/2019  
 ms.topic: conceptual
 author: dphansen
 ms.author: davidph
 manager: cgronlun
 ---
-# Add SQLRUserGroup as a SQL Server login
+# Create a login for SQLRUserGroup
 [!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md-winonly](../../includes/appliesto-ss-xxxx-xxxx-xxx-md-winonly.md)]
 
-Create a SQL Server login for [SQLRUserGroup](../concepts/security.md#sqlrusergroup) when a [loop back connection](../../advanced-analytics/concepts/security.md#implied-authentication) in your script specifies a *trusted connection*, and the identity used to execute an object contains your code is a Windows user account.
+Create a [login in SQL Server](https://docs.microsoft.com/sql/relational-databases/security/authentication-access/create-a-login) for [SQLRUserGroup](../concepts/security.md#sqlrusergroup) when a [loop back connection](../../advanced-analytics/concepts/security.md#implied-authentication) in your script specifies a *trusted connection*, and the identity used to execute an object contains your code is a Windows user account.
 
 Trusted connections are those having `Trusted_Connection=True` in the connection string. When SQL Server receives a request specifying a trusted connection, it checks whether the identity of the current Windows user has a login. For external processes executing as a worker account (such as MSSQLSERVER01 from **SQLRUserGroup**), the request fails because those accounts do not have a login by default.
 
-You can work around the connection error by giving **SQLServerRUserGroup** a SQL Server login. For more information about identities and external processes, see [Security overview for the extensibility framework](../concepts/security.md).
+You can work around the connection error by creating a login for  **SQLServerRUserGroup**. For more information about identities and external processes, see [Security overview for the extensibility framework](../concepts/security.md).
 
 > [!Note]
->  Make sure that **SQLRUserGroup** has "Allow Log on locally" permissions. By default, this right is given to all new local users, but in some organizations stricter group policies might disable this right.
+> Make sure that **SQLRUserGroup** has "Allow Log on locally" permissions. By default, this right is given to all new local users, but some organizations stricter group policies might disable this right.
 
 ## Create a login