converted alerts to devofficecom format

Author: davidchesnut

docs/general-development/access-sharepoint-from-mobile-and-native-device-apps.md

@@ -13,7 +13,7 @@ SharePoint Add-ins, farm solutions, and "no code" sandboxed solutions are all ru
 
 
 
-> [!IMPORTANT]
+> **Important:**
 > To test and debug on any platform, you need a **developer account on Office 365**. More info: [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) or [Create a developer site on an existing Office 365 subscription](http://msdn.microsoft.com/library/2ec857d5-dc6f-4cf6-ba45-adc845ef2a25%28Office.15%29.aspx). 
   
 

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

@@ -13,7 +13,7 @@ This topic shows one example of how you can access and look at a schema for the
 
 
 
-> [!NOTE]
+> **Note:**
 > The Excel Services REST API applies to SharePoint 2013 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.
 

docs/general-development/add-in-scoped-external-content-types-in-sharepoint.md

@@ -129,7 +129,7 @@ The following example shows how to set the **MetadataCatalogFileName** property
 ```
 
 
-> [!NOTE]
+> **Note:**
 > Site administrators can install add-ins that use App-Scoped-ECTs, but only SiteCollection administrators can grant permissions for Apps to Use BCS Connections. 
   
 
@@ -154,14 +154,14 @@ You can include a BDC model in a WSP file for deployment. The following example
 ```
 
 
-> [!IMPORTANT]
+> **Important:**
 > Only one BDC model file can be included per add-in. While the file name in this example is BDCMetadata.bdcm, the model file can actually be any name you choose as long as the file name matches that is in the **Path** attribute of the BDC model file.
   
 
 
 
 
-> [!NOTE]
+> **Note:**
 > Only Open Data protocol (OData) connections are allowed for add-in-scoped external content types. 
   
 

docs/general-development/advanced-scenarios-and-additional-samples.md

@@ -13,7 +13,7 @@ This topic describes some advanced REST scenarios and additional samples. It pro
 
 
 
-> [!NOTE]
+> **Note:**
 > The Excel Services REST API applies to SharePoint 2013 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.
 

docs/general-development/architecture-of-the-windows-phone-sharepoint-list-application-template.md

@@ -137,7 +137,7 @@ Software designs based on the MVVM pattern often confine business logic and vali
 
 
 
-> [!NOTE]
+> **Note:**
 > The **ListDataProvider** object only loads the data from server. Other operations, such as **Add**, **Update**, and **Delete**, are performed in the ViewModel itself, followed by a refresh call to update the ViewModel data from the server. This design reduces cluttering of the code. 
   
 

docs/general-development/authentication-authorization-and-security-in-sharepoint.md

@@ -49,7 +49,7 @@ SharePoint 2013 supports security for user access at the website, list, list or
 
 
 
-> [!NOTE]
+> **Note:**
 > For information about authorization related to SharePoint Add-ins, see  [Authorization and authentication of SharePoint Add-ins](http://msdn.microsoft.com/library/bde5647a-fff1-4b51-b67b-2139de79ce4a%28Office.15%29.aspx). 
   
 
@@ -68,15 +68,15 @@ SharePoint 2013 supports the following types of authentication:
 
     For information about signing in to SharePoint by using Windows claims mode, see  [Incoming claims: Signing into SharePoint 2013](incoming-claims-signing-into-sharepoint.md).
 
-    > [!IMPORTANT]
+    > **Important:**
       >  For information about suspending impersonation, see [Avoid suspending impersonation of the calling user](http://msdn.microsoft.com/en-us/library/ff407852.aspx). 
 - **ASP.NET Forms:** A non-Windows identity management system that uses the pluggable ASP.NET forms-based authentication system is supported. This mode enables SharePoint 2013 to work with a variety of identity management systems, including externally defined groups or roles such as Lightweight Directory Access Protocol (LDAP) and light-weight database identity management systems. Forms authentication allows ASP.NET to perform the authentication for SharePoint 2013, often involving a redirect to a log-on page. In SharePoint 2013, ASP.NET forms are supported only under claims authentication. A forms provider must be registered within a web application that is configured for claims.
 
     For information about signing in to SharePoint by using ASP.NET membership and role passive sign-in, see  [Incoming claims: Signing into SharePoint 2013](incoming-claims-signing-into-sharepoint.md).
 
 
 
-> [!NOTE]
+> **Note:**
 > SharePoint 2013 does not support working with a case-sensitive membership provider. It uses case-insensitive SQL storage for all users in the database, regardless of the membership provider. 
   
 
@@ -108,7 +108,7 @@ When a user signs in to SharePoint 2013, the user's token is validated and then
 
 
 
-> [!NOTE]
+> **Note:**
 > For more information about signing into SharePoint and the different sign-in modes, see  [Incoming claims: Signing into SharePoint 2013](incoming-claims-signing-into-sharepoint.md). 
   
 
@@ -140,7 +140,7 @@ Under this model, your application makes identity-related decisions based on cla
 
 
 
-> [!NOTE]
+> **Note:**
 > For more information about claims-based identity and claims providers, see  [Claims-based identity and concepts in SharePoint 2013](claims-based-identity-and-concepts-in-sharepoint.md) and [Claims provider in SharePoint 2013](claims-provider-in-sharepoint.md). 
   
 
@@ -159,7 +159,7 @@ The membership provider is responsible for validating the credential information
 
 
 
-> [!NOTE]
+> **Note:**
 > For more information about STS, see  [Claims-based identity and concepts in SharePoint 2013](claims-based-identity-and-concepts-in-sharepoint.md). 
   
 
@@ -170,7 +170,7 @@ The role manager is optional. If a custom authentication system does not support
 
 
 
-> [!NOTE]
+> **Note:**
 > For more information about claims-based identity and claims providers, see  [Claims-based identity and concepts in SharePoint 2013](claims-based-identity-and-concepts-in-sharepoint.md) and [Claims provider in SharePoint 2013](claims-provider-in-sharepoint.md). 
   
 
@@ -181,7 +181,7 @@ In ASP.NET membership and role passive sign-in, the sign-in happens by redirecti
 
 
 
-> [!NOTE]
+> **Note:**
 > For more information about signing into SharePoint, see  [Incoming claims: Signing into SharePoint 2013](incoming-claims-signing-into-sharepoint.md). 
   
 
@@ -196,7 +196,7 @@ For information about the pluggable authentication framework provided by ASP.NET
 
 
 
-> [!NOTE]
+> **Note:**
 > For more information about forms-based authentication, see  [Forms authentication in SharePoint products and technologies (Part 1): Introduction](http://msdn.microsoft.com/library/e5efd4d7-b369-49f0-a6f7-431d21daff20%28Office.15%29.aspx). 
   
 

docs/general-development/authorization-users-groups-and-the-object-model-in-sharepoint.md

@@ -67,7 +67,7 @@ In policy roles, the users and groups are identified by both their security iden
 
 
 
-> [!NOTE]
+> **Note:**
 > Central administration policy roles differ from the role definitions for a site collection. 
   
 

docs/general-development/basic-uri-structure-and-path.md

@@ -13,7 +13,7 @@ This topic explains how to construct the URI structure and path for REST service
 
 
 
-> [!NOTE]
+> **Note:**
 > The Excel Services REST API applies to SharePoint 2013 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.
 

docs/general-development/bcs-rest-api-reference-for-sharepoint.md

@@ -36,7 +36,7 @@ You can access external data by constructing URLs just as you would to access st
 
 
 
-> [!NOTE]
+> **Note:**
 > Access to entities through the BDC directly is not provided. To work with external data, you must create an external list and use the REST URLs to access the list items contained in the external list. 
   
 
@@ -81,11 +81,11 @@ In order to limit the amount of data returned, or make it more relevant to the u
 
 |**Operator**|**Description**|
 |:-----|:-----|
-|EQ  <br/> |Equals  <br/> > [!NOTE]> When you use **EQ** to filter, the filter criteria are passed to the external system where the filtering happens on the server.          |
-|GT  <br/> |Greater Than  <br/> > [!NOTE]> When you use the **GT** operator, only client-side filtering is executed.> For example:  `web/lists/getByTitle('ListName')/Items?$select=Title&amp;$filter=AverageRating gt 3` returns all titles with an average rating over 3.          |
+|EQ  <br/> |Equals  <br/> > **Note:**> When you use **EQ** to filter, the filter criteria are passed to the external system where the filtering happens on the server.          |
+|GT  <br/> |Greater Than  <br/> > **Note:**> When you use the **GT** operator, only client-side filtering is executed.> For example:  `web/lists/getByTitle('ListName')/Items?$select=Title&amp;$filter=AverageRating gt 3` returns all titles with an average rating over 3.          |
 
 
-> [!NOTE]
+> **Note:**
 > To retrieve columns that are part of an association, you must explicitly include the column in the URL using **$select** in the query string.
   
 

docs/general-development/bdc-model-schema-reference-for-sharepoint.md

@@ -233,7 +233,7 @@ The URL attribute of a URL-based action can receive parameters by using the **Ac
 
 
 
-> [!IMPORTANT]
+> **Important:**
 > **ActionParameters** can either represent identifier values, or values that correspond to **TypeDescriptors** in a **SpecificFinder** of the **Entity**. The **ActionParameter** represents an identifier value when the **IdOrdinal** property is present. The value of the property specifies the index of the identifier whose value this **ActionParameter** represents. If the **IdOrdinal** property is not specified, the **ActionParameter** represents a **TypeDescriptor**, and the **Name** attribute specifies which type descriptor is being represented. The **Name** attribute is specified as a **Dotted Path**. 
   
 
@@ -244,7 +244,7 @@ The **ActionParameter** element accepts the following property.
 
 
 
-> [!IMPORTANT]
+> **Important:**
 > Properties are case-sensitive. 
   
 
@@ -442,7 +442,7 @@ The Association element links related external content types within a system. Fo
 
 
 
-> [!IMPORTANT]
+> **Important:**
 > Properties are case-sensitive. 
   
 
@@ -720,7 +720,7 @@ The Convert element specifies the rule to convert the data type of a data value
 
 
 
-> [!CAUTION]
+> **Caution:**
 > **ConvertType** does not support non-Gregorian calendars for conversions between **System.String** and **System.DateTime**. 
   
 
@@ -1032,11 +1032,11 @@ The following sections describe attributes, child elements, and parent elements.
 
 |**Attribute**|**Description**|
 |:-----|:-----|
-|**Namespace** <br/> |Required.  <br/> The namespace that this external content type belongs to.  <br/> Attribute type: **String** <br/> > [!NOTE]> The namespace should not contain the asterisk special character " *****".           |
-|**Version** <br/> |Required.  <br/> The version number of this external content type.  <br/> Attribute type: **String** <br/> > [!CAUTION]> When the BDC model changes, you must increase the version number of the external content type. If the structure of an external content type changes, you should increase the major number. Examples of structural changes include adding a field to a **SpecificFinder** or changing an identifier field. If the change does not affect the structure of the external content type, for example, when adding a creator method, changing connection information, or when changing names of **LobSystems** and type descriptors, you should change the build number and revision number.          |
+|**Namespace** <br/> |Required.  <br/> The namespace that this external content type belongs to.  <br/> Attribute type: **String** <br/> > **Note:**> The namespace should not contain the asterisk special character " *****".           |
+|**Version** <br/> |Required.  <br/> The version number of this external content type.  <br/> Attribute type: **String** <br/> > **Caution:**> When the BDC model changes, you must increase the version number of the external content type. If the structure of an external content type changes, you should increase the major number. Examples of structural changes include adding a field to a **SpecificFinder** or changing an identifier field. If the change does not affect the structure of the external content type, for example, when adding a creator method, changing connection information, or when changing names of **LobSystems** and type descriptors, you should change the build number and revision number.          |
 |**EstimatedInstanceCount** <br/> |Optional.  <br/> The estimated number of external items contained by the external system.  <br/> Default value: 10000  <br/> Attribute type: **Integer** <br/> |
 |**DefaultOperationMode** <br/> |Optional.  <br/> Specifies the default behavior when interacting with the external system while creating, deleting, updating, or reading external items.  <br/> Default value: Default  <br/> The following table lists the possible values for this attribute.  <br/> <table width="50%" cellspacing="2" cellpadding="5" frame="lhs"><thead><tr><th><p>Value</p></th><th><p>Description</p></th></tr></thead><tbody><tr><td><p>Online</p></td><td><p>Bypass the cached external items for all operations and interact with the external system directly.</p></td></tr><tr><td><p>Cached</p></td><td><p>Perform <b>Create</b>, <b>Read</b>, <b>Update</b>, and <b>Delete</b> operations directly against the cached external items. For <b>Read</b> operations, if the requested external items are available in the cache, use the external items in the cache. Otherwise, bypass the cache to obtain the external items from the external system, and put it in the cache for later use.</p></td></tr><tr><td><p>Offline</p></td><td><p>Perform <b>Create</b>, <b>Read</b>, <b>Update</b>, and <b>Delete</b> operations against only the cached external items.</p></td></tr><tr><td><p>Default</p></td><td><p>Use the System default behavior. This uses Cached mode if the environment supports caching external items.</p></td></tr></tbody></table>|
-|Name  <br/> |Required.  <br/> The name of the external content type.  <br/> Attribute type: **String** <br/> > [!NOTE]> The name of an external content type should not contain the asterisk special character " *****".           |
+|Name  <br/> |Required.  <br/> The name of the external content type.  <br/> Attribute type: **String** <br/> > **Note:**> The name of an external content type should not contain the asterisk special character " *****".           |
 |DefaultDisplayName  <br/> |Optional.  <br/> The default display name of the external content type.  <br/> Attribute type: **String** <br/> |
 |IsCached  <br/> |Optional.  <br/> Specifies whether this external content type will be frequently used. If set to true, Business Data Connectivity (BDC) service will cache this external content type in memory.  <br/> Default value: **true** <br/> Attribute type: **Boolean** <br/> |
 
@@ -1208,7 +1208,7 @@ Specifies an identifier of an external content type.
 
 
 
-> [!NOTE]
+> **Note:**
 > Business Data Connectivity (BDC) service enables the mapping of identifiers to fields with nullable data types. However, for primary identifiers, BDC will cause an error when the value of these identifiers are **null**. 
   
 
@@ -2650,7 +2650,7 @@ The following sections describe attributes, child elements, and parent elements.
 |**UpdaterField** <br/> |Optional.  <br/> Specifies whether the **TypeDescriptor** represents a field for **MethodInstances** of type **Updater** that are contained by the **Method** that contains the **Parameter** containing the **TypeDescriptor**. When this attribute is specified, a **PreUpdaterField** attribute must not be specified. <br/> Default value: **false** <br/> Attribute type: **Boolean** <br/> |
 |**PreUpdaterField** <br/> |Optional.  <br/> Specifies whether data structure represented by the **TypeDescriptor** stores the latest data value received from the external system of a field for **MethodInstances** of type **Updater**. When this attribute is specified, a **UpdaterField** attribute must not be specified. <br/> Default value: **false** <br/> Attribute type: **Boolean** <br/> |
 |**Significant** <br/> |Optional.  <br/> Specifies whether values stored by the data structure represented by this **TypeDescriptor** are included in calculating a hash code or comparing values stored in the data structures. For example, a **TypeDescriptor** representing a customer's last name is taken into account when determining whether a record has been modified, and so it is significant, whereas the **TypeDescriptor** representing the date on which the customer record is last modified typically is not taken into account to determine whether a record has been modified, and so it is not significant. <br/> Default value: **true** <br/> Attribute type: **Boolean** <br/> |
-|**Name** <br/> |Required.  <br/> The name of the **TypeDescriptor**.  <br/> Attribute type: **String** <br/> > [!NOTE]> The name of a **TypeDescriptor** should not contain the special characters for forward slash ("/"), period ("."), or opening bracket ("[").          |
+|**Name** <br/> |Required.  <br/> The name of the **TypeDescriptor**.  <br/> Attribute type: **String** <br/> > **Note:**> The name of a **TypeDescriptor** should not contain the special characters for forward slash ("/"), period ("."), or opening bracket ("[").          |
 |**DefaultDisplayName** <br/> |Optional.  <br/> The display name of the **TypeDescriptor**.  <br/> Attribute type: **String** <br/> |
 |**IsCached** <br/> |Optional.  <br/> Specifies whether the **TypeDescriptor** is used frequently. <br/> Default value: **true** <br/> Attribute type: **Boolean** <br/> |