Fixed SharePoint, OneDrive and on-premises typos (SharePoint#4837)

Author: andikrueger

docs/apis/export-amr-api.md

@@ -108,7 +108,7 @@ The use case for this function:  The ISV can issue a default read to retrieve th
 
 This flag indicates whether to return the extended set of metadata content of object query. By default this option is off and only basic content is provided (e.g. names, URL, author, modifier, dates) . Turning  this flag on provides all the metadata content; however, it will also impact the performance as query will take longer. 
 
-Recommendation is to keep the default for file share migration, but consider setting this flag on for SharePoint on-prem or other more complex migration.
+Recommendation is to keep the default for file share migration, but consider setting this flag on for SharePoint on-premises or other more complex migration.
 
     public string StartChangeToken { get; set; }
 

docs/apis/migration-api-overview.md

@@ -337,7 +337,7 @@ If the Migration API was unable to resolve a user using the login provided in th
 a)       This user will be replaced by “System Account” in the associated metadata within the package ( author, editor etc.).
 b)      A warning will be reported in the ImportLogs –  “Failed to ensure user '[email protected]'”
 
-If the migration API was unable to resolve a user using the login provided in the UserGroup.xml and the System ID is provided (which is the SID for the user in the on-prem AD), then:
+If the migration API was unable to resolve a user using the login provided in the UserGroup.xml and the System ID is provided (which is the SID for the user in the on-premises AD), then:
 a)       A new deleted user with the provided login and SystemId is created and is used in the associated metadata within the package.
 b)      A warning will be reported in the ImportLogs- “Failed to retrieve user '[email protected]' attributes from the SiteUsers; falling back to passed in values”
 

docs/apis/migration-isv-guidance.md

@@ -44,7 +44,7 @@ Azure Active Directory (AAD) provides two type of permission : delegated permiss
 
 - [Permissions and consent in the Azure Active Directory v1.0 endpoint](https://docs.microsoft.com/en-us/azure/active-directory/develop/v1-permissions-and-consent). 
 
-For Sharepoint and Onedrive migration scenarios, the guidance is to follow the AAD permission specification. 
+For SharePoint and OneDrive migration scenarios, the guidance is to follow the AAD permission specification. 
 
 For migration tool that relies on end user signed in and presence, delegated permission is recommended. 
 
@@ -87,7 +87,7 @@ If a feature is not supported by the migration API, we recommend that you use th
 
 ### CSOM Guidance (fallback only)
 
-The following provides guidance on specific CSOM implementation scenarios to help improve migration performance with Sharepoint and OneDrive.
+The following provides guidance on specific CSOM implementation scenarios to help improve migration performance with SharePoint and OneDrive.
 
 #### Enumeration Query Ordering guidance 
 There are two kinds of enumeration queries, assuming the client intends to read every item with no server-side filtering.

docs/general-development/external-events-and-alerts-in-sharepoint.md

@@ -40,7 +40,7 @@ public class EntryContentEventReceiver : SPItemEventReceiver
    }
 ```
 
-External event receivers can also be extended to work against an entity event receiver and as remote event receivers deployed as a service on-premise or in Microsoft Azure. 
+External event receivers can also be extended to work against an entity event receiver and as remote event receivers deployed as a service on-premises or in Microsoft Azure. 
 
 
 

docs/general-development/machine-translation-services-in-sharepoint.md

@@ -31,7 +31,7 @@ The Machine Translation Service application processes translation requests async
 
 ```
 
