address automated feedback issues

Author: andrewconnell

docs/schema/listtemplate-element-list-template.md

@@ -103,10 +103,7 @@ The following sections describe attributes, child elements, and parent elements.
 | **OnQuickLaunch** | Optional **Boolean**. **TRUE** to display lists created from the list definition on the **QuickLaunch** bar. |
 | **Path** | Optional **Text**. Specifies the name of the site definition that contains the list definition; for example, **STS**. This path is assumed to be relative to the **12\\TEMPLATE** directory. The path can be directed at a Features schema; for example, **Features\\Announcements**. *Same as previous version, but deprecated.* |
 | **RootWebOnly** | Optional **Boolean**. **TRUE** to specify that the list created from the definition exists only in the root website of a site collection. *Same as previous version, but deprecated.* |
-| **SecurityBits** | Optional **Text**. Defines the item-level permissions in the list for users with sufficient permission to read or edit list items. The **SecurityBits** attribute contains a 2-digit string. The first digit in the string controls the read access; the second digit in the string controls the edit access. For read access, the following are valid digits:<ul><li>1: Users can read all items.</li><li>2: Users can read only their own items.</li></ul>For edit access, the following are valid digits:<ul><li>1: Users can edit all items.</li><li>2: Users can edit only their own items.</li><li>4: Users cannot edit items.</li></ul>
-> [!NOTE]
-> Users with the ManageLists permission can read and edit all items, regardless of value of the **SecurityBits** attribute. This attribute does not apply to document libraries.
-|
+| **SecurityBits** | Optional **Text**. Defines the item-level permissions in the list for users with sufficient permission to read or edit list items. The **SecurityBits** attribute contains a 2-digit string. The first digit in the string controls the read access; the second digit in the string controls the edit access. For read access, the following are valid digits:<ul><li>1: Users can read all items.</li><li>2: Users can read only their own items.</li></ul>For edit access, the following are valid digits:<ul><li>1: Users can edit all items.</li><li>2: Users can edit only their own items.</li><li>4: Users cannot edit items.</li></ul>**Note**: Users with the ManageLists permission can read and edit all items, regardless of value of the **SecurityBits** attribute. This attribute does not apply to document libraries.|
 | **Sequence** | Optional **Integer**. Specifies the ordering priority to use for the list template on the **Create** page. If **Sequence** is not set, the template appears last in arbitrary order with any other templates that also lack a **Sequence** value. Two templates that specify the same sequence are sorted together in an arbitrary order. |
 | **SetupPath** | Optional **Text**. Specifies the path to a folder in the SharePoint Foundation setup directory (**%ProgramFiles%\\Common Files\\Microsoft Shared\\web server extensions\\15\\\TEMPLATE**) that contains a file to include in the template. |
 | **SyncType** | Optional **Boolean**. **TRUE** to override the default client list type associated with a SharePoint Foundation base template. |

docs/solution-guidance/javascript-patterns-and-performance.md

