Continued edit pass on Solutions guidance docs (SharePoint#1835)

* Edit pass on Sandbox topics

* Edit pass - Feature receivers

* Edit pass InfoPath

* Fixes

* Initial edit pass User profile

* Updated titles

* Fixed titles in Transform sections

* Fixes

* Fixes

* Initial updates User profiles

* Edit of Read or Update

* Fixes

* Edit pass Migrate

* Fixes

* Initial edit of Upload

* Edit Upload

* Edit Personalize

* Resized image in Personalize

* TOC - User profile section

* Edit pass on Bulk update topic

* Fixes

* Edit pass on Bulk Update

* Edit pass Bulk update

* Finish Bulk Update topic

* Fixes

* Fixes

* Initial edit pass for Deploy Add-ins

* Edit pass Deploy sites

* Edit Deploy Add-ins section

* Changed Portal to portal, updated link

[Azure portal](https://ms.portal.azure.com/)

* Finish edit pass on Deploy Add-ins section

* Changed Management Portal to portal,  updated link

[Azure portal](https://ms.portal.azure.com)

* Initial edit pass PnP remote provisioning

* Edit pass on PnP Provisioning Engine topic

* Attempt to push build

* Edit pass of PnP framework

* Updated "storage" capitalization per style guide

* Edit pass on Engine & Core topic

* Edit of PnP sample

* Fixes

* Initial edits on Timer Job topics

* Finished Timer Job Framework topic

* Fixes to TJ framework topic

* Edit pass of remote timer jobs

* Initial edit of WebJobs topic

* Edit of WebJobs topic

* Minor fixes to Modern Experience topics

* Edited Modern Provisioning doc

* Added site classification topic to master page

Author: Linda-Editor

docs/community/open-source-projects.md

@@ -17,7 +17,7 @@ There are numerous open-source projects that are coordinated by the SharePoint P
 | [Office 365 CLI](https://sharepoint.github.io/office365-cli/) | A cross-platform command-line interface (CLI) that allows users on any platform to manage various configuration settings of Office 365. |
 | [Office 365 Developer PnP Core Component](https://github.com/SharePoint/PnP-Sites-Core) | An extension component that encapsulates commonly used remote CSOM/REST operations as reusable extension methods on out-of-the box CSOM objects.  |
 | [PnP Partner Pack](https://github.com/SharePoint/PnP-Partner-Pack) | A starter kit for customers and partners that combines numerous patterns and practices demonstrated within PnP samples into one reusable solution targeting the classic SharePoint experience. |
-| [PnP PowerShell cmdlets](https://docs.microsoft.com/en-us/powershell/sharepoint/sharepoint-pnp/sharepoint-pnp-cmdlets?view=sharepoint-ps) | Allow you to perform complex provisioning and artifact management actions for SharePoint. The commands use CSOM and can work against both SharePoint online as well as SharePoint on-premises. |
+| [PnP PowerShell cmdlets](https://docs.microsoft.com/en-us/powershell/sharepoint/sharepoint-pnp/sharepoint-pnp-cmdlets?view=sharepoint-ps) | Allow you to perform complex provisioning and artifact management actions for SharePoint. The commands use CSOM and can work against both SharePoint Online as well as SharePoint on-premises. |
 | [PnP remote provisioning schema](https://github.com/SharePoint/PnP-provisioning-schema) | Designed to be used as remote creation instructions for the remote provisioning engine for Office 365. |
 | [PnPJS](https://pnp.github.io/pnpjs/) | A fluent JavaScript API for consuming SharePoint and Office 365 REST APIs in a type-safe way. |
 | [SharePoint Framework reusable property pane controls](https://sharepoint.github.io/sp-dev-fx-property-controls) | Can be used in SharePoint Framework (SPFx) solutions. |

docs/declarative-customization/site-design-pnp-provisioning.md

@@ -70,7 +70,7 @@ In this section, you will use Azure Queue storage to receive messages from Micro
 
 To set up the Azure Queue storage:
 
-1. Go to the [Azure portal](https://portal.azure.com) and sign in. 
+1. Go to the [Azure portal](https://ms.portal.azure.com/) and sign in. 
 
 2. Choose **+ New**.
 
@@ -192,7 +192,7 @@ Copy the following provisioning template XML to a new file and save the file as
 
 ## Create the Azure function
 
-1. Go to the [Azure Portal](https://portal.azure.com). 
+1. Go to the [Azure portal](https://ms.portal.azure.com/) . 
 
 2. Search for **Function App**, and create a new function app. In the **Storage** field, select **Use existing**, and then select the storage account that you created earlier. Set the other values as required. 
 
@@ -273,7 +273,7 @@ Next, upload the files so that your Azure function can use the module.
     Apply-PnPProvisioningTemplate -Path D:\home\site\wwwroot\ApplyPnPProvisioningTemplate\FlowDemoTemplate.xml
    ```
 
-4. Notice that you're using two environment variables: `SPO_AppId`and `SPO_AppSecret`. To set those variables, go to the main Function app page in the Azure Portal, select **Application settings**, and add two new application settings:
+4. Notice that you're using two environment variables: `SPO_AppId`and `SPO_AppSecret`. To set those variables, go to the main Function app page in the Azure portal, select **Application settings**, and add two new application settings:
 
    - `SPO_AppId` - Set the value to the Client ID you copied in the first step when you created your app on your tenant. 
 

docs/general-development/develop-sharepoint-workflows-using-visual-studio.md

@@ -167,7 +167,7 @@ To debug SharePoint Online workflows in Visual Studio, perform the following ste
     For information about how to register for a Microsoft Azure account, see  [Microsoft Azure](http://www.windowsazure.com).
 
 
-3. Create a Microsoft Azure Service Bus namespace, which you can use to debug remote workflows. You can do this on the  [Microsoft Azure management portal](http://manage.windowsazure.com).
+3. Create a Microsoft Azure Service Bus namespace, which you can use to debug remote workflows. You can do this on the [Microsoft Azure portal](https://ms.portal.azure.com).
 
     For more information about the Microsoft Azure Service Bus, see  [Managing Service Bus Service Namespaces](http://msdn.microsoft.com/en-us/library/windowsazure/hh690928.aspx).
 

docs/general-development/how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj.md

@@ -73,7 +73,7 @@ To create a console application that uses the server object model to work with u
   -  [Retrieve and change values for user properties](how-to-work-with-user-profiles-and-organization-profiles-by-using-the-server-obj.md#bkmk_GetChangePropValues)
 
 
-7. To test the console application, on the menu bar, choose **Debug**, **Start Debugging**. You can check your changes from the **Manage Profile Service** page for the User Profile Service Application in Central Administration.
+7. To test the console application, on the menu bar, choose **Debug**, **Start Debugging**. You can check your changes from the **Manage Profile Service** page for the user profile service application in Central Administration.
 
 
 

docs/general-development/incoming-claims-signing-into-sharepoint.md

@@ -40,7 +40,7 @@ In Security Assertion Markup Language (SAML) passive sign-in, when a user signs
 
 
 
-For SAML-based claims providers, like the Active Directory Federation Services (ADFS) claims provider and the Windows Live ID claims provider, signing in by using the SAML passive sign-in mode is the only supported way. The SAML passive sign-in is the SharePoint online identity model.
+For SAML-based claims providers, like the Active Directory Federation Services (ADFS) claims provider and the Windows Live ID claims provider, signing in by using the SAML passive sign-in mode is the only supported way. The SAML passive sign-in is the SharePoint Online identity model.
 
 > [!NOTE]
 > SAML passive sign-in describes the process of signing in. When a sign-in for a web application is configured to accept tokens from a trusted login provider, this type of sign-in is called SAML passive sign-in. A trusted login provider is an external (that is, external to SharePoint) security token service (STS) that SharePoint trusts. 

docs/general-development/overview-of-the-sharepoint-mobile-client-authentication-object-model.md

@@ -292,7 +292,7 @@ ClientContext ctx = new ClientContext("SiteUrl");
 
 ```
 
- **ADFS** is an optional property which will be effective only when it is used with Microsoft SharePoint Online. Using **ADFS** authentication with any other authentication scheme will not have any effect. With Microsoft SharePoint online, if **ADFS** is not set then default scheme will be used, i.e. server preference.
+ **ADFS** is an optional property which will be effective only when it is used with Microsoft SharePoint Online. Using **ADFS** authentication with any other authentication scheme will not have any effect. With Microsoft SharePoint Online, if **ADFS** is not set then default scheme will be used, i.e. server preference.
 
 
 

docs/general-development/set-up-a-general-development-environment-for-sharepoint.md

@@ -36,11 +36,11 @@ If you have an MSDN subscription, you can quickly provision a virtual machine in
 If you haven't activated the Microsoft Azure benefit that comes with your MSDN subscription, you can learn more about it at  [Microsoft Azure Benefit for MSDN Subscribers](http://azure.microsoft.com/en-us/pricing/member-offers/msdn-benefits/).
 
 > [!NOTE]
-> The Microsoft Azure Image Gallery no longer provides images with SharePoint and Visual Studio preinstalled. But a Microsoft Azure VM is still a good option for a development machine. > Sign in to the  [Microsoft Azure management portal](https://manage.windowsazure.com). > Create a VM using one of the images in the gallery for Windows Server 2008 R2 Service Pack 1 x64, Windows Server 2012 (or later). Follow the instructions provided by the virtual machine creation wizard. We recommend an **X-Large** VM size for SharePoint development.> After the machine is provisioned and running, complete the setup using the same procedures in the section below **Create a SharePoint development environment on premises**. (Skip the section about installing the operating system.)> Once you've set up your development environment, you can access your source control from Visual Studio on the virtual machine by using an Azure Point-to-Site connection. See  [Configure a point-to-site VPN connection to an Azure Virtual Network](https://azure.microsoft.com/en-us/documentation/articles/vpn-gateway-point-to-site-create/) for instructions on how to do this.
-  
-    
-    
-
+> The Microsoft Azure Image Gallery no longer provides images with SharePoint and Visual Studio preinstalled. But a Microsoft Azure virtual machine is still a good option for a development machine. 
+> Sign in to the [Microsoft Azure portal](https://ms.portal.azure.com). 
+> Create a VM using one of the images in the gallery for Windows Server 2008 R2 Service Pack 1 x64, Windows Server 2012 (or later). Follow the instructions provided by the virtual machine creation wizard. We recommend an **X-Large** VM size for SharePoint development.
+> After the machine is provisioned and running, complete the setup using the same procedures in the section below **Create a SharePoint development environment on premises**. (Skip the section about installing the operating system.)
+> Once you've set up your development environment, you can access your source control from Visual Studio on the virtual machine by using an Azure Point-to-Site connection. See [Configure a point-to-site VPN connection to an Azure Virtual Network](https://azure.microsoft.com/en-us/documentation/articles/vpn-gateway-point-to-site-create/) for instructions on how to do this.
 
 ## Create a SharePoint development environment on premises
 <a name="SP15_bk_devenvazure"> </a>

docs/general-development/use-feature-upgrade-to-apply-new-sharepoint-master-pages-when-upgrading-fro.md

@@ -126,7 +126,7 @@ public override void FeatureUpgrading(SPFeatureReceiverProperties properties, st
 
 ```
 
-Once you're done with the upgrade, you'll want to think about the future and long-term maintenance of your feature. Refer to  [Application Lifecycle Management in SharePoint 2010](http://msdn.microsoft.com/en-us/library/office/gg604045%28v=office.14%29.aspx) for guidance on maintaining full-trust code. Although this article refers to SharePoint 2010 specifically, it applies equally well to full-trust code in SharePoint. If you aren't familiar with feature versioning and upgrade actions, refer to the [Models for Solution Lifecycle Management](http://msdn.microsoft.com/en-us/library/office/gg604045%28v=office.14%29.aspx#sectionSection7) section of this article. You should also look at [Best Practices for Using Feature Versions](http://msdn.microsoft.com/en-us/library/office/ee535064%28v=office.14%29.aspx).
+Once you're done with the upgrade, you'll want to think about the future and long-term maintenance of your feature. Refer to  [Application Lifecycle Management in SharePoint 2010](http://msdn.microsoft.com/en-us/library/office/gg604045%28v=office.14%29.aspx) for guidance on maintaining full trust code. Although this article refers to SharePoint 2010 specifically, it applies equally well to full trust code in SharePoint. If you aren't familiar with feature versioning and upgrade actions, refer to the [Models for Solution Lifecycle Management](http://msdn.microsoft.com/en-us/library/office/gg604045%28v=office.14%29.aspx#sectionSection7) section of this article. You should also look at [Best Practices for Using Feature Versions](http://msdn.microsoft.com/en-us/library/office/ee535064%28v=office.14%29.aspx).
 
 
 

docs/general-development/using-odata-sources-with-business-connectivity-services-in-sharepoint.md

@@ -45,7 +45,7 @@ The following are some examples of implementations of OData. These applications
 - SQL Azure
 
 
-- Microsoft Azure Table Storage
+- Microsoft Azure Table storage
 
 
 - Microsoft Azure Marketplace

docs/scenario-guidance/Long-running-scheduled-operations.md

@@ -78,22 +78,22 @@ In this pattern, the Azure WebJob handles the scheduling aspects associated with
 - [Asynchronous operations with Azure storage queues and WebJobs](https://dev.office.com/patterns-and-practices-detail/2254)
 - [Content Type Enforce Retention](https://dev.office.com/patterns-and-practices-detail/2266)
 
-### PnP Timer Job Framework
+### PnP timer job framework
 
 _**Applies to:** Office 365 and SharePoint Server_
 
-The PnP Timer Job Framework is a set of classes designed to ease the creation of background processes that operate against SharePoint sites. The Timer Job Framework is similar to on-premises full trust code Timer Jobs (`SPJobDefinition`). The primary difference with between the Timer Job Framework and the full trust code Timer Job is that the Timer Job Framework only uses client side APIs and therefore can (and should) be run outside of SharePoint. The Timer Job Framework makes it possible to build Timer Jobs that operate against SharePoint Online.
+The PnP timer job framework is a set of classes designed to ease the creation of background processes that operate against SharePoint sites. The timer job framework is similar to on-premises full trust code Timer Jobs (`SPJobDefinition`). The primary difference with between the timer job framework and the full trust code Timer Job is that the timer job framework only uses client side APIs and therefore can (and should) be run outside of SharePoint. The timer job framework makes it possible to build Timer Jobs that operate against SharePoint Online.
 
 #### Related resources
 
 ##### Articles
 
-- [The Timer Job Framework](https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/timerjob-framework)
+- [PnP timer job framework](https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/timerjob-framework)
 - [Create remote timer jobs in SharePoint](https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/create-remote-timer-jobs-in-sharepoint)
 
 ##### Videos
 
-- [PnP Core Component - Remote Timer Job Framework](https://www.youtube.com/watch?v=nzL6jCv0dKQ)
+- [PnP Core Component - Remote timer job framework](https://www.youtube.com/watch?v=nzL6jCv0dKQ)
 - [Introduction to the PnP timer job framework](http://channel9.msdn.com/blogs/OfficeDevPnP/Introduction-to-the-PnP-timer-job-framework)
 - [Creating simple remote timer job](https://channel9.msdn.com/Blogs/Office-365-Dev/Simple-remote-timer-job-that-interacts-with-SharePoint-Online-Office-365-Developer-Patterns-and-Prac)