-$tj = get-sptimerjob "Sharepoint Translation Services"
+$tj = get-sptimerjob "SharePoint Translation Services"
 $tj.Runnow()
 ```
 

docs/general-development/sharepoint-add-ins-compared-with-sharepoint-solutions.md

@@ -18,12 +18,12 @@ This article compares the use cases of SharePoint Add-ins, farm solutions, and n
 - SharePoint farm solutions are packages of SharePoint components that are uploaded to a farm-wide gallery from where they can be installed. They cannot be distributed through the Office Store, and they cannot be installed on SharePoint Online. They can include custom managed code that runs on the SharePoint farm servers. For more information about the basics of farm solutions, see  [Solutions Overview](http://msdn.microsoft.com/library/1983cab9-4b29-494a-a62a-0f8e83908744%28Office.15%29.aspx) and [Farm Solutions in SharePoint 2010](http://msdn.microsoft.com/library/845f7524-b9ff-412b-aa29-3afacda91100%28Office.15%29.aspx).
 
 
-- NCSSs are also packages of SharePoint components; but they are uploaded to a site collection gallery from where they can be installed. They can be installed to either on-premise farms or to SharePoint Online, but they cannot be distributed through the Office Store. They can include the almost the same kinds of descriptive components as SharePoint Add-ins and, like add-ins, they can have JavaScript, but they do not contain custom managed code that runs on the SharePoint servers. Differences in the deployment systems of add-ins and NCSSs make NCSSs a better development option for a short list of scenarios. For information about sandboxed solutions, see  [Sandboxed Solutions in SharePoint 2010](https://technet.microsoft.com/en-us/library/ee721992%28v=office.14%29.aspx).
+- NCSSs are also packages of SharePoint components; but they are uploaded to a site collection gallery from where they can be installed. They can be installed to either on-premises farms or to SharePoint Online, but they cannot be distributed through the Office Store. They can include the almost the same kinds of descriptive components as SharePoint Add-ins and, like add-ins, they can have JavaScript, but they do not contain custom managed code that runs on the SharePoint servers. Differences in the deployment systems of add-ins and NCSSs make NCSSs a better development option for a short list of scenarios. For information about sandboxed solutions, see  [Sandboxed Solutions in SharePoint 2010](https://technet.microsoft.com/en-us/library/ee721992%28v=office.14%29.aspx).
 
 
 
 > **Important:**
-> While developing sandboxed solutions that contain only declarative markup and JavaScript -- which we call no-code sandboxed solutions (NCSS)-- is still viable, we have deprecated the use of custom managed code within the sandboxed solution. We have introduced the new SharePoint Add-in model as a replacement to those scenarios that required the use of managed code. The add-in model decouples the SharePoint core product from the add-in runtime, and this enables much more flexibility and gives you the ability to run the code in the environment of your choice. We realize that our customers have made investments in coded sandboxed solutions and we will phase them out responsibly. Existing coded sandboxed solutions will continue to work in on-premise SharePoint farms for the foreseeable future. Given the dynamic nature of online services, we will determine support needs for coded sandboxed solutions in SharePoint Online based on customer demand. NCSSs continue to be supported. All future investments will go to making the new SharePoint Add-in model richer and more powerful. Accordingly, we recommend that all new development should use the new add-in model whenever possible. In scenarios where you have to develop a farm solution or coded sandboxed solution, we recommend that you design it so that it can easily evolve toward a more loosely coupled development model. 
+> While developing sandboxed solutions that contain only declarative markup and JavaScript -- which we call no-code sandboxed solutions (NCSS)-- is still viable, we have deprecated the use of custom managed code within the sandboxed solution. We have introduced the new SharePoint Add-in model as a replacement to those scenarios that required the use of managed code. The add-in model decouples the SharePoint core product from the add-in runtime, and this enables much more flexibility and gives you the ability to run the code in the environment of your choice. We realize that our customers have made investments in coded sandboxed solutions and we will phase them out responsibly. Existing coded sandboxed solutions will continue to work in on-premises SharePoint farms for the foreseeable future. Given the dynamic nature of online services, we will determine support needs for coded sandboxed solutions in SharePoint Online based on customer demand. NCSSs continue to be supported. All future investments will go to making the new SharePoint Add-in model richer and more powerful. Accordingly, we recommend that all new development should use the new add-in model whenever possible. In scenarios where you have to develop a farm solution or coded sandboxed solution, we recommend that you design it so that it can easily evolve toward a more loosely coupled development model. 
   
 
 

docs/general-development/what-s-new-in-access.md

@@ -20,7 +20,7 @@ Access 2013 features a new application model that is designed for one purpose―
 ## Architecture
 <a name="SP15_access15overview_Architecture"> </a>
 
-In an on-premise environment, Access 2013 apps are hosted by SharePoint while the data is stored in SQL Server 2012. SharePoint provides authentication, authorization, and security for Access 2013 apps. The back-end tables, views, macros, and queries are stored in an SQL Server 2012 database.
+In an on-premises environment, Access 2013 apps are hosted by SharePoint while the data is stored in SQL Server 2012. SharePoint provides authentication, authorization, and security for Access 2013 apps. The back-end tables, views, macros, and queries are stored in an SQL Server 2012 database.
 
 
 

docs/solution-guidance/Branding-and-site-provisioning-solutions-for-SharePoint.md

@@ -155,7 +155,7 @@ The branding and provisioning code samples follow this sequence of events to sho
 |Step|Description|Samples|Article|
 |:-----|:-----|:-----|:-----|
 |1|The user requests a change to the site through a form, which kicks off an approval workflow. The data that the user submits via the request form are stored using potentially any data storage format (SQL, Azure SQL, XML).| <p>[SharePoint 2013: Use workflow to provision a SharePoint site (host web)](https://code.msdn.microsoft.com/SharePoint-2013-Use-e2ee88dd)</p><p>[SharePoint 2013: Use workflow to provision a SharePoint site (app web)](https://code.msdn.microsoft.com/SharePoint-2013-Use-2b96feb7)</p>| [SharePoint site provisioning solutions](sharepoint-site-provisioning-solutions.md)|
-|2|If the workflow is approved, the SharePoint Add-in calls the stored data, and provisions the site according to the metadata that user submitted in step 1.| <p>[Provision sites in batches with the add-in model](https://code.msdn.microsoft.com/Provision-sites-in-batches-fcf31bc6)</p><p>[SharePoint 2013: Use workflow to provision a SharePoint site (host web)](https://code.msdn.microsoft.com/SharePoint-2013-Use-e2ee88dd)</p><p>[SharePoint 2013: Use workflow to provision a SharePoint site (app web)](https://code.msdn.microsoft.com/SharePoint-2013-Use-2b96feb7)</p><p>[SharePoint 2013: Use SharePoint Add-ins to provision on-prem site collection](https://code.msdn.microsoft.com/SharePoint-2013-Use-apps-9094e012)</p>| [SharePoint site provisioning solutions](sharepoint-site-provisioning-solutions.md)|
+|2|If the workflow is approved, the SharePoint Add-in calls the stored data, and provisions the site according to the metadata that user submitted in step 1.| <p>[Provision sites in batches with the add-in model](https://code.msdn.microsoft.com/Provision-sites-in-batches-fcf31bc6)</p><p>[SharePoint 2013: Use workflow to provision a SharePoint site (host web)](https://code.msdn.microsoft.com/SharePoint-2013-Use-e2ee88dd)</p><p>[SharePoint 2013: Use workflow to provision a SharePoint site (app web)](https://code.msdn.microsoft.com/SharePoint-2013-Use-2b96feb7)</p><p>[SharePoint 2013: Use SharePoint Add-ins to provision on-premises site collection](https://code.msdn.microsoft.com/SharePoint-2013-Use-apps-9094e012)</p>| [SharePoint site provisioning solutions](sharepoint-site-provisioning-solutions.md)|
 |3|The SharePoint Add-in scopes provisioning to the instructions in the request form by using the data available in the add-in web and content database. During this stage, applicable branding elements are provisioned to the site.| <p>[SharePoint 2013: Use a SharePoint Add-in to configure CSS](https://code.msdn.microsoft.com/SharePoint-2013-Use-an-app-c5d78f25)</p><p>[SharePoint 2013: Use a SharePoint Add-in to apply a theme to a SharePoint site](https://code.msdn.microsoft.com/SharePoint-2013-Use-an-app-d90a49e3)</p><p>[SharePoint 2013: Brand a SharePoint OneDrive For Business site](https://code.msdn.microsoft.com/SharePoint-2013-Brand-a-6da627cb)</p><p>[SharePoint 2013: Provision custom CSS to a site with remote provisioning](https://code.msdn.microsoft.com/SharePoint-2013-Provision-bf1d878a)</p><p>[SharePoint 2013: Use a SharePoint Add-in to provision a wiki page](https://code.msdn.microsoft.com/SharePoint-2013-Use-an-app-5db977e8)</p>|<p>[SharePoint pages and the page model](sharepoint-pages-and-the-page-model.md)</p><p>[SharePoint site branding and page customization solutions](sharepoint-site-branding-and-page-customization-solutions.md)</p><p>[SharePoint site provisioning solutions](sharepoint-site-provisioning-solutions.md)|
 
 > [!NOTE] 

docs/solution-guidance/provisioning-console-application-sample.md

@@ -38,7 +38,7 @@ To begin, create a Visual Studio project. In this sample, for simplicity, we cre
 4. Download and install the PnP Core library that is available as a NuGet package at [OfficeDevPnP.Core packages](https://www.nuget.org/packages?q=SharePointPnPCore*).
 
 	> [!NOTE] 
-	> There are three versions of the library. One version is the **SharePointPnPCoreOnline** library, which targets SharePoint Online and Office 365. The other versions are **SharePointPnPCore2013** and **SharePointPnPCore2016** , which target SharePoint on-premise versions 2013 and 2016 respectively. 
+	> There are three versions of the library. One version is the **SharePointPnPCoreOnline** library, which targets SharePoint Online and Office 365. The other versions are **SharePointPnPCore2013** and **SharePointPnPCore2016** , which target SharePoint on-premises versions 2013 and 2016 respectively. 
 
 
 5. Install the NuGet client by going to the [NuGet client installer](http://docs.nuget.org/consume/installing-nuget).

docs/spfx/extensions/guidance/migrate-from-usercustomactions-to-spfx-extensions.md

@@ -101,7 +101,7 @@ SPOCustomUI.loadCSS = function (url) {
 }
 
 SPOCustomUI.init = function (whenReadyDoFunc) {
-    // avoid executing inside iframes (used by Sharepoint for dialogs)
+    // avoid executing inside iframes (used by SharePoint for dialogs)
     if (self !== top) return;
 
     if (!window.jQuery) {