fixed spelling errors and date

Author: rjagiewich

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

@@ -4,7 +4,7 @@ description: Add new R packages to SQL Server 2016 R Services or SQL Server 2017
 ms.prod: sql
 ms.technology: machine-learning
 
-ms.date: 05/17/2018  
+ms.date: 05/17/2019  
 ms.topic: conceptual
 author: dphansen
 ms.author: davidph
@@ -26,7 +26,7 @@ This article describes how to install new R packages to an instance of SQL Serve
 
 The R package library is physically located in the Program Files folder of your SQL Server instance, in a secure folder with restricted access. Writing to this location requires administrator permissions.
 
-Non-administrators can install packages but doing so requires addititional configuration and capability not available in initial installations. There are two approaches for non-admin package installations: RevoScaleR using version 9.0.1 and later, or using CREATE EXTERNAL LIBRARY (SQL Server 2017 only). In SQL Server 2017, **dbo_owner** or another user with CREATE EXTERNAL LIBRARY permission can install R packages to the current database.
+Non-administrators can install packages but doing so requires additional configuration and capability not available in initial installations. There are two approaches for non-admin package installations: RevoScaleR using version 9.0.1 and later, or using CREATE EXTERNAL LIBRARY (SQL Server 2017 only). In SQL Server 2017, **dbo_owner** or another user with CREATE EXTERNAL LIBRARY permission can install R packages to the current database.
 
 R developers are accustomed to creating user libraries for the packages they need if centrally located libraries are off-limits. This practice is problematic for R code executing in a SQL Server database engine instance. SQL Server cannot load packages from external libraries, even if that library is on the same computer. Only packages from the instance library can be used in R code running in SQL Server.
 
@@ -46,7 +46,7 @@ In general, servers that host production databases block internet connections. I
 
 Identifying all dependencies gets complicated. For R, we recommend that you use [miniCRAN to create a local repository](create-a-local-package-repository-using-minicran.md) and then transfer the fully defined repo to an isolated SQL Server instance.
 
-Alternativley, you can perform this steps manually:
+Alternatively, you can perform these steps manually:
 
 1. Identify all package dependencies. 
 2. Check whether any required packages are already installed on the server. If the package is installed, verify that the version is correct.
@@ -91,4 +91,4 @@ Packages that are installed to the R_SERVER library are used only by a standalon
 ## See also
 
 + [Install new Python packages](../python/install-additional-python-packages-on-sql-server.md)
-+ [Tutorials, samples, solutions](../tutorials/machine-learning-services-tutorials.md)
++ [Tutorials, samples, solutions](../tutorials/machine-learning-services-tutorials.md)