Updates to Dev Program links (SharePoint#1468)

* Updated for new dev program release

* Updates for dev program release

* Fixed bullet

* Minor tweaks

* Updates for Dev Program release

* Updates for new Dev Program

* Attempt to fix link

* Updated Dev Program links

Author: Linda-Editor

docs/apis/webhooks/get-started-webhooks.md

@@ -1,7 +1,7 @@
 ---
 title: Get started with SharePoint webhooks
 description: Build an application that adds and handles SharePoint webhook requests.
-ms.date: 02/08/2018
+ms.date: 03/14/2018
 ms.prod: sharepoint
 ---
 
@@ -10,15 +10,15 @@ ms.prod: sharepoint
 
 This article describes how to build an application that adds and handles SharePoint webhook requests. You will learn how to use [Postman client](https://www.getpostman.com/) to construct and execute SharePoint webhook requests quickly while interacting with a simple ASP.NET Web API as the webhook receiver.
 
-You will use plain HTTP requests, which is useful for helping you to understand how webhooks work.  
+You will use plain HTTP requests, which is useful for helping you understand how webhooks work.  
 
 To complete the step-by-step instructions in this article, download and install the following tools:
 
 * [Google Chrome Browser](http://google.com/chrome)
 * [Postman](https://www.getpostman.com/)
 * [Visual Studio Community Edition](https://go.microsoft.com/fwlink/?LinkId=691978&clcid=0x409)
 * [ngrok](https://ngrok.com/) (to install ngrok, see [Download and Installation](https://ngrok.com/download))
-* An Office 365 subscription with SharePoint Online. If you are new to Office 365, you can also [sign up for an Office 365 developer account](http://dev.office.com/devprogram).
+* An Office 365 developer subscription with SharePoint Online. If you are new to Office 365, you can also [sign up for an Office 365 developer subscription through the Office 365 Developer Program](https://developer.microsoft.com/en-us/office/dev-program). See the [Office 365 Developer Program documentation](https://docs.microsoft.com/en-us/office/developer-program/office-365-developer-program) for step-by-step instructions about how to join the Office 365 Developer Program and sign up and configure your subscription.
 
 ## Step 1: Register an Azure AD application for Postman client
 

docs/general-development/sharepoint-server-application-lifecycle-management.md

@@ -128,7 +128,7 @@ Figure 2 shows how developers can use Office 365 as a development environment an
 
 
 
-Developers with MSDN subscriptions can obtain a development tenant that contains aSharePointDeveloper Site. The SharePointDeveloper Site is preconfigured for developing applications. Users can use not only Visual Studio 2012 in developing applications, but with Office 365 developer sites, Napa can be used within the site to construct applications. For more information about getting started with anOffice 365 Developer Site, see  [Set up a development environment for SharePoint Add-ins on Office 365](http://msdn.microsoft.com/library/b22ce52a-ae9e-4831-9b68-c9210af6dc54%28Office.15%29.aspx).
+Developers with MSDN subscriptions can obtain a development tenant that contains a SharePoint developer site. The SharePointDeveloper Site is preconfigured for developing applications. Users can use not only Visual Studio 2012 in developing applications, but with Office 365 developer sites, Napa can be used within the site to construct applications. For more information about getting started with an Office 365 developer site, see [Set up a development environment for SharePoint Add-ins on Office 365](../sp-add-ins/set-up-a-development-environment-for-sharepoint-add-ins-on-office-365.md).
 
 
 

docs/solution-guidance/Use-remote-event-receivers-in-SharePoint.md

@@ -41,7 +41,7 @@ Before you run this add-in, do the following:
 
 	3. Verify that  **Scope** is set to **Web**, and  **Permission** is set to **Manage**.
 
-3. To run this code sample, you need an Azure subscription. To sign up for a trial, see  [Free one-month trial](http://azure.microsoft.com/en-us/pricing/free-trial/).
+3. To run this code sample, you need an Azure subscription. To sign up for a trial, see [Free one-month trial](http://azure.microsoft.com/en-us/pricing/free-trial/).
 
 4. Create an Azure Service Bus Namespace with ACS Support.
 

docs/solution-guidance/onedrive-for-business-customization-sharepoint-add-in.md

@@ -122,7 +122,7 @@ Enhanced app part based customization
 
 Here's more detailed description of enhanced app part based customizations, which seems to be the typical approach for applying and managing needed customizations to the OD4B sites. Source code and additional details on this solution is available from the [Office 365 Developer Patterns and Practices guidance](http://aka.ms/officedevpnp).
 
-Actual logical design follows the hidden app part approach, mentioned before in [this blog post](http://blogs.msdn.com/b/vesku/archive/2013/11/25/office365-apply-automatically-custom-branding-to-personal-site-skydrive-pro.aspx). This means that the assumption is that you have centralized Intranet in the office 365 environment where you can put the needed app part and that the end users will be landing to this welcome page when they open up their browser. It is common that each company browser will have same home page set using group policies, so that end users will always start from one centralized ___location when they open up their browser. This is the ___location where you’d put app part, which can be set to be sized as 0 pixel width and height. Key point here is that you use the end user context to execute the app part, which contains page from the provider hosted add-in.
+Actual logical design follows the hidden app part approach, mentioned before in [this blog post](http://blogs.msdn.com/b/vesku/archive/2013/11/25/office365-apply-automatically-custom-branding-to-personal-site-skydrive-pro.aspx). This means that the assumption is that you have centralized Intranet in the Office 365 environment where you can put the needed app part and that the end users will be landing to this welcome page when they open up their browser. It is common that each company browser will have same home page set using group policies, so that end users will always start from one centralized ___location when they open up their browser. This is the ___location where you’d put app part, which can be set to be sized as 0 pixel width and height. Key point here is that you use the end user context to execute the app part, which contains page from the provider hosted add-in.
 
 **Performance optimization and maintenance considerations**
 

docs/sp-add-ins/create-a-developer-site-on-an-existing-office-365-subscription.md

@@ -1,37 +1,37 @@
 ---
 title: Create a developer site on an existing Office 365 subscription
-description: Set up an Office 365 Developer Site for SharePoint Add-ins.
-ms.date: 11/03/2017
+description: Set up an Office 365 developer site for SharePoint Add-ins.
+ms.date: 03/09/2018
 ms.prod: sharepoint
 ---
 
 
 # Create a developer site on an existing Office 365 subscription
 
-An Office 365 Developer Site makes it easier to get set up and start creating, testing, and deploying your Office and SharePoint Add-ins more quickly. Many Office 365 Business, Enterprise, Education, and Government subscriptions include a site template that you can use to create a Developer Site.
+An Office 365 developer site makes it easier to get set up and start creating, testing, and deploying your Office and SharePoint Add-ins more quickly. Many Office 365 Business, Enterprise, Education, and Government subscriptions include a site template that you can use to create a developer site.
 
 ### Before you start
 
-**Be sure you have an Office 365 subscription that supports a Developer Site.** If you have one of the following Office 365 subscription plans, you can create a Developer Site within your existing subscription:
+**Be sure you have an Office 365 subscription that supports a developer site.** If you have one of the following Office 365 subscription plans, you can create a developer site within your existing subscription:
 
 - Office 365 Midsize Business
 - Office 365 Enterprise E1, E3, E4, E5, or K1
 - Office 365 Education A2, A3, or A4
 - Office 365 Government G1, G3, G4, or K1
 
-**If you have an Office 365 Small Business subscription,** it supports only a single site collection, so you can't create a Developer Site collection. If you would like to learn more about Office 365 plans for your business, see [SharePoint Online: software boundaries and limits](http://office.microsoft.com/en-us/office365-sharepoint-online-enterprise-help/sharepoint-online-software-boundaries-and-limits-HA102694293.aspx).
+**If you have an Office 365 Small Business subscription,** it supports only a single site collection, so you can't create a developer site collection. If you would like to learn more about Office 365 plans for your business, see [SharePoint Online: software boundaries and limits](http://office.microsoft.com/en-us/office365-sharepoint-online-enterprise-help/sharepoint-online-software-boundaries-and-limits-HA102694293.aspx).
 
 For more information about the Office 365 Enterprise offerings, see [Plans & Pricing](http://products.office.com/en-us/business/office-365-enterprise-e1-business-software).
 
 <a name="bk_createdevsite"> </a>
-## Create a Developer Site
+## Create a developer site
 
 1. Sign in to Office 365 as a Global or SharePoint Online admin.
 
-   **You must sign in as a Global or SharePoint Online admin to create new site collections,** such as a Developer Site. Only admins can see Admin options when signing in to Office 365. If you're not an admin, contact an admin in your company and have them do one of the following:
+   **You must sign in as a Global or SharePoint Online admin to create new site collections,** such as a developer site. Only admins can see Admin options when signing in to Office 365. If you're not an admin, contact an admin in your company and have them do one of the following:
 
-   - Grant you admin rights, so you can create the Developer Site yourself.
-   - Create the Developer Site for you, and specify you as an admin for the site collection.
+   - Grant you admin rights, so you can create the developer site yourself.
+   - Create the developer site for you, and specify you as an admin for the site collection.
 
 2. Select the App Launcher button on the far left of the navigation bar at the top of the page.
 
@@ -40,27 +40,23 @@ For more information about the Office 365 Enterprise offerings, see [Plans &amp;
 4. In the navigation tree on the left, expand **Admin**, and then select **SharePoint**.
 
 5. In the **SharePoint admin center**, on the **Site Collections** tab, select **New** > **Private Site Collection**.
-  
-   *Figure 1. SharePoint Admin Center new site collection option*
 
    ![SharePoint Admin Center new site collection option](../images/SPAdminCenter_newSiteCollection.png)
 
-6. In the **New Site Collection** dialog box, provide information about your Developer Site.
+6. In the **New Site Collection** dialog box, provide information about your developer site.
 
    |**Field**|**Value**|
    |:-----|:-----|
-   |**Title**|The name you want to give your Developer Site.|
+   |**Title**|The name you want to give your developer site.|
    |**Public Website Address** list|A ___domain name and a URL path—either **/sites/** or **/teams/**—and then<br/>type a URL name for the site collection.|
-   |**Select a language** list in the **Template Selection** section|A primary language to use for your Developer Site.<br/>*Be sure to select the appropriate language for the Developer Site site collection, because once you choose it, it can't be changed.*<br/>Selecting a language for your Developer Site does not affect the languages you can make available in your Office and SharePoint Add-ins.<br/>You can enable the SharePoint multiple language interface on your sites, but the primary language for the site collection is the one you choose here.|
+   |**Select a language** list in the **Template Selection** section|A primary language to use for your developer site.<br/>*Be sure to select the appropriate language for the developer site site collection, because once you choose it, it can't be changed.*<br/>Selecting a language for your developer site does not affect the languages you can make available in your Office and SharePoint Add-ins.<br/>You can enable the SharePoint multiple language interface on your sites, but the primary language for the site collection is the one you choose here.|
    |**Template Selection** section, on the **Collaboration** tab under **Select a template**|Select **Developer Site.**|
-   |**Time Zone**|Time zone that's appropriate for the locale of your Developer Site.|
+   |**Time Zone**|Time zone that's appropriate for the locale of your developer site.|
    |**Administrator**|The user name of your site collection administrator.|
-   |**Storage Quota**|Number of megabytes (MB) you want to allocate to this Developer Site site collection.|
+   |**Storage Quota**|Number of megabytes (MB) you want to allocate to this developer site site collection.|
    |**Server Resource Quota**|The amount of resources to allocate to the site collection.<br/>This number is a combination of performance metrics (such as processor time and unhandled exceptions) that pertain to code in sandboxed solutions.<br/>When the level exceeds a daily quota, the sandbox is turned off for this site collection.|
 
-7. Select **OK**. You'll see the new developer site URL in the **Site Collections** list. When the site creation is finished, you can go to the URL to open your Developer Site.
-    
-   *Figure 2. New site collection provisioning*
+7. Select **OK**. You'll see the new developer site URL in the **Site Collections** list. When the site creation is finished, you can go to the URL to open your developer site.
 
    ![New site collection provisioning](../images/SPAdminCenter_newSiteCollection_provisioning.png)