Merge pull request SharePoint#8042 from dereklh7/AbsoluteLink-6-6-2

Validation: Removed Absolute Links and Added Missing Descriptions

Author: andrewconnell

docs/solution-guidance/Sandbox-Solution-Transformation-Guidance.md

@@ -1,7 +1,7 @@
 ---
 title: Transform sandbox solutions to the SharePoint Add-in model
 description: Learn about the options and strategies for converting existing code-based functionalities to SharePoint Add-in model or alternative solutions.
-ms.date: 4/22/2020
+ms.date: 06/07/2022
 ms.localizationpriority: high
 ---
 
@@ -84,9 +84,9 @@ Following are typical customizations that are included in the sandbox solutions
 |:-----|:-----|
 |Declarative solution with empty assembly|<p>You can control assembly creation from Visual Studio solution project properties. For more information, see [Remove the assembly reference from your Sandbox solution created in Visual Studio](https://support.microsoft.com/help/3183084/remove-the-assembly-reference-from-your-sandbox-solution-created-in-vi). </p><br/><br/>**Important:** When you use the SharePoint Sandbox Solution scanner, the scan output lists which solutions have an empty assembly, and the tool creates updated sandbox solution packages for you in which the assembly is dropped. You can then simply replace the existing sandbox solution with the updated one.</p> |
 |InfoPath form with code|<p>If you have published an InfoPath form from the InfoPath client that contains code, it’s actually published to SharePoint as a sandbox solution. This means that the form code is actually executed by the sandbox engine in SharePoint.</p> <p>Moving away from the code-based InfoPath forms is dependent on the actual business use case. There are multiple options from generating custom UI as add-ins or utilizing other form techniques.</p><p>For more information, see [Fix InfoPath in sandbox solutions](sandbox-solution-transformation-guidance-infopath.md).</p>|
-|Web part|<p>Web parts are typically converted either to add-in parts or they are implemented with fully client-side technologies by using the JavaScript embed pattern. </p><p>For more information, see:<lu><li>[Customize your SharePoint site UI by using JavaScript](customize-your-sharepoint-site-ui-by-using-javascript.md)</li><li>[Create add-in parts to install with your SharePoint Add-in](../sp-add-ins/create-add-in-parts-to-install-with-your-sharepoint-add-in.md)</li><li>[How to update your SharePoint pages via the embedding of JavaScript](https://channel9.msdn.com/blogs/OfficeDevPnP/JavaScript-embedding-demo)</li><li>[Cross site collection navigation](https://channel9.msdn.com/blogs/OfficeDevPnP/Cross-site-collection-navigation)</li></lu></p>|
+|Web part|<p>Web parts are typically converted either to add-in parts or they are implemented with fully client-side technologies by using the JavaScript embed pattern. </p><p>For more information, see: <ul><li>[Customize your SharePoint site UI by using JavaScript](customize-your-sharepoint-site-ui-by-using-javascript.md)</li><li>[Create add-in parts to install with your SharePoint Add-in](../sp-add-ins/create-add-in-parts-to-install-with-your-sharepoint-add-in.md)</li><li>[How to update your SharePoint pages via the embedding of JavaScript](https://channel9.msdn.com/blogs/OfficeDevPnP/JavaScript-embedding-demo)</li><li>[Cross site collection navigation](https://channel9.msdn.com/blogs/OfficeDevPnP/Cross-site-collection-navigation)</li></ul></p>|
 |Visual web part|<p>Visual web parts are transformed in similar ways as normal web parts. User controls used in visual web parts must be replaced because in sandbox solution cases, it's included inside of the assembly.</p>|
-|Event receiver|<p>Event receivers can in many cases be replaced with the remote event receiver implementation. Remote event receivers do, however, need to hosted on some platform, typically on specific provider-hosted add-ins.</p><p>For more information, see:<lu><li>[Use remote event receivers in SharePoint](use-remote-event-receivers-in-sharepoint.md)</li><li>[How to use remote event receivers for your SharePoint add-ins](https://channel9.msdn.com/blogs/OfficeDevPnP/How-to-use-remote-event-receivers-for-your-SharePoint-add-ins)</li></lu></p>|
+|Event receiver|<p>Event receivers can in many cases be replaced with the remote event receiver implementation. Remote event receivers do, however, need to hosted on some platform, typically on specific provider-hosted add-ins.</p><p>For more information, see: <ul><li>[Use remote event receivers in SharePoint](use-remote-event-receivers-in-sharepoint.md)</li><li>[How to use remote event receivers for your SharePoint add-ins](https://channel9.msdn.com/blogs/OfficeDevPnP/How-to-use-remote-event-receivers-for-your-SharePoint-add-ins)</li></ul></p>|
 |Feature receiver|<p>Feature receivers are typically replaced with a remote API based operation, such as using CSOM or REST for applying the needed customization or configuration at the site level. If a needed API is missing from the remote APIs (CSOM/REST), report this gap by using [SharePoint UserVoice](https://sharepoint.uservoice.com/).</p><p>Feature receivers are used, for example, to set a custom master page or theme to a site when they are activated. These kinds of operations can be easily replaced with remote code-based solutions or by using [PnP PowerShell](https://github.com/SharePoint/PnP-PowerShell/blob/master/README.md), which provides easy commands for controlling site configuration.</p>|
 |Custom workflow action|<p>The typical code migration path for these kinds of customizations is to use SharePoint workflows or alternative solutions such as Microsoft Flow or third-party solutions.</p>| 
 

docs/solution-guidance/Set-external-sharing-on-site-collections-in-Office-365.md

@@ -1,6 +1,7 @@
 ---
 title: Set external sharing on site collections in Office 365
-ms.date: 11/03/2017
+description: Describes how to set external sharing on site collections in Microsoft Office 365 and outlines how to use the Core.ExternalSharing application.
+ms.date: 06/07/2022
 ms.localizationpriority: high
 ---
 # Set external sharing on site collections in Office 365

docs/solution-guidance/SharePoint-pages-and-the-page-model.md

@@ -1,7 +1,7 @@
 ---
 title: SharePoint pages and the page model
 description: Introduction to the SharePoint page model, including master pages, content pages, parts of a SharePoint page, and default page file types.
-ms.date: 4/23/2018
+ms.date: 06/07/2022
 ms.localizationpriority: high
 ---
 
@@ -141,7 +141,7 @@ When a SharePoint user loads a wiki page (either by using the Enterprise wiki te
 
 To learn more about how to provision a wiki page by using the remote provisioning pattern, see the [Provisioning.Pages](https://github.com/SharePoint/PnP/tree/master/Samples/Provisioning.Pages) sample.
 
-### Minimal download strategy and <AjaxDelta> controls
+### Minimal download strategy and \<AjaxDelta\> controls
 
 In SharePoint, the minimal download strategy feature manages which specific content on a master page to refresh before the page renders. When the strategy is enabled, the content associated with content placeholders wrapped in  `<SharePoint:AjaxDelta>` tags on the master page refreshes before the page renders. Conversely, content placeholders not wrapped in `<SharePoint:AjaxDelta>` tags does not render when the minimal download strategy is enabled.
 

docs/solution-guidance/pnp-remote-timer-job-framework.md

@@ -1,7 +1,7 @@
 ---
 title: PnP remote timer job framework
-description:
-ms.date: 5/9/2018
+description: Describes the PnP remote timer job framework, provides a table that outlines a description for various articles, and provides additional references.
+ms.date: 06/07/2022
 ms.localizationpriority: medium
 ---
 

docs/solution-guidance/portal-navigation.md

@@ -1,7 +1,7 @@
 ---
 title: Navigation solutions for SharePoint Online portals
 description: Explains the pros and cons of using an out-of-the-box navigation solution versus a custom navigation solution.
-ms.date: 4/30/2018
+ms.date: 06/07/2022
 ms.localizationpriority: high
 ---
 
@@ -189,7 +189,7 @@ For more information about the Client-Side Data Access Layer, see [Performance g
 ## See also
 
 - [Navigation options for SharePoint Online](https://support.office.com/article/Navigation-options-for-SharePoint-Online-adb92b80-b342-4ecb-99a1-da2a2b4782eb?ui=en-US&rs=en-US&ad=US)
-- [Overview of managed navigation in SharePoint Server](https://docs.microsoft.com/SharePoint/administration/overview-of-managed-navigation)
+- [Overview of managed navigation in SharePoint Server](/SharePoint/administration/overview-of-managed-navigation)
 - [PnP O365 Starter Intranet - Navigation implementation](http://thecollaborationcorner.com/2016/08/31/part-4-the-navigation-implementation/#.WNoU5oVOKiM)
 - [ASP.NET Web API 2](https://msdn.microsoft.com/library/dn448365(v=vs.118))
 - [Azure AD Authentication Library for JavaScript (GitHub)](https://github.com/AzureAD/azure-activedirectory-library-for-js)

docs/solution-guidance/portal-overview.md

@@ -1,7 +1,7 @@
 ---
 title: Building well performing classic publishing portals for SharePoint Online
 description: Guidelines for developing well-performing SharePoint Online portals. 
-ms.date: 4/30/2018
+ms.date: 06/07/2022
 ms.localizationpriority: high
 ---
 
@@ -11,7 +11,7 @@ SharePoint on-premises has been, and is, a popular platform for building enterpr
 
 > [!NOTE]
 > - Although this guidance primarily targets SharePoint Online, most of it also applies to portals hosted in an on-premises SharePoint environment.
-> - Ensuring the portal you design is healthy and does achieve the performance you desire is important, another recommended read is the [Creating and launching a healthy SharePoint portal](https://docs.microsoft.com/sharepoint/portal-health) documentation which covers both classic and modern portals.
+> - Ensuring the portal you design is healthy and does achieve the performance you desire is important, another recommended read is the [Creating and launching a healthy SharePoint portal](/sharepoint/portal-health) documentation which covers both classic and modern portals.
 
 ## Why we created these guidelines
 
@@ -59,5 +59,5 @@ The following table contains an overview of the individual articles that are par
 
 ## See also
 
-- [Creating and launching a healthy SharePoint portal](https://docs.microsoft.com/sharepoint/portal-health)
+- [Creating and launching a healthy SharePoint portal](/sharepoint/portal-health)
 - [Office 365 development and SharePoint PnP solution guidance](office-365-development-patterns-and-practices-solution-guidance.md)

docs/solution-guidance/search-api-usage-sharepoint-add-in.md

@@ -1,7 +1,7 @@
 ---
 title: Search API usage in the SharePoint Add-in model
 description: The approach you take to execute searches with the SharePoint Search Service 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, the SharePoint server-side object model (Content By Query web part overrides) or the Search Web Services were used to execute searches with the SharePoint Search Service.
-ms.date: 12/29/2020
+ms.date: 06/07/2022
 ms.localizationpriority: medium
 ---
 # Search API usage in the SharePoint Add-in model
@@ -161,7 +161,7 @@ In this option you use the REST API to execute searches with the SharePoint Sear
 
 - This API is the most flexible because it is available in both server-side and client-side code.
 - The SharePoint Search Service REST API root endpoint is:
-  - https://<tenant>/site/_api/search/query
+  - https://\<tenant\>/site/_api/search/query
 - Here are some simple examples:
   - Keyword search