Fix "heading-with-underline" markdown warnings

Author: andrewconnell

docs/solution-guidance/custom-field-type-sharepoint-add-in.md

@@ -1,14 +1,14 @@
 ---
 title: Custom field type in the SharePoint Add-in model
+description: The approach you take to provide customized end user experiences is different in the new SharePoint Add-in model than it was with Full Trust Code. In a typical Full Trust Code (FTC) / Farm Solution scenario, custom field types were created with the SharePoint server-side object model code by inheriting from one of the built-in field type classes and creating a field type deployment file (XML).
 ms.date: 11/03/2017
 localization_priority: Normal
 ---
-Custom field type in the SharePoint Add-in model
-================================================
+# Custom field type in the SharePoint Add-in model
 
 ## Summary
 
-The approach you take to provide customized end user experiences is different in the new SharePoint Add-in model than it was with Full Trust Code. In a typical Full Trust Code (FTC) / Farm Solution scenario, custom field types were created with the SharePoint server-side object model code by inheriting from one of the built-in field type classes and creating a field type deployment file (XML). These components were deployed via SharePoint solutions. 
+The approach you take to provide customized end user experiences is different in the new SharePoint Add-in model than it was with Full Trust Code. In a typical Full Trust Code (FTC) / Farm Solution scenario, custom field types were created with the SharePoint server-side object model code by inheriting from one of the built-in field type classes and creating a field type deployment file (XML). These components were deployed via SharePoint solutions.
 
 In a SharePoint Add-ins model scenario, customized end user experiences are implemented via client-side rendering. In this approach, JavaScript files are used to implement customized end user experiences. The remote provisioning pattern deploys the JavaScript files and registers them with SharePoint fields via the JSLink property.
 
