Acrolinx fixes

Author: jeannt

docs/advanced-analytics/r/create-a-local-package-repository-using-minicran.md

@@ -27,29 +27,24 @@ There are two ways that you can prepare R packages for installation onto a serve
 
 -   [Manually download and copy packages one by one](#bkmk_manual)
 
-This article describes how you can create an R package repository using both methods, with particualr emphasis on the **miniCRAN** package.
+This article describes how you can create an R package repository using both methods, and recommends use of the **miniCRAN** package.
 
 ## Prepare packages using miniCRAN
 
 The goal of creating a local package repository is to provide a single location that a server administrator or other users in the organization can use to install new R packages on a server that does not have internet access.
 
-The miniCRAN package for R was written by Andre de Vries to make it easier to create a consistent, managed set of R packages for an organization.
-
-After creating the repository, you can modify it by adding new packages or upgrading the version of existing packages.
-
--   For details, see [miniCRAN](https://cran.r-project.org/web/packages/miniCRAN/index.html)
-
--   For a walkthrough of the repository creation process, see [How to install R packages on an off-line SQL Server 2016 instance](http://blog.revolutionanalytics.com/2016/05/minicran-sql-server.html)
-
+The [miniCRAN](https://cran.r-project.org/web/packages/miniCRAN/index.html) package for R was written by [Andre de Vries](http://blog.revolutionanalytics.com/2016/05/minicran-sql-server.html) to make it easier to create a consistent, managed set of R packages for an organization. 
 
 There are many advantages to using miniCRAN to create the repository:
 
--   **Security**: Many R users are accustomed to downloading and installing new R packages at will, from CRAN or one of its mirror sites. However, for security reasons, production servers running [!INCLUDE[ssNoVersion_md](file:///C:\includes\ssnoversion-md.md)] typically do not have internet connectivity.
+-   **Security**: Many R users are accustomed to downloading and installing new R packages at will, from CRAN or one of its mirror sites. However, for security reasons, production servers running [!INCLUDE[ssNoVersion_md](..\..\includes\ssnoversion-md.md)] typically do not have internet connectivity.
 
 -   **Easier offline installation**: To install package to an offline server requires that you also download all package dependencies, Using miniCRAN makes it easier to get all dependencies in the correct format.
 
 -   **Improved version management**: In a multiuser environment, there are good reasons to avoid unrestricted installation of multiple package versions on the server.
 
+After creating the repository, you can modify it by adding new packages or upgrading the version of existing packages.
+
 ### Step 1. Install the miniCRAN package
 
 You begin by creating a miniCRAN repository to use as a source. You should create this repository on a computer that has internet access.
@@ -83,7 +78,7 @@ You begin by creating a miniCRAN repository to use as a source. You should creat
 
 1.  After miniCRAN is installed, create a list that specifies the additional packages you want to download.
 
-    Do not include dependencies; the **igraph** package used by miniCRAN generates the list of dependencies for you. For more information about how to use this graph, see [Using miniCRAN to identify package
+    Do not add dependencies to this initial list; the **igraph** package used by miniCRAN generates the list of dependencies for you. For more information about how to use this graph, see [Using miniCRAN to identify package
     dependencies](https://cran.r-project.org/web/packages/miniCRAN/vignettes/miniCRAN-dependency-graph.html).
 
     The following R script demonstrates how to get the target packages, "zoo"
@@ -105,7 +100,7 @@ You begin by creating a miniCRAN repository to use as a source. You should creat
     makeRepo(pkgs_expanded, path = local_repo, repos = CRAN_mirror, type = "win.binary", Rversion = "3.3")
     ```
 
-    From this information, the miniCRAN package creates the folder structure that you need to copy the packages to the [!INCLUDE[ssNoVersion_md](file:///C:\includes\ssnoversion-md.md)] later.
+    From this information, the miniCRAN package creates the folder structure that you need to copy the packages to the [!INCLUDE[ssNoVersion_md](..\..\includes\ssnoversion-md.md)] later.
 
 4. At this point you should have a folder containing the packages you needed, and any additional packages that were required.
 
@@ -192,7 +187,7 @@ After downloading the packages, you install the R packages from the zipped file
 
 1.  Download the packages zip files, and save them in a local folder
 
-2.  Copy that folder to the [!INCLUDE[ssNoVersion_md](file:///C:\includes\ssnoversion-md.md)] computer.
+2.  Copy that folder to the [!INCLUDE[ssNoVersion_md](..\..\includes\ssnoversion-md.md)] computer.
 
 3.  Install the packages into the SQL Server instance library.
 

docs/advanced-analytics/r/determine-which-packages-are-installed-on-sql-server.md

@@ -17,14 +17,13 @@ manager: "jhubbard"
 ---
 # Determine which R packages are installed on SQL Server
 
-When you install Machine Learning Services with the R language option, or install
-[!INCLUDE[rsql_productname](file:///C:\includes\rsql-productname-md.md)], setup creates an R package library associated with the instance. Each instance has a separate package library. Package libraries are **not** shared across instances, so it is possible for different packages to be installed on different instances.
+When you install machine learning in SQL Server with the R language option, setup creates an R package library associated with the instance. Each instance has a separate package library. Package libraries are **not** shared across instances, so it is possible for different packages to be installed on different instances.
 
-This article describes how you can determine which R packages are installed for a specific the [!INCLUDE[ssNoVersion](file:///C:\includes\ssnoversion-md.md)] instance.
+This article describes how you can determine which R packages are installed for a specific instance.
 
 ## Generate R package list using a stored procedure
 
-The following example uses the base R function `installed.packages()` in a [!INCLUDE[tsql](file:///C:\includes\tsql-md.md)] stored procedure to get a matrix of packages that have been installed in the R_SERVICES library for the current instance. To avoid parsing the fields in the DESCRIPTION file, only the name is returned.
+The following example uses the R function `installed.packages()` in a [!INCLUDE[tsql](..\..\includes\tsql-md.md)] stored procedure to get a matrix of packages that have been installed in the R_SERVICES library for the current instance. To avoid parsing the fields in the DESCRIPTION file, only the name is returned.
 
 ```SQL
 EXECUTE sp_execute_external_script
@@ -52,7 +51,7 @@ GO
 
 This example looks for and loads the RevoScaleR library.
 
-+ If the package is found, the message returned should be something like "Commands completed successfully".
++ If the package is found, the message returned should be something like "Commands completed successfully."
 
 + If the package cannot be located or loaded, you get an error like this: "An external script error occurred: Error in library("RevoScaleR"): there is no package called RevoScaleR"
 

docs/advanced-analytics/r/install-additional-r-packages-on-sql-server.md

@@ -30,10 +30,11 @@ The process differs slightly depending on the version of SQL Server you are runn
 
     See [Getting the correct package version and format](#packageVersion) for details.
 
-2.  If the server does not have internet access, you'll need to download the binaries in zipped format in advance. 
+2.  If the server does not have internet access, download the binaries in advance.
+
     See [Download zip files](#bkmk_zipPreparation) for details.
 
-3. If installing offline, check for package dependencies and get any related packages that might be needed during installation. Using the [miniCRAN package](#bkmk_packageDependencies) is an easy way to prepare a collection of packages and their dependeicnies.
+3. If installing offline, check for package dependencies and get any related packages that might be needed during installation. Using the [miniCRAN package](#bkmk_packageDependencies) is an easy way to prepare a collection of packages and their dependencies.
 
 4.  Package installation methods differ depending on whether the server has internet access, and on your version of SQL Server. The recommended methods are as follows:
 
@@ -59,7 +60,7 @@ The process differs slightly depending on the version of SQL Server you are runn
 
 There are multiple sources for R packages, the best known among them being CRAN and Bioconductor. The official site for the R language (<https://www.r-project.org/>) lists many of these resources. Many packages are also published to GitHub, where you can obtain the source code. However, you may also have been given R packages that were developed by someone in your company.
 
-Regardless of the source, you must ensure that the package you want to install has a binary format for the Windows platform. Otherwise the downloaded package will not run in the SLQ Server environment.
+Regardless of the source, you must ensure that the package you want to install has a binary format for the Windows platform. Otherwise the downloaded package cannot run in the SQL Server environment.
 
 You should also determine whether the package is compatible with the version of R that is running in SQL Server.
 
@@ -91,7 +92,7 @@ If you need to install multiple packages, or want to ensure that everyone in you
 
 If you are an experienced R user, you might be accustomed to installing packages from the command line without special permissions, or without downloading them in advance. However, most servers do not have an internet connection and access to file shares or storage might be restricted.
 
-This section describes the different level of permissions required for installing pckages in SQL Server 2016 and SQl Server 2017. Installation can  be done using either R tools or SQL Server, but the process and permissions differ slightly.
+This section describes the different level of permissions required for installing packages in SQL Server 2016 and SQl Server 2017. Installation can  be done using either R tools or SQL Server, but the process and permissions differ slightly.
 
 -   SQL Server 2016
 
@@ -107,7 +108,7 @@ This section describes the different level of permissions required for installin
 
 > [!IMPORTANT]
 > 
-> Experienced R users are accustomed to installing packages in a user library, and then referencing the package in that folder as part of the R solution, by specifying a file path. This practice will not work in SQL Server. For more information and workarounds, see [How to use packages in user libraries](packages-installed-in-user-libraries.md).
+> Experienced R users are accustomed to installing packages in a user library, and then referencing the package in that folder as part of the R solution, by specifying a file path. This practice is not supported in SQL Server. For more information and workarounds, see [How to use packages in user libraries](packages-installed-in-user-libraries.md).
 
 ### Comparing package management methods
 

docs/advanced-analytics/r/installing-and-managing-r-packages.md

@@ -63,29 +63,29 @@ Installation of R in SQL Server 2016 and SQL Server 2017 also includes the **Rev
 
 ## Permissions required for installing R packages
 
-In SQL Server 2016, an administrator had to istall new R packages on an instance-wide basis. In SQL Server 2017, new database features were added that give the database administrator the ability to delegate package management to selected users.
+In SQL Server 2016, an administrator had to install new R packages on an instance-wide basis. In SQL Server 2017, new database features were added that give the database administrator the ability to delegate package management to selected users.
 
 This section describes the permissions required to install and manage packages per version.
 
 + SQL Server 2016 R Services (In-Database)
 
-    To install a new R package on a computer that is running [!INCLUDE[ssCurrent](file:///C:\includes\sscurrent-md.md)], you must have administrative rights to the computer. It is the task of the database administrator or other administrator on the server to ensure that all required packages are installed on the [!INCLUDE[ssNoVersion_md](file:///C:\includes\ssnoversion-md.md)] instance.
+    To install a new R package on a computer that is running [!INCLUDE[ssCurrent](..\..\includes\sscurrent-md.md)], you must have administrative rights to the computer. It is the task of the database administrator or other administrator on the server to ensure that all required packages are installed on the [!INCLUDE[ssNoVersion_md](..\..\includes\ssnoversion-md.md)] instance.
 
-    If you do not have administrative privileges on the computer that hosts the [!INCLUDE[ssNoVersion_md](file:///C:\includes\ssnoversion-md.md)] instance, you can provide to the administrator information about how to install R packages, and provide access to a secure package repository where packages requested by users can be obtained.
+    If you do not have administrative privileges on the computer that hosts the [!INCLUDE[ssNoVersion_md](..\..\includes\ssnoversion-md.md)] instance, you can provide to the administrator information about how to install R packages, and provide access to a secure package repository where packages requested by users can be obtained.
 
 + SQL Server 2017 Machine Learning Services
 
-    This release includes package management functions that let database administrator delegate package installation rights to selected users. If this feature has been enabled, request that your database administrator add you to one of the new pakcage roles. For more information, see [R package management for SQL Server](r-package-management-for-sql-server-r-services.md).
+    This release includes package management functions that let database administrator delegate package installation rights to selected users. If this feature has been enabled, request that your database administrator add you to one of the new package roles. For more information, see [R package management for SQL Server](r-package-management-for-sql-server-r-services.md).
 
-    If you are an administrator on the SQL Server instance, you can install new packages at will. Just be sure to use the default library that is associated with the instance, or the package might not run when called from a stored procedure, or as part of a remote SQL Server compute context.
+    If you are an administrator on the SQL Server instance, you can install new packages at will. Just be sure to use the default library that is associated with the instance. Packages installed to other locations cannot run when called from a stored procedure. Any R code that runs using the SQL Server as a compute context also requires that packages be available in the instance library.
 
 + R Server (Standalone)
 
     You need administrative rights to the computer to install new R packages.
 
 + Other client environments
 
-    If you are installing a new R package on a computer that is being used as an R workstation and the computer does **not** have an instance of [!INCLUDE[ssNoVersion_md](file:///C:\includes\ssnoversion-md.md)] installed, you still need administrative rights to the computer to install the package. After you have installed the package, you can run it locally.
+    If you are installing a new R package on a computer that is being used as an R workstation and the computer does **not** have an instance of [!INCLUDE[ssNoVersion_md](..\..\includes\ssnoversion-md.md)] installed, you still need administrative rights to the computer to install the package. After you have installed the package, you can run it locally.
 
 ## Managing or viewing installed packages
 

docs/advanced-analytics/r/package-install-uninstall-and-sync.md

@@ -46,7 +46,7 @@ Before you can use package synchronization, you must have the appropriate versio
 
 This feature is available in SQL Server 2017 CTP 2 or later.
 
-Because this feature uses R functions in Microsoft R version 9.1.0, you can add this feature to a instance of SQL Server 2016 by upgrading the instance to use the latest version of Microsoft R. For more information, see [Use SqlBindR.exe to Upgrade SQL Server R Services](use-sqlbindr-exe-to-upgrade-an-instance-of-sql-server.md).
+Because this feature uses R functions in Microsoft R version 9.1.0, you can add this feature to an instance of SQL Server 2016 by upgrading the instance to use the latest version of Microsoft R. For more information, see [Use SqlBindR.exe to Upgrade SQL Server R Services](use-sqlbindr-exe-to-upgrade-an-instance-of-sql-server.md).
 
 ### Enable the package management feature
 
@@ -63,7 +63,7 @@ Whenever you add a new package using the package management functions, both the
 > You cannot use package synchronization if you have been installing R packages the traditional way, using R tools to install packages directly into the file system.
 ### Permissions
 
-+ The person who executes the package snchronization function must be a security principal on the SQL
++ The person who executes the package synchronization function must be a security principal on the SQL
     Server instance and database that has the packages.
 
 + The caller of the function must be a member of one of these package management roles: **rpkgs-shared** or **rpkgs-private**.
@@ -103,13 +103,13 @@ rxSyncPackages(computeContext=computeContext, verbose=TRUE)
 
 ### Example 2. Restrict synchronized packages by scope
 
-The following examples synchonize only the packages in the specified scope.
+The following examples synchronize only the packages in the specified scope.
 
 ```R
 #Shared scope
 rxSyncPackages(computeContext=computeContext, scope="shared", verbose=TRUE)
 
-#Private scope**
+#Private scope
 rxSyncPackages(computeContext=computeContext, scope="private", verbose=TRUE)
 ```
 

docs/advanced-analytics/r/packages-installed-in-user-libraries.md

@@ -17,25 +17,25 @@ manager: "jhubbard"
 ---
 # Avoiding errors on R packages installed in user libraries
 
-Experienced R users are accustomed to installing R packages in a user library, if the default library is blocked or not available. However, this approach is not supported in SQL Server, and installation to a user library usually ends in a “package not found” error.
+Experienced R users are accustomed to installing R packages in a user library, whenever the default library is blocked or not available. However, this approach is not supported in SQL Server, and installation to a user library usually ends in a “package not found” error.
 
 This topic provides workarounds to help you avoid this error. It explains how you can modify your R code, and suggests the correct R package installation process for using R packages from a SQL Server instance.
 
 ## Why R user libraries cannot be accessed from SQL Server
 
-R developers who need to install new R packages are accustomed to installing packages at will, and using a private, user library whenever the default library is not available, or if the developer is not an administrator on the computer.
+R developers who need to install new R packages are accustomed to installing packages at will, and using a private, user library whenever the default library is not available, or when the developer is not an administrator on the computer.
 
 For example, in a typical R development environment, the user would add the  location of the package to the R environment variable `libPath`, or reference the full package path, like this:
 
 ```R
 library("c:/Users/<username>/R/win-library/packagename")  
 ```
 
-However, this can never work when running R solutions in SQL Server, because R packages must be installed to a specific default library that is associated with the instance. 
+However, this can never work when running R solutions in SQL Server, because R packages must be installed to a specific default library that is associated with the instance.
 
 If the package is not installed in the default library, you might get this error when you try to call the package:
 
-*Error in library(xxx) : there is no package called 'xxx'*
+*Error in library(xxx) : there is no package called 'package-name'*
 
 It is also a bad development practice to install required R packages to a custom user library, as it can lead to errors if a solution is run by another user who does not have access to the library location.