fixed alerts in tables

Author: davidchesnut

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

@@ -81,8 +81,8 @@ 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:**

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

@@ -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/> |
 
@@ -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/> |
 

docs/general-development/choose-the-right-api-set-in-sharepoint.md

@@ -95,7 +95,7 @@ The following table provides guidance on which set of APIs to use for a selected
 |Create a timer job  <br/> |Server object model  <br/> |
 |Create an extension of Central Administration  <br/> |Server object model  <br/> |
 |Create consistent branding across an entire SharePoint farm  <br/> |Server object model  <br/> |
-|Create a custom Web Part, application page, or ASP.NET user control  <br/> |Server object model  <br/> > **Important:**> If the functionality you want to offer customers is not oriented to SharePoint administration at a scope broader than site collection, we recommend that, instead of using the server object model, you create an SharePoint Add-in that includes a remote ASP.NET web application with custom Web Parts and user controls as needed. See the top two rows of this table.           |
+|Create a custom Web Part, application page, or ASP.NET user control  <br/> |Server object model  <br/> **Important:** If the functionality you want to offer customers is not oriented to SharePoint administration at a scope broader than site collection, we recommend that, instead of using the server object model, you create an SharePoint Add-in that includes a remote ASP.NET web application with custom Web Parts and user controls as needed. See the top two rows of this table.           |
 
 
 ## Server object model

docs/general-development/custom-security-trimming-for-search-in-sharepoint-server.md

@@ -234,7 +234,7 @@ The following table describes the parameters that the cmdlet uses.
 |:-----|:-----|
 | _SearchApplication_ <br/> |Required. The name of the Search service application, for example "Search Service Application".  <br/> |
 | _typeName_ <br/> |Required. The strong name of the custom security trimmer assembly.  <br/> |
-| _RulePath_ <br/> |Required for post-trimmers; optional for pre-trimmers. The crawl rule for the security trimmer.  <br/> > **Note:**> We recommend using one crawl rule per content source.           |
+| _RulePath_ <br/> |Required for post-trimmers; optional for pre-trimmers. The crawl rule for the security trimmer.  <br/> **Note:** We recommend using one crawl rule per content source.           |
 | _id_ <br/> |Required. The security trimmer identifier (ID). This value is unique; if a security trimmer is registered with an ID that is already registered for another security trimmer, the registration for the first trimmer is overwritten with the registration for the second trimmer.  <br/> |
 | _properties_ <br/> |Optional. The name-value pairs specifying the configuration properties. Must be in the following format:  `Name1~Value1~Name2~Value~…` <br/> |
 

docs/general-development/develop-sharepoint-workflows-using-visual-studio.md

@@ -102,13 +102,13 @@ The following table provides a side-by-side comparison of the features and requi
 |Enables reuse of workflows  <br/> |A workflow can be used only by the list or library on which it was developed. However, SharePoint Designer provides reusable workflows that can be used multiple times within the same site.  <br/> |A workflow can be written as a template so that after it is deployed, it can be reused and associated with any list or library.  <br/> |
 |Allows you to include a workflow as part of a SharePoint solution or SharePoint Add-in  <br/> |No  <br/> |Yes  <br/> |
 |Allows you to create custom actions  <br/> |No. However, SharePoint Designer can consume and implement custom actions that are created and deployed by using Visual Studio.  <br/> |Yes. However, be aware that in Visual Studio, the underlying activities, not their corresponding actions, are used.  <br/> |
-|Allows you to write custom code  <br/> |No  <br/> |No  <br/> > **Note:**> This is changed from previous versions. In SharePoint 2013, workflows are declarative only and Visual Studio relies on the visual design surface for workflow development.           |
+|Allows you to write custom code  <br/> |No  <br/> |No  <br/> **Note:** This is changed from previous versions. In SharePoint 2013, workflows are declarative only and Visual Studio relies on the visual design surface for workflow development.           |
 |Can use Visio Professional to create workflow logic  <br/> |Yes  <br/> |No  <br/> |
 |Deployment  <br/> |Deployed automatically to list, library, or site on which they were created.  <br/> |Create a SharePoint solution package (.wsp) file and deploy the solution package to the site (SPWeb).  <br/> |
 |One-click publishing available for workflows  <br/> |Yes  <br/> |Yes  <br/> |
 |Workflows can be packaged and deployed to a remote server  <br/> |Yes  <br/> |Yes  <br/> |
 |Debugging  <br/> |Cannot be debugged.  <br/> |Workflow can be debugged by using Visual Studio.  <br/> |
-|Can use only actions that are approved by site administrator  <br/> |Yes  <br/> |Yes  <br/> > **Note:**> This is changed from previous versions. Previously, workflows and actions that were authored by using Visual Studio were code-based and deployed at the farm scope, so administrator approval was not required.           |
+|Can use only actions that are approved by site administrator  <br/> |Yes  <br/> |Yes  <br/> **Note:** This is changed from previous versions. Previously, workflows and actions that were authored by using Visual Studio were code-based and deployed at the farm scope, so administrator approval was not required.           |
 
 
 ## Developing workflows using Visual Studio

docs/general-development/integrating-___location-and-map-functionality-in-sharepoint.md

@@ -60,7 +60,7 @@ The ___location and map features in SharePoint 2013 provide unique opportunities fo
 |:-----|:-----|
 | [How to: Set the Bing Maps key at the web and farm level in SharePoint 2013](how-to-set-the-bing-maps-key-at-the-web-and-farm-level-in-sharepoint.md) <br/> |SharePoint 2013 uses Bings Maps to render the map of the ___location. To be able to use the Bing Maps feature, you need to create a Bing Maps key and set the key at the web or farm level. The article shows the various ways you can set the key in SharePoint 2013 and when to choose which option. You see an error message on the map if you do not use a valid Bing Maps key or if a key is not set at the web that contains the list or at the farm level.  <br/> |
 | [How to: Add a Geolocation column to a list programmatically in SharePoint 2013](how-to-add-a-geolocation-column-to-a-list-programmatically-in-sharepoint.md) <br/> |The Geolocation column is not available in SharePoint lists for users, by default. To add the column to a SharePoint list, you need to write code. In this topic, learn how to add the Geolocation field to a list programmatically.  <br/> |
-| [How to: Extend the Geolocation field type using client-side rendering](how-to-extend-the-geolocation-field-type-using-client-side-rendering.md) <br/> |You can provide your own rendering to default user interface (UI), logic, and behavior of the Geolocation field by creating custom field types that derive from the Geolocation field. SharePoint 2013 simplifies the creation of custom field types by enabling you to run JavaScript by providing a new JSLink property in the Geolocation field class, which points to a custom .js file that renders the field.  <br/> > **Note:**> The JSLink property is not supported on Survey or Events lists. A SharePoint calendar is an Events list.           |
+| [How to: Extend the Geolocation field type using client-side rendering](how-to-extend-the-geolocation-field-type-using-client-side-rendering.md) <br/> |You can provide your own rendering to default user interface (UI), logic, and behavior of the Geolocation field by creating custom field types that derive from the Geolocation field. SharePoint 2013 simplifies the creation of custom field types by enabling you to run JavaScript by providing a new JSLink property in the Geolocation field class, which points to a custom .js file that renders the field.  <br/> **Note:** The JSLink property is not supported on Survey or Events lists. A SharePoint calendar is an Events list.           |
 
 
 ## Additional resources