@@ -24,9 +24,11 @@ Here are some examples of custom field type that implements a Google map. These
 ![Two Google map views showing the Microsoft Campus Location Point, and Location Area.](https://raw.githubusercontent.com/SharePoint/PnP/master/Samples/Branding.JSLink/readme-images/GoogleMaps.png)
 
 **Inline editing showing a larger Google map thumbnail:**
+
 ![Two Google maps. One view showing the Microsoft Campus Location Point with a link to Select Location, the other view showing the Microsoft Campus Location Area with a link to Edit Shape.](https://raw.githubusercontent.com/SharePoint/PnP/master/Samples/Branding.JSLink/readme-images/GoogleMaps_Edit.png)
 
 **A dialog enabling inline editing:**
+
 ![A Google Map showing the Microsoft Campus Shape. Text on the image reads, Click on the map to place markers and create your shape. Finish by clicking on the first marker. You can drag each of the markers around, or click on them for more options. You can use the Clear Map button above to remove all markers.](https://raw.githubusercontent.com/SharePoint/PnP/master/Samples/Branding.JSLink/readme-images/GoogleMaps_Shape_Edit.png)
 
 ## High-level guidelines
@@ -38,89 +40,87 @@ As a rule of a thumb, we would like to provide the following high-level guidelin
 - Register the JavaScript files with the Minimal Download Strategy (MDS) engine to ensure the MDS engine is aware of the custom rendering JavaScript files.
 - Setting JSLink property to host web requires at least full permission at web level, so this approach is not suitable for add-ins at the SharePoint store
 
-Options to implement client-side rendering with JavaScript files via the JSLink property
-----------------------------------------------------------------------------------------
+## Options to implement client-side rendering with JavaScript files via the JSLink property
 
 You have a couple of options to implement client-side rendering with JavaScript files via the JSLink property.
 
-- Set the JSLink property on a List View web part that renders a view of a SharePoint list.	
-- Set the JSLink property for a SharePoint field. 
-- Set the JSLink property for a SharePoint content type. 
-	
+- Set the JSLink property on a List View web part that renders a view of a SharePoint list.
+- Set the JSLink property for a SharePoint field.
+- Set the JSLink property for a SharePoint content type.
+
+## Set the JSLink property on a List View web part that renders a view of a SharePoint list
 
-Set the JSLink property on a List View web part that renders a view of a SharePoint list
------------------------------------------------------------------------------------------
 In this option you set the JSLink property on a WebPartDefinition.
-	
+
 - **This approach does not specifically create a custom field type at the SPField level.**
-	+ Therefore, *the custom rendering only applies in the List View web part where you set the JSLink property*.
+  - Therefore, *the custom rendering only applies in the List View web part where you set the JSLink property*.
 - This approach allows you to change the rendering for one or more SharePoint fields at once.
 - This approach may be done with declarative code, with the SharePoint server-side object model, with the SharePoint client-side object model (CSOM), or via PowerShell.
-	+ We recommend you use the SharePoint server-side object model, the SharePoint client-side object model, or PowerShell to set the JSLink property via the remote provisioning pattern.
+  - We recommend you use the SharePoint server-side object model, the SharePoint client-side object model, or PowerShell to set the JSLink property via the remote provisioning pattern.
 
-**When is it a good fit?**
+### When is it a good fit?
 
 When you need to define specific views for SharePoint list data and modify the rendering for more than one SharePoint field, this is a good option.
 
-**Getting started**
+### Getting started
 
 The following sample sets the JSLink property on a SharePoint List View web part.
 
 - [Branding.ClientSideRendering (O365 PnP Sample)](https://github.com/SharePoint/PnP/tree/master/Samples/Branding.ClientSideRendering)
-	+ Includes 9 samples that set the JSLink property on a SharePoint List View web part and an explanation of how each sample was implemented.
-	+ The RegisterJStoWebPart method sets the List View web part's JSLink property. 
+  - Includes 9 samples that set the JSLink property on a SharePoint List View web part and an explanation of how each sample was implemented.
+  - The RegisterJStoWebPart method sets the List View web part's JSLink property.
 
-Set the JSLink property for a SharePoint field
-----------------------------------------------
+## Set the JSLink property for a SharePoint field
 
 In this option you set the JSLink property on an SPField.
-	
+
 - **This approach specifically registers the JSLink property at the SPField level.**
-	+ Therefore, *the custom rendering will apply everywhere the SPField is rendered*.
+  - Therefore, *the custom rendering will apply everywhere the SPField is rendered*.
 - This approach allows you to change the rendering for one SharePoint field.
 - This approach may be done with declarative code, with the SharePoint server-side object model, with the SharePoint client-side object model, or via PowerShell.
-	+ We recommend you use the SharePoint server-side object model, the SharePoint client-side object model, or PowerShell to set the JSLink property via the remote provisioning pattern.
+  - We recommend you use the SharePoint server-side object model, the SharePoint client-side object model, or PowerShell to set the JSLink property via the remote provisioning pattern.
 
-**When is it a good fit?**
+### When is it a good fit?
 
 When you need to define a specific view for a given SharePoint field and ensure the view is always used when the field is rendered, this is a good option.
 
-**Getting started**
+### Getting started
 
 The following articles demonstrate how to set the JSLink property on a SPField.
 
 - [Using the JSLink property to change the way your field or views are rendered in SharePoint 2013 (Tobias Zimmergren)](http://zimmergren.net/technical/sp-2013-using-the-spfield-jslink-property-to-change-the-way-your-field-is-rendered-in-sharepoint-2013)
 - [Using JSLink with SharePoint 2013 (MSDN Magazine)](https://msdn.microsoft.com/magazine/dn745867.aspx)
 
-Challenges with implementing client-side rendering with JavaScript files via the JSLink property
-------------------------------------------------------------------------------------------------
+## Challenges with implementing client-side rendering with JavaScript files via the JSLink property
 
 As you develop custom client-side rendering components, keep in mind the following things.
 
 - Not all SharePoint fields may be overridden with the JSLink property.
-	+ The TaxonomyField is a good example.
+  - The TaxonomyField is a good example.
 - JSLink supports several tokens.
-	+ _layouts
-	+ _site
-	+ _siteCollection
-	+ _siteCollectionLayouts
-	+ _siteLayouts
+  - _layouts
+  - _site
+  - _siteCollection
+  - _siteCollectionLayouts
+  - _siteLayouts
 - You can register the JSLink JavaScript files with the SharePoint Script On Demand (SOD) framework to lazy load the file.
-	- Use the (d) tag at the end of the JSLink URL to register the file with the SOD.
- 
-	```
-	~sitecollection/Style Library/JSLink-Samples/DependentFields.js(d)
-	```
+  - Use the (d) tag at the end of the JSLink URL to register the file with the SOD.
+
+      ```text
+      ~sitecollection/Style Library/JSLink-Samples/DependentFields.js(d)
+      ```
+
 - You can load multiple JavaScript files via the JSLink property.
-	+ This is especially helpful if you have a library of JavaScript files that implement your client-side rendering.
-	+ Consider using this approach when targeting mobile devices because it allows you to deliver just the JavaScript you need to implement a given SharePoint field's client-side rendering.
-	+ Use the | character to separate the JavaScript files you wish to load. 
-	
-	```
-	~sitecollection/Style Library/JSLink-Samples/MainLibrary.js|~sitecollection/Style Library/JSLink-Samples/SpecificField.js**(d)**
-	```
+  - This is especially helpful if you have a library of JavaScript files that implement your client-side rendering.
+  - Consider using this approach when targeting mobile devices because it allows you to deliver just the JavaScript you need to implement a given SharePoint field's client-side rendering.
+  - Use the | character to separate the JavaScript files you wish to load.
+
+      ```text
+      ~sitecollection/Style Library/JSLink-Samples/MainLibrary.js|~sitecollection/Style Library/JSLink-Samples/SpecificField.js**(d)**
+      ```
 
 ## Related links
+
 - [SPField.JSLink property (MSDN API Docs)](https://msdn.microsoft.com/library/microsoft.sharepoint.spfield.jslink.aspx)
 - [Using the JSLink property to change the way your field or views are rendered in SharePoint 2013 (Tobias Zimmergren)](http://zimmergren.net/technical/sp-2013-using-the-spfield-jslink-property-to-change-the-way-your-field-is-rendered-in-sharepoint-2013)
 - [Using JSLink with SharePoint 2013 (MSDN Magazine)](https://msdn.microsoft.com/magazine/dn745867.aspx)

docs/solution-guidance/delegate-controls-sharepoint-add-in.md

@@ -1,19 +1,18 @@
 ---
 title: Delegate controls in the SharePoint Add-in model
+description: The approach you take to implement delegate controls in your code is different in the new SharePoint Add-in model than it was with Full Trust Code.  In a typical Full Trust Code (FTC) / Farm Solution scenario, delegate controls were built as user controls or web controls, registered with features, and deployed via SharePoint Solutions.
 ms.date: 05/20/2020
 localization_priority: Normal
 ---
-Delegate controls in the SharePoint Add-in model
-================================================
+# Delegate controls in the SharePoint Add-in model
 
 ## Summary
 
 The approach you take to implement delegate controls in your code is different in the new SharePoint Add-in model than it was with Full Trust Code.  In a typical Full Trust Code (FTC) / Farm Solution scenario, delegate controls were built as user controls or web controls, registered with features, and deployed via SharePoint Solutions.
 
 In an SharePoint Add-in model scenario, JavaScript is embedded in SharePoint pages to implement the same functionality as delegate controls.
 
-High Level Guidelines
----------------------
+## High Level Guidelines
 
 As a rule of a thumb, we would like to provide the following high level guidelines for creating delegate controls in the new SharePoint Add-in model.
 
@@ -24,12 +23,14 @@ As a rule of a thumb, we would like to provide the following high level guidelin
 See the [User controls and web controls (SharePoint Add-in Model Recipe)](user-controls-and-web-controls-sharepoint-add-in.md) to learn how to embed JavaScript to all SharePoint pages with custom user actions and how to embed JavaScript directly into page layouts and master pages.
 
 ## Related links
+
 - [Cross site collection navigation (O365 PnP Video)](https://channel9.msdn.com/blogs/OfficeDevPnP/Cross-site-collection-navigation)
 - Guidance articles at [https://aka.ms/OfficeDevPnPGuidance](https://aka.ms/OfficeDevPnPGuidance "Guidance Articles")
 - References in MSDN at [https://aka.ms/OfficeDevPnPMSDN](https://aka.ms/OfficeDevPnPMSDN "References in MSDN")
 - Videos at [https://aka.ms/OfficeDevPnPVideos](https://aka.ms/OfficeDevPnPVideos "Videos")
 
 ## PnP samples
+
 - [OD4B.NavLinksInjection (O365 PnP Sample)](https://github.com/SharePoint/PnP/tree/master/Samples/OD4B.NavLinksInjection)
 - Samples and content at [Microsoft 365 Patterns and Practices (PnP)](https://aka.ms/sppnp)