Final edit pass through sp-dev-docs (SharePoint#1145)

* Fixed YAML header

* Updated Develop Overview topic

* Final edit

* Final edit

* Final edit

* Final edit

* Final edit

* Final edit

* Final edit

* Final edit

* Final edit

* Final edit

* Final edit

* Removed md from dev.office.com links

Author: Linda-Editor

docs/declarative-customization/site-theming/sharepoint-site-theming-rest-api.md

@@ -2,12 +2,12 @@
 
 You can use the the SharePoint REST interface to perform basic create, read, update, and delete (CRUD) operations on site themes.
 
-The SharePoint Online (and SharePoint 2016 and later on-premises) REST service supports combining multiple requests into a single call to the service by using the OData $batch query option. For details and links to code samples, see [Make batch requests with the REST APIs](https://dev.office.com/sharepoint/docs/apis/rest/make-batch-requests-with-the-rest-apis.md).
+The SharePoint Online (and SharePoint 2016 and later on-premises) REST service supports combining multiple requests into a single call to the service by using the OData $batch query option. For details and links to code samples, see [Make batch requests with the REST APIs](https://dev.office.com/sharepoint/docs/apis/rest/make-batch-requests-with-the-rest-apis).
 
 ## Prerequisites
 Before you get started, make sure that you're familiar with the following:
-- [Get to know the SharePoint REST service](https://dev.office.com/sharepoint/docs/apis/rest/get-to-know-the-sharepoint-rest-service.md) 
-- [Complete basic operations using SharePoint REST endpoints](https://dev.office.com/sharepoint/docs/apis/rest/complete-basic-operations-using-sharepoint-rest-endpoints.md)
+- [Get to know the SharePoint REST service](https://dev.office.com/sharepoint/docs/apis/rest/get-to-know-the-sharepoint-rest-service) 
+- [Complete basic operations using SharePoint REST endpoints](https://dev.office.com/sharepoint/docs/apis/rest/complete-basic-operations-using-sharepoint-rest-endpoints)
 
 ## REST commands for site themes
 
@@ -131,6 +131,6 @@ RestRequest("/_api/thememanager/GetTenantThemingOptions");
 * [SharePoint site theming: JSON schema](sharepoint-site-theming-json-schema.md)
 * [SharePoint site theming: PowerShell cmdlets](sharepoint-site-theming-powershell.md)
 * [SharePoint site theming: CSOM](sharepoint-site-theming-csom.md)
-* [Complete basic operations using SharePoint REST endpoints](https://dev.office.com/sharepoint/docs/apis/rest/complete-basic-operations-using-sharepoint-rest-endpoints.md)
+* [Complete basic operations using SharePoint REST endpoints](https://dev.office.com/sharepoint/docs/apis/rest/complete-basic-operations-using-sharepoint-rest-endpoints)
 * [Making REST calls with C# and JavaScript for SharePoint 2013](http://www.microsoft.com/resources/msdn/en-us/office/media/video/video.mdl?cid=sdc&from=mscomsdc&VideoID=4e4cc094-ff69-405b-852f-2ac7c41293c5)
 

docs/sp-add-ins/access-sharepoint-data-from-add-ins-using-the-cross-___domain-library.md

@@ -1,4 +1,4 @@
----
+---
 title: Access SharePoint data from add-ins using the cross-___domain library
 ms.date: 09/25/2017
 ms.prod: sharepoint

docs/sp-add-ins/complete-basic-operations-using-javascript-library-code-in-sharepoint.md

@@ -115,7 +115,7 @@ Use  `_api` to denote the SharePoint REST service in your endpoint URIs. The RES
 
 ### Specify entry points for the SharePoint REST service
 
-The main entry points for the REST service represent the site collection and site of the specified context. In this way, these entry points correspond to the  **ClientContext.Site** property and **ClientContext.Web** property in the client object models.
+The main entry points for the REST service represent the site collection and site of the specified context. In this way, these entry points correspond to the **ClientContext.Site** property and **ClientContext.Web** property in the client object models.
 
 
 
@@ -207,11 +207,11 @@ The following figure shows the SharePoint REST parameter syntax.
 
 ### Complex types as parameters for the REST service
 
-Some methods in the client object model require a large payload as a parameter. For REST endpoints to maintain functionality parity with their corresponding client object model APIs, the endpoints must accept a complex type as a parameter. In these cases, the REST service extends the existing OData protocol to enable these REST endpoints to accept a single complex type as a parameter. This applies to  **POST** operations only, and you have to pass the complex type in [Atom](http://www.odata.org/developers/protocols/atom-format#RepresentingComplexTypesProperties) format or [JSON](http://www.odata.org/developers/protocols/json-format#RepresentingComplexTypeProperties) format, according to OData standards.
+Some methods in the client object model require a large payload as a parameter. For REST endpoints to maintain functionality parity with their corresponding client object model APIs, the endpoints must accept a complex type as a parameter. In these cases, the REST service extends the existing OData protocol to enable these REST endpoints to accept a single complex type as a parameter. This applies to **POST** operations only, and you have to pass the complex type in [Atom](http://www.odata.org/developers/protocols/atom-format#RepresentingComplexTypesProperties) format or [JSON](http://www.odata.org/developers/protocols/json-format#RepresentingComplexTypeProperties) format, according to OData standards.
 
 
 
-For example, the  **ListCollection.Add** method takes a **Microsoft.SharePoint.Client.ListCreationInformation** object as a parameter. To add a list to a specified site, construct the appropriate REST endpoint as follows:
+For example, the **ListCollection.Add** method takes a **Microsoft.SharePoint.Client.ListCreationInformation** object as a parameter. To add a list to a specified site, construct the appropriate REST endpoint as follows:
 
 
 
@@ -312,13 +312,13 @@ A  `Dictionary<String, object>` is represented as a multi-value object, named Ke
 
 
 
--  **Key** The key of the multi-value object.
+- **Key** The key of the multi-value object.
 
 
--  **Value** The value of the object
+- **Value** The value of the object
 
 
--  **ValueType** The value type of the object. For simple value types that map to existing Entity Data Model (EDM) types, the REST service returns the appropriate EDM type string; for example, "Edm.String." If not, the REST service returns the value type returned by the **Type.ToString** function.
+- **ValueType** The value type of the object. For simple value types that map to existing Entity Data Model (EDM) types, the REST service returns the appropriate EDM type string; for example, "Edm.String." If not, the REST service returns the value type returned by the **Type.ToString** function.
 
 
 
@@ -359,7 +359,7 @@ To construct URIs that correspond to static methods or properties, use the corre
 
 
 
-However, static properties can be accessed only directly, and are not allowed as part of a larger URI composition. For example, directly accessing the  **SP.Utility.AssetsLibrary** method in REST is allowable, as follows:
+However, static properties can be accessed only directly, and are not allowed as part of a larger URI composition. For example, directly accessing the **SP.Utility.AssetsLibrary** method in REST is allowable, as follows:
 
 
 
@@ -402,8 +402,7 @@ If you want to select, filter, or order the data you requested from an endpoint,
 ## See also
 <a name="bk_addresources"> </a>
 
-
--  [Get to know the SharePoint REST service](get-to-know-the-sharepoint-rest-service.md)
+- [Get to know the SharePoint REST service](get-to-know-the-sharepoint-rest-service.md)
 
 
 -  [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-rest-endpoints.md)

docs/sp-add-ins/complete-basic-operations-using-sharepoint-client-library-code.md

@@ -1,19 +1,20 @@
 ---
 title: Develop SharePoint Add-ins
-ms.date: 09/25/2017
+description: In-depth articles and resources to help you build advanced capabilities into your SharePoint Add-ins.
+ms.date: 12/13/2017
 ms.prod: sharepoint
 ---
 
 
 # Develop SharePoint Add-ins
+
 Find in-depth articles and resources to help you build advanced capabilities into your SharePoint Add-ins.
 
 
 > [!NOTE]
-> This article assumes that you are familiar with the article  [SharePoint Add-ins](sharepoint-add-ins.md) and the getting started material that it links to.
-
-Under  **Develop**, we've got the following to help explain all the different things you can do in a SharePoint Add-in:
+> This article assumes that you are familiar with the article [SharePoint Add-ins](sharepoint-add-ins.md) and the getting started material that it links to.
 
+Under **Develop**, we've got the following to help explain all the different things you can do in a SharePoint Add-in:
 
 - In-depth overviews
 - How-to articles
@@ -26,33 +27,35 @@ You'll find articles about:
 - How to build REST queries and interact with the new APIs
 - How and when to configure OAuth for security
 
-SharePoint has enterprise social features like activity feeds and user profiles, along with enterprise content management features, line-of-business (LOB) interoperability features, and website design features that can really make your add-ins stand out. Learn more about them in  [Add SharePoint capabilities](http://msdn.microsoft.com/library/11ecb65e-6dc5-4cf1-80ca-3c16418697b6%28Office.15%29.aspx).
+SharePoint has enterprise social features such as activity feeds and user profiles, along with enterprise content management features, line-of-business (LOB) interoperability features, and website design features that can really make your add-ins stand out. Learn more about them in [Add SharePoint capabilities](../general-development/add-sharepoint-capabilities.md).
 
 And, code is key, so take a look at the "Samples" menu in the Dev Center. It's a direct link to our code samples for add-ins. As soon as you've set up your development environment, you should check out a few of our samples. Take advantage of a community feature that lets you request a code sample if we don't have one you'd like to see. We take those requests, along with other doc feedback and use them in our continuous updates to the content and samples. So please, let us know if you'd like to see something!
 
-## Get started with SharePoint Add-ins resources
 <a name="bk_gettingstarted"> </a>
 
-If you're just getting started with developing SharePoint Add-ins, first take a look a  [SharePoint Add-ins](sharepoint-add-ins.md). That page points you to key articles to get you acquainted quickly with the different kinds of SharePoint Add-ins. Before doing more advanced kinds of development with SharePoint Add-ins, you should start with a good idea of the kinds of add-ins that you want to build, the technologies that you will want to include, and the hosting options that you will want to use.
- 
-### Essential tasks and resources for developing SharePoint Add-ins using the client object model, JavaScript object model, and REST endpoints in SharePoint
+## Get started with SharePoint Add-ins resources
+
+If you're just getting started with developing SharePoint Add-ins, first take a look at [SharePoint Add-ins](sharepoint-add-ins.md). That page points you to key articles to get you acquainted quickly with the different kinds of SharePoint Add-ins. Before doing more advanced kinds of development with SharePoint Add-ins, you should start with a good idea of the kinds of add-ins that you want to build, the technologies that you want to include, and the hosting options that you want to use.
+
 <a name="bk_essentials"> </a>
 
+### Essential tasks and resources for developing SharePoint Add-ins using the client object model, JavaScript object model, and REST endpoints in SharePoint
+
 No matter what kind of SharePoint Add-in you decide to build, your add-in will always interact in some way with a SharePoint site. The articles in Table 1 describe how to do many of the most important kinds of work with SharePoint sites by using three interfaces that are available for you to use in your SharePoint Add-ins: the client object model, the JavaScript object model, and REST endpoints.
 
 **Table 1. Basic operations with the SharePoint client object model, JavaScript object model, and REST interface**
 
-
 |**Topic**|**Description**|
 |:-----|:-----|
 | [Complete basic operations using SharePoint client library code](complete-basic-operations-using-sharepoint-client-library-code.md)|Explains how to do common operations by using C# and the client object model.|
 | [Complete basic operations using JavaScript library code in SharePoint](complete-basic-operations-using-javascript-library-code-in-sharepoint.md)|Explains how to do common operations by using the JavaScript object model.|
 | [Complete basic operations using SharePoint REST endpoints](complete-basic-operations-using-sharepoint-rest-endpoints.md)|Explains how to do common operations by using the REST interface.|
 
-## Learn the fundamental concepts for development with SharePoint Add-ins
 <a name="bk_fundamentals"> </a>
 
-In addition to understanding the basic operations, you should understand the fundamental concepts of the SharePoint add-in development model. Every kind of SharePoint Add-in contains an add-in manifest file and is built into an add-in package that you deploy to a SharePoint site. And when you develop any kind of add-in you must consider a range of issues related to authentication and authorization, data access, and usability. The articles in Table 2 acquaint you with these issues and explain their implications for any kind of that you want to create.
+## Learn the fundamental concepts for development with SharePoint Add-ins
+
+In addition to understanding the basic operations, you should understand the fundamental concepts of the SharePoint add-in development model. Every kind of SharePoint Add-in contains an add-in manifest file and is built into an add-in package that you deploy to a SharePoint site. When you develop any kind of add-in, you must consider a range of issues related to authentication and authorization, data access, and usability. The articles in Table 2 acquaint you with these issues and explain their implications for any kind of add-in that you want to create.
 
 **Table 2. Fundamental concepts for working with SharePoint Add-ins**
 
@@ -62,11 +65,12 @@ In addition to understanding the basic operations, you should understand the fun
 | [Explore the app manifest structure and the package of a SharePoint Add-in](explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in.md)|Explains how add-in manifests work and how add-in packages are built.|
 | [Create UX components in SharePoint](create-ux-components-in-sharepoint.md)|Explores the ways in which you can build a rich user experience in SharePoint Add-ins.|
 | [Work with external data in SharePoint](work-with-external-data-in-sharepoint.md)|Explains the data access options and techniques that are available in different kinds of SharePoint Add-ins.|
-| [License your Office and SharePoint Add-ins](http://msdn.microsoft.com/library/license-your-office-and-sharepoint-add-ins%28Office.15%29.aspx)|Guides you through the add-in license framework for Office and SharePoint Add-ins.|
+| [License your Office and SharePoint Add-ins](https://docs.microsoft.com/en-us/office/dev/store/license-your-add-ins)|Guides you through the add-in license framework for Office and SharePoint Add-ins.|
 
-## Put the pieces together: Building advanced SharePoint Add-ins by integrating capabilities
 <a name="bk_integrate"> </a>
 
+## Put the pieces together: Building advanced SharePoint Add-ins by integrating capabilities
+
 When you are familiar with the capabilities and features of SharePoint Add-ins, you can start building more complex add-ins by putting all of the pieces together in ways that suit your requirements. The articles in Table 3 demonstrate how to integrate capabilities and create more fully featured SharePoint Add-ins.
 
 **Table 3. Advanced concepts in SharePoint Add-ins**