@@ -36,11 +36,11 @@ At each step of the development process, it's important to keep performance in m
 |Option|Description|
 |:---|:---|
 |[Reduce the number of requests](#reduce-the-number-of-requests) | Fewer requests means fewer round-trips to the server, reducing latency.|
-|[Retrieve only the data you need](#RetrieveOnlyTheDataYouNeed) | Reduce the amount of data sent over the wire. Also reduces server load.|
-|[Provide a good page load experience](#ProvideAGoodUserExperience) | Keep your UI responsive to the user. For example, update the menus on the page *before* you start the download of 100+ records.|
-|[Use asynchronous calls and patterns whenever possible](#EverythingIsAsynchronous) | Polling is a heavier burden on performance than using an asynchronous call or callback.|
-|[Caching is key](#ClientSideCaching) | Caching further reduces the burden on the server while giving immediate performance improvement.|
-|[Prepare for more page views than you ever imagined](#PriceOfPopularity) | A data-heavy landing page is okay when you only have a few hits. But if you get thousands of hits, that can really impact performance.|
+|[Retrieve only the data you need](#retrieve-only-the-data-you-need) | Reduce the amount of data sent over the wire. Also reduces server load.|
+|[Provide a good page load experience](#provide-a-good-user-experience) | Keep your UI responsive to the user. For example, update the menus on the page *before* you start the download of 100+ records.|
+|[Use asynchronous calls and patterns whenever possible](#everything-is-asynchronous) | Polling is a heavier burden on performance than using an asynchronous call or callback.|
+|[Caching is key](#client-side-caching) | Caching further reduces the burden on the server while giving immediate performance improvement.|
+|[Prepare for more page views than you ever imagined](#the-price-of-popularity) | A data-heavy landing page is okay when you only have a few hits. But if you get thousands of hits, that can really impact performance.|
 
 ## What is my code doing
 
@@ -54,7 +54,7 @@ There are several ways to reduce requests and reduce request size.
 
 - Limit the number of JavaScript files in production. Separating your JavaScript files works well for development, but not so well for production. Combine your JavaScript files into a single JavaScript file, or as few JavaScript files as you can.
 - Shrink file sizes. Minimize your production JavaScript files by removing line breaks, white space, and comments. There are several JavaScript minify programs and websites that you can use to greatly reduce your JavaScript file sizes.
-- Use browser file caching to reduce requests. The updated [Loader Pattern](#LoaderPattern) below is a good way to expand upon this idea.
+- Use browser file caching to reduce requests. The updated [Loader Pattern](#the-loader-pattern) below is a good way to expand upon this idea.
 
 ### Retrieve only the data you need
 

docs/solution-guidance/update-the-branding-of-existing-sharepoint-sites-and-page-regions.md

@@ -130,7 +130,7 @@ When your objective is to customize regions of a SharePoint page, you can use a
 |Suite navigation|Any of the default master pages. |Can be hidden via the **Focus on Content** button.|
 |Suite links||Can be hidden via the **Focus on Content** button.|
 |Welcome menu|**\*.master**|Can be hidden via the **Focus on Content** button.|
-|Settings menu or gear|**\*.master**|For an example, see [FTC to CAM - Custom actions and property bag entries from SP Add-in](https://blogs.msdn.com/b/vesku/archive/2013/10/02/ftc-to-cam-custom-actions-and-property-bag-entries.aspx).|
+|Settings menu or gear|**\*.master**||
 |Help|**\*.master**||
 |Ribbon contextual tabs|Any default master page.|For examples, see the following: <ul><li>[SharePoint 2013 Duplicate Contextual Tabs](https://social.msdn.microsoft.com/Forums/sharepoint/df1e4e32-ef58-4b51-8ac8-a8c3690e648b/sharepoint-2013-duplicate-contextual-tabs?forum=sharepointdevelopment)</li><li>[Hide a Contextual ribbon tab](https://social.msdn.microsoft.com/Forums/sharepoint/a3640d58-afe1-41d0-ac83-bd7886c37355/hide-a-contextual-ribbon-tab?forum=crmdevelopment)</li><li>[Hide/Show contextual tab on click event of subgrid](https://social.msdn.microsoft.com/Forums/sharepoint/201306cf-5874-4778-b773-f870c67cee94/hideshow-contextual-tab-on-click-event-of-subgrid?forum=crmdevelopment)</li></ul>|
 |Quick access toolbar|**\*.master**|Can be hidden via the **Focus on Content** button.|

docs/sp-add-ins/use-the-client-side-people-picker-control-in-sharepoint-hosted-sharepoint-add-in.md

@@ -50,7 +50,7 @@ If you're not using Napa on a developer site, you need the following:
 > [!NOTE]
 > For guidance about how to set up a development environment that fits your needs, see [SharePoint Add-ins](sharepoint-add-ins.md#two-types-of-sharepoint-add-ins-sharepoint-hosted-and-provider-hosted).
 
-The following sections describe the high-level steps for adding the picker to your add-in and then getting its user information from another client-side control. For the corresponding code, see [Code example: Using the client-side People Picker](#bk_example).
+The following sections describe the high-level steps for adding the picker to your add-in and then getting its user information from another client-side control. For the corresponding code, see [Code example: Using the client-side People Picker](#code-example-using-the-client-side-people-picker-in-a-sharepoint-hosted-add-in).
 
 You can use the client-side People Picker control in SharePoint-hosted SharePoint Add-ins, but not in provider-hosted add-ins.