Final edit pass Develop sp-add-ins (SharePoint#1191)

* Final edit

* Final edit

* Final edit

* Final edit

* Final edit

* Final edit

* Final edit

Author: Linda-Editor

docs/sp-add-ins/add-in-permissions-in-sharepoint.md

@@ -9,7 +9,7 @@ ms.prod: sharepoint
 
 Before you read this article, you should first be familiar with the topic [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md). 
 
-A SharePoint Add-in requests the permissions that it needs during installation from the user who is installing it. The developer of an add-in must request, through the add-in manifest file, the permissions that the particular add-in needs to be able to run. (Device and web apps that access SharePoint, but are not installed to SharePoint websites, must be granted permissions at runtime by the user who is executing the add-in. For more information, see [Get an overview of add-ins that request access permission from SharePoint on the fly](authorization-code-oauth-flow-for-sharepoint-add-ins.md#Overview).)
+A SharePoint Add-in requests the permissions that it needs during installation from the user who is installing it. The developer of an add-in must request, through the add-in manifest file, the permissions that the particular add-in needs to be able to run. (Device and web apps that access SharePoint, but are not installed to SharePoint websites, must be granted permissions at runtime by the user who is executing the add-in. For more information, see [Authorization Code OAuth flow for SharePoint Add-ins](authorization-code-oauth-flow-for-sharepoint-add-ins.md).)
 
 Users can grant only the permissions that they have. The user must grant all the permissions that an add-in requests or not grant any permission. Selective grants are not possible. (For add-ins that request permissions on the fly, only a user with Manage permissions to the SharePoint resources that the add-in seeks to access can run the add-in, even if the add-in is asking only for lesser permissions, such as Read.)
 

docs/sp-add-ins/authorization-code-oauth-flow-for-sharepoint-add-ins.md

@@ -274,5 +274,8 @@ The free  [Fiddler tool](http://www.telerik.com/fiddler) can be used to capture
 
 
 -  [OAuth 2.0](http://oauth.net/2/)
+
+- [Creating SharePoint Add-ins that use high-trust authorization](creating-sharepoint-add-ins-that-use-high-trust-authorization.md)
+- [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md)
 
 

docs/sp-add-ins/context-token-oauth-flow-for-sharepoint-add-ins.md

@@ -511,6 +511,8 @@ When you are debugging in Visual Studio with  **F5**, Microsoft Office Developer
 
 
 -  [Get started creating provider-hosted SharePoint Add-ins](get-started-creating-provider-hosted-sharepoint-add-ins.md)
+- [Creating SharePoint Add-ins that use high-trust authorization](creating-sharepoint-add-ins-that-use-high-trust-authorization.md)
+- [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md)
 
 
 

docs/sp-add-ins/create-and-use-access-tokens-in-provider-hosted-high-trust-sharepoint-add-ins.md

@@ -139,6 +139,11 @@ In connection with this point, note the following:
 <a name="DomainRelatedErrors"> </a>
 
 If you are sure you have the correct certificate serial number in the web.config and you can see the certificate in the  **Windows Certificate Store**, then there may be a hidden extra character in the serial number in the web.config. This will happen if the serial number is copy'n'pasted from the **Microsoft Management Console**. Delete the entire serial number value from the web.config and *manually*  retype it.
+
+## See also
+
+- [Creating SharePoint Add-ins that use high-trust authorization](creating-sharepoint-add-ins-that-use-high-trust-authorization.md)
+- [Authorization and authentication of SharePoint Add-ins](authorization-and-authentication-of-sharepoint-add-ins.md)