Updated Note formatting

Author: Linda Caputo

docs/apis/rest/complete-basic-operations-using-sharepoint-rest-endpoints.md

@@ -224,7 +224,8 @@ When you send a POST request, the request must include the form digest value in
 
 Cloud-hosted add-ins use either OAuth or the cross-___domain library to authorize access to SharePoint data. Add-in components with code that runs on a remote web server must use OAuth to authorize access to SharePoint data. In this case, you need to include an  **Authorization** header to send the access token. See [Reading data with the SharePoint REST interface](complete-basic-operations-using-sharepoint-rest-endpoints.md#ReadingData) for an example that adds an authorization header to an **HTTPWebRequest** object.
 
- **Note**  Cloud-hosted add-in components that are written in JavaScript must use the  **SP.RequestExecutor** object in the cross-___domain library to access to SharePoint data. Cross-___domain library requests don't need to include an access token.
+> [!NOTE]
+> Cloud-hosted add-in components that are written in JavaScript must use the  **SP.RequestExecutor** object in the cross-___domain library to access to SharePoint data. Cross-___domain library requests don't need to include an access token.
  
 To learn more about OAuth access tokens and how to get them, see  [Context Token OAuth flow for SharePoint Add-ins](https://msdn.microsoft.com/en-us/library/office/fp142382.aspx) and [Authorization Code OAuth flow for SharePoint Add-ins](https://msdn.microsoft.com/en-us/library/office/jj687470.aspx).
 
@@ -237,7 +238,8 @@ Requests are sent to the resource endpoint that's specified in the  **url** prop
 
 Cross-___domain library requests use this format when they access data on the add-in web, which is the default context for cross-___domain library requests. But to access data on the host web or on another site collection, the requests need to initialize the host web or other site collection as the context. To do this, they use the  **SP.AppContextSite** endpoint in the URI, as shown in Table 1. The example URIs in Table 1 use the **@target** alias to send the target URL in the query string because the URL contains a special character (':').
 
- **Note**  An add-in web instance is required for a cloud-hosted add-in to access SharePoint data when using the cross-___domain library.
+> [!NOTE]
+> An add-in web instance is required for a cloud-hosted add-in to access SharePoint data when using the cross-___domain library.
 
 **Table 1. Using the SP.AppContextSite endpoint to change the context of the request**
 
@@ -248,7 +250,8 @@ Cross-___domain library requests use this format when they access data on the add-i
 |Cloud-hosted|JavaScript add-in component accessing data in a site collection other than the host web by using the cross-___domain library (tenant-scoped add-ins only)| _<app web url>_/_api/SP.AppContextSite(@target)/web/title?@target=' _<target site url>_'|
 |SharePoint-hosted|Add-in web component accessing data in another site collection (tenant-scoped add-ins only)| _<app web url>_/_api/SP.AppContextSite(@target)/web/title?@target=' _<target site url>_'|
 
- **Note**  Cross-___domain data access scenarios also require appropriate add-in permissions. For more information, see  [Access data from the host web](https://msdn.microsoft.com/en-us/library/office/fp179927.aspx#SP15Accessdatafromremoteapp_Hostweb) and [Access data across site collections](https://msdn.microsoft.com/en-us/library/office/fp179927.aspx#SP15Accessdatafromremoteapp_TenantScope).
+> [!NOTE]
+> Cross-___domain data access scenarios also require appropriate add-in permissions. For more information, see  [Access data from the host web](https://msdn.microsoft.com/en-us/library/office/fp179927.aspx#SP15Accessdatafromremoteapp_Hostweb) and [Access data across site collections](https://msdn.microsoft.com/en-us/library/office/fp179927.aspx#SP15Accessdatafromremoteapp_TenantScope).
 
 SharePoint Add-ins can get the add-in web URL and host web URL from the query string of the add-in page, as shown in the following code example. The example also shows how to reference the cross-___domain library, which is defined in the SP.RequestExecutor.js file on the host web. The example assumes that your add-in launches from SharePoint. See  [Authorization Code OAuth flow for SharePoint Add-ins](https://msdn.microsoft.com/en-us/library/office/jj687470.aspx) for guidance on setting your SharePoint context correctly when your add-in does not launch from SharePoint.
 

docs/apis/rest/upload-a-file-by-using-the-rest-api-and-jquery.md

@@ -26,7 +26,8 @@ This process uses the following high-level steps:
 <a name="RunTheExamples"> </a>
 Both code examples in this article use the REST API and jQuery AJAX requests to upload a file to the  **Shared Documents** folder and then change list item properties. The first example uses **SP.AppContextSite** to make calls across SharePoint domains, like a SharePoint-hosted add-in would do when uploading files to the host web. The second example makes same-___domain calls, like a SharePoint-hosted add-in would do when uploading files to the add-in web, or a solution that's running on the server would do when uploading files.
 
- **Note**  Provider-hosted add-ins written in JavaScript must use the SP.RequestExecutor cross-___domain library to send requests to a SharePoint ___domain. For an example, see  [upload a file by using the cross-___domain library](http://msdn.microsoft.com/library/2c3d2545-1cd7-497e-b535-12199d8edfbb%28Office.15%29.aspx#bk_FileCollectionAdd).
+> [!NOTE]
+> Provider-hosted add-ins written in JavaScript must use the SP.RequestExecutor cross-___domain library to send requests to a SharePoint ___domain. For an example, see  [upload a file by using the cross-___domain library](http://msdn.microsoft.com/library/2c3d2545-1cd7-497e-b535-12199d8edfbb%28Office.15%29.aspx#bk_FileCollectionAdd).
  
 To use the examples in this article, you'll need the following:
 

docs/apis/rest/use-odata-query-operations-in-sharepoint-rest-requests.md

@@ -20,7 +20,8 @@ The SharePoint REST service supports a wide range of OData query string operator
 ## Select fields to return
 Use the  [$select](http://www.odata.org/documentation/odata-version-2-0/uri-conventions#SelectSystemQueryOption) query option to specify which fields to return for a given list, list item, or other SharePoint object represented by an entity set. You can use `$select=*` to return all available fields.
 
- **Note**  In general, if you do not specify the  `$select` query option, the REST service returns all available fields by default. However, in a few cases, some SharePoint objects include properties that are very resource intensive to retrieve; to optimize REST service performance, these properties are not included in the default query, and must be explicitly requested.For example, the  **SPWeb.EffectiveBasePermissions** property is not returned by default, and must be explicitly requested using the `$select` query option.
+> [!NOTE]
+> In general, if you do not specify the  `$select` query option, the REST service returns all available fields by default. However, in a few cases, some SharePoint objects include properties that are very resource intensive to retrieve; to optimize REST service performance, these properties are not included in the default query, and must be explicitly requested.For example, the  **SPWeb.EffectiveBasePermissions** property is not returned by default, and must be explicitly requested using the `$select` query option.
  
 In addition, you can specify that the request returns projected fields from other lists and the values of lookups. To do this, specify the field name in both the  `$select` and `$expand` query options. For example:
 
@@ -37,7 +38,8 @@ Single value lookup fields are represented by two separate fields in the SharePo
 ## Query for users
 In the SharePoint REST service, users are represented by the user's friendly (display) name, and not their alias or ___domain\alias combination. Therefore, you must construct user queries against users' friendly names.
 
- **Note**  Membership-based user queries are not supported.Usage of the  **Current** operator to do queries using the ID of the current user is not supported.
+> [!NOTE]
+> Membership-based user queries are not supported.Usage of the  **Current** operator to do queries using the ID of the current user is not supported.
 
 ## Query for multi-value lookup fields and users
 Because multi-value lookup fields are returned as a string of multiple values, there is no way to query for them (for example, the equivalent of an  **Includes** element or **NotIncludes** element is not supported).
@@ -48,7 +50,8 @@ Use the  [$orderby](http://www.odata.org/documentation/odata-version-2-0/uri-con
 ## Page through returned items
 Use the  [$top](http://www.odata.org/documentation/odata-version-2-0/uri-conventions#TopSystemQueryOption) and [$skiptoken](http://msdn.microsoft.com/library/dd942121.aspx) query options to select a subset of the items that would otherwise be returned by your query.
 
- **Note**  The $skip query option does not work with queries for SharePoint list items.
+> [!NOTE]
+> The $skip query option does not work with queries for SharePoint list items.
 
 The  `$top` option enables you to select the first *n*  items of the return set for return. For example, the following URI requests that only the first ten items in the prospective return set actually be returned:
 
@@ -58,7 +61,8 @@ The $skiptoken option enables you to skip over items until the specified item is
 
  `$skiptoken=Paged=TRUE&p_ID=5`
 
- **Note**  When using these query options, take into account that paging in OData is ordinal. For example, suppose you are implementing a next page button to display SharePoint list items. You use the REST service to enable the button to return items 1 through 20 when clicked, then items 21 through 40, and so on. However, suppose another user deletes items 4 and 18 between clicks of the next button. In such a case, the ordinal positioning of the remaining items is reset, and displaying items 21 through 40 actually skips over two items.
+> [!NOTE]
+> When using these query options, take into account that paging in OData is ordinal. For example, suppose you are implementing a next page button to display SharePoint list items. You use the REST service to enable the button to return items 1 through 20 when clicked, then items 21 through 40, and so on. However, suppose another user deletes items 4 and 18 between clicks of the next button. In such a case, the ordinal positioning of the remaining items is reset, and displaying items 21 through 40 actually skips over two items.
  
 ## OData query operators supported in the SharePoint REST service
 <a name="bk_supported"> </a>

docs/apis/rest/working-with-folders-and-files-with-rest.md

@@ -121,7 +121,8 @@ Headers:
 
 The following example shows how to  **update** a file by using the **PUT** method.
 
- **Note**   **PUT** is the only method that you can use to update a file. The **MERGE** method is not allowed.
+> [!NOTE]
+> **PUT** is the only method that you can use to update a file. The **MERGE** method is not allowed.
 
 ```
 url: http://site url/_api/web/GetFileByServerRelativeUrl('/Folder Name/file name')/$value
@@ -248,7 +249,8 @@ headers:
 
 The following example shows how to  **update** a file attachment to a list item by using the **PUT** method.
 
- **Note**   **PUT** is the only method that you can use to update a file. The **MERGE** method is not allowed.
+> [!NOTE]
+> **PUT** is the only method that you can use to update a file. The **MERGE** method is not allowed.
  
 ```
 url: http://site url/_api/web/lists/getbytitle('list title')/items(item id)/AttachmentFiles('file name')/$value

docs/apis/rest/working-with-lists-and-list-items-with-rest.md

@@ -25,7 +25,8 @@ Headers:
     accept: "application/json;odata=verbose" or "application/atom+xml"
 
 ```
- **Note**  Use  `application/json;odata=verbose` in the `accept` header if you want the response in JSON. Use `application/atom+xml` in the `accept` header if you want the response in Atom format.
+> [!NOTE]
+> Use  `application/json;odata=verbose` in the `accept` header if you want the response in JSON. Use `application/atom+xml` in the `accept` header if you want the response in Atom format.
  
 The following example shows how to  **retrieve** a specific list if you know its title.
 
@@ -82,7 +83,8 @@ The following XML shows an example of the list properties that are returned when
     </m:properties>
   </content>
 ```
- **Note**  The  **ListItemEntityTypeFullName** property ( **SP.Data.ProjectPolicyItemListItem** in the previous example) is especially important if you want to create and update list items. This value must be passed as the **type** property in the metadata that you pass in the body of the HTTP request whenever you create and update list items.
+> [!NOTE]
+> The  **ListItemEntityTypeFullName** property ( **SP.Data.ProjectPolicyItemListItem** in the previous example) is especially important if you want to create and update list items. This value must be passed as the **type** property in the metadata that you pass in the body of the HTTP request whenever you create and update list items.
 
 ## Working with lists by using REST
 <a name="WorkLists"> </a>
@@ -146,7 +148,8 @@ Headers:
 <a name="ListItems"> </a>
 The following example shows how to  **retrieve** all of a list's items.
 
- **Note**  The OData $skip query option does not work when querying list items. In may situations, you can use the  [$skiptoken](http://msdn.microsoft.com/library/4dda9434-c2c5-4577-8e01-7bf9e822d90a.aspx) option instead.
+> [!NOTE]
+> The OData $skip query option does not work when querying list items. In may situations, you can use the  [$skiptoken](http://msdn.microsoft.com/library/4dda9434-c2c5-4577-8e01-7bf9e822d90a.aspx) option instead.
 
 ```
 url: http://site url/_api/web/lists/GetByTitle('Test')/items
@@ -191,7 +194,8 @@ The following XML shows an example of the list item properties that are returned
 
 The following example shows how to  **create** a list item.
 
- **Note**  To do this operation, you must know the  **ListItemEntityTypeFullName** property of the list and pass that as the value of **type** in the HTTP request body.
+> [!NOTE]
+> To do this operation, you must know the  **ListItemEntityTypeFullName** property of the list and pass that as the value of **type** in the HTTP request body.
 
 ```
 url: http://site url/_api/web/lists/GetByTitle('Test')/items
@@ -207,7 +211,8 @@ headers:
 
 The following example shows how to  **update** a list item.
 
- **Note**  To do this operation, you must know the  **ListItemEntityTypeFullName** property of the list and pass that as the value of **type** in the HTTP request body.
+> [!NOTE]
+> To do this operation, you must know the  **ListItemEntityTypeFullName** property of the list and pass that as the value of **type** in the HTTP request body.
 
 ```
 url: http://site url/_api/web/lists/GetByTitle('Test')/items(item id)

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

@@ -59,7 +59,8 @@ For this project, use the Visual Studio Web API project to build the webhook rec
 * Change the authentication to **No Authentication** by choosing the **Change Authentication** button.
 * Choose **OK** to create the Web API project.
 
-> **Note:** You can uncheck the **Host in the cloud** option because this project will not be deployed to the cloud.
+> [!NOTE]
+> You can uncheck the **Host in the cloud** option because this project will not be deployed to the cloud.
 
 Visual Studio will create your project.
 

docs/apis/webhooks/sharepoint-webhooks-using-azure-functions.md

@@ -26,7 +26,7 @@ This will offer you to start your function from a template, in the case of Share
 
 ![Choosing an Azure Function template](../../images/webhook-azure-function3.png)
 
->**Note:**
+> [!NOTE]
 > - Using the **GenericWebHook** template currently does not yet work for SharePoint webhooks but the SharePoint product team is aware of this problem and will address it.
 > - If you get "Failed to validate the notification URL" errors when using your Azure function based webhook you might be able to resolve this by setting the Authorization level to **Function** and define your function for anonymous access
 

docs/apis/webhooks/webhooks-reference-implementation.md

@@ -100,7 +100,8 @@ Property|Description
 **resource**|The ID of the list for which the change happened.
 **siteUrl**|The server relative URL of the site holding the resource for which the change happened.
 
-> **Note:** SharePoint only sends a notification that a change happened, but the notification does not include what actually changed. Because you get information about the web and list that were changed, this means that you can use the same service endpoint to handle webhook events from multiple sites and lists.
+> [!NOTE]
+> SharePoint only sends a notification that a change happened, but the notification does not include what actually changed. Because you get information about the web and list that were changed, this means that you can use the same service endpoint to handle webhook events from multiple sites and lists.
 
 When your service is called, it's important that your service replies with an HTTP 200 message in under 5 seconds. Later in this article you'll learn more about the response time, but essentially this requires that you **asynchronously** handle the notifications. In this reference implementation you'll do this by using Azure Web Jobs and Azure Storage Queues.
 
@@ -149,7 +150,8 @@ When your service receives a notification it also gets information about the sub
 
 Create a web job that on a weekly basis reads all the subscription IDs from the persistent storage. One-by-one extend the found subscriptions each time. 
 
-> **Note:** This web job is not part of this reference implementation.
+> [!NOTE]
+> This web job is not part of this reference implementation.
 
 The actual renewal of a SharePoint list webhook can be done using a [`PATCH /_api/web/lists('list-id')/subscriptions(‘subscriptionID’)`](./lists/update-subscription.md) REST call. In the reference implementation, updating of webhooks is implemented in the [WebHookManager](https://github.com/SharePoint/sp-dev-samples/blob/master/Samples/WebHooks.List/SharePoint.WebHooks.Common/WebHookManager.cs) class of the **SharePoint.WebHooks.Common** project. Updating a webhook is done using the **UpdateListWebHookAsync** method:
 

docs/declarative-customization/site-theming/sharepoint-site-theming-csom.md

@@ -13,10 +13,10 @@ You will also need to reference the [Microsoft.SharePointOnline.CSOM](https://ww
 
 The following example shows how to create a __Microsoft.Online.SharePoint.TenantAdministration.Tenant__ object and call the __GetAllTenantThemes__ method to return a list of themes. 
 
->**Note:**
->* The URL used to create the context object includes the _-admin_ suffix, because **TenantAdministration** methods work with the admin site.
->* Create a __Tenant__ instance with the [Tenant constructor](https://msdn.microsoft.com/en-us/library/dn174852.aspx), and then call the methods on that instance.
->* You can use the same approach to call other theme management methods.
+> [!NOTE]
+> * The URL used to create the context object includes the _-admin_ suffix, because **TenantAdministration** methods work with the admin site.
+> * Create a __Tenant__ instance with the [Tenant constructor](https://msdn.microsoft.com/en-us/library/dn174852.aspx), and then call the methods on that instance.
+> * You can use the same approach to call other theme management methods.
 
 ```C#
 using System.Security;

docs/general-development/accessing-a-schema.md

@@ -10,11 +10,8 @@ ms.assetid: 02613912-36f6-4edc-a915-165d12e60bc8
 
 This topic shows one example of how you can access and look at a schema for the REST service in Excel Services. This topic assumes that you have read  [Sample URI For Excel Services REST API](sample-uri-for-excel-services-rest-api.md).d
 
-    
-    
-
-
-> **Note:**
+> [!NOTE]
+> 
 > The Excel Services REST API applies to SharePoint and SharePoint 2016 on-premises. For Office 365 Education, Business, and Enterprise accounts, use the Excel REST APIs that are part of the  [Microsoft Graph](http://graph.microsoft.io/en-us/docs/api-reference/v1.0/resources/excel
 ) endpoint.