Removed disallowed HTML

Author: dereklh7

docs/sp-add-ins/add-a-web-part-to-a-page-in-a-sharepoint-hosted-sharepoint-add-in.md

@@ -1,7 +1,7 @@
 ---
 title: Add a web part to a page in a SharePoint-hosted SharePoint Add-in
 description: Add a web part to a page, and run and test the add-in.
-ms.date: 06/22/2021
+ms.date: 06/13/2022
 ms.prod: sharepoint
 ms.localizationpriority: high
 ---
@@ -18,8 +18,8 @@ In this article, you add a web part to the default page of the Employee Orientat
 ## Add a web part to a page
 
 1. In **Solution Explorer**, open the Default.aspx file.
-1. Because we'll be adding a list view web part to the page that surfaces the New Employees in Seattle list, we no longer need a link to the list view page for the list. Remove the **<asp:HyperLink>** element from the **<asp:Content>** element whose **ContentPlaceHolderId** is `PlaceHolderMain`.
-1. Inside the same **<asp:Content>** element, add the following **WebPartZone**.
+1. Because we'll be adding a list view web part to the page that surfaces the New Employees in Seattle list, we no longer need a link to the list view page for the list. Remove the **\<asp:HyperLink\>** element from the **\<asp:Content\>** element whose **ContentPlaceHolderId** is `PlaceHolderMain`.
+1. Inside the same **\<asp:Content\>** element, add the following **WebPartZone**.
 
     ```XML
       <WebPartPages:WebPartZone runat="server" FrameType="TitleBarOnly"
@@ -32,7 +32,7 @@ In this article, you add a web part to the default page of the Employee Orientat
 1. In the **File** element, add a child **AllUsersWebPart** element, and set its **WebPartZoneID** to the ID of the web part zone that you created on the page. The file's contents should now look like the following. This markup tells SharePoint to insert an **AllUsersWebPart** into the web part zone that is named "HomePage1".
 
     ```xml
-    <Elements xmlns="http://schemas.microsoft.com/sharepoint/">
+    <Elements xmlns="https://schemas.microsoft.com/sharepoint/">
       <Module Name="Pages">
         <File Path="Pages\Default.aspx" Url="Pages/Default.aspx" ReplaceContent="TRUE" >
           <AllUsersWebPart WebPartZoneID="HomePage1" WebPartOrder="1">
@@ -59,7 +59,7 @@ In this article, you add a web part to the default page of the Employee Orientat
 1. Add the following **webPart** markup as a child of the **webParts** element. This markup adds an **XsltListViewWebPart** and tells the web part to show the **New Employees in Seattle** list. Note that the **ViewContentTypeId** property value is just `0x`, not the actual ID of the **NewEmployee** content type.
 
     ```xml
-    <webPart xmlns="http://schemas.microsoft.com/WebPart/v3">
+    <webPart xmlns="https://schemas.microsoft.com/WebPart/v3">
       <metaData>
         <type name="Microsoft.SharePoint.WebPartPages.XsltListViewWebPart,
                       Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral,

docs/sp-add-ins/add-in-permissions-in-sharepoint.md

@@ -295,7 +295,7 @@ SharePoint Add-ins that are installed to SharePoint are granted permissions when
 
 When you are developing an add-in or troubleshooting an add-in, there may be occasions when you want to change, or regrant, the permissions of an add-in that has already been installed. You can do so with these steps:
 
-1. Go to `http://<SharePointWebSite>/_layouts/15/AppInv.aspx`, where  _<SharePointWebSite>_ is the URL of the website where the add-in is installed. Be careful not to add any query parameters on the URL. The form you need only appears on this page if the URL is exactly as shown.
+1. Go to `http://<SharePointWebSite>_layouts/15/AppInv.aspx`, where  _\<SharePointWebSite\>_ is the URL of the website where the add-in is installed. Be careful not to add any query parameters on the URL. The form you need only appears on this page if the URL is exactly as shown.
 
 2. Enter the add-in's ID, also called the client ID, in the **Add-in Id** box, and then select **Lookup**. The other boxes on the form are then populated with information about the add-in.
 

docs/sp-add-ins/authorization-code-oauth-flow-for-sharepoint-add-ins.md

@@ -1,7 +1,7 @@
 ---
 title: Authorization Code OAuth flow for SharePoint Add-ins
 description: The OAuth flow for add-ins that request permission to access SharePoint resources on the fly, and how to use the **OAuthAuthorize.aspx** page and the SharePoint redirect URI.
-ms.date: 06/22/2021
+ms.date: 06/13/2022
 ms.prod: sharepoint
 ms.localizationpriority: high
 ---
@@ -128,7 +128,7 @@ The Fabrikam SharePoint Online site asks ACS to create a short-lived (approximat
 
 The Fabrikam SharePoint Online site redirects the browser back to Contoso via HTTP 302 Response. The URL construct for this redirection uses the redirect URI that was specified when the photo-printing add-in was registered. It also includes the authorization code as a query string.
 
-The redirect URL is structured like the following: **https://contoso.com/RedirectAccept.aspx?code=<authcode>**
+The redirect URL is structured like the following: **https://contoso.com/RedirectAccept.aspx?code=\<authcode\>**
 
 #### Step 6: The add-in uses the authorization code to request an access token from ACS, which validates the request, invalidates the authorization code, and then sends access and refresh tokens to the add-in
 

docs/sp-add-ins/convert-an-autohosted-sharepoint-add-in-to-a-provider-hosted-add-in.md

@@ -1,7 +1,7 @@
 ---
 title: Convert an autohosted SharePoint Add-in to a provider-hosted add-in
 description: Steps to convert an autohosted SharePoint Add-in to a provider-hosted add-in, including deploying to Azure SQL, creating an Azure website, and registering the add-in.
-ms.date: 12/27/2017
+ms.date: 06/13/2022
 ms.prod: sharepoint
 ms.localizationpriority: medium
 ---
@@ -217,7 +217,7 @@ The next step is to reconfigure the remote web application so that it can be dep
 
 ### To update the remote web application project
 
-The big change that needs to occur in the ASP.NET MVC web application is within the web.config file. Within this file there are three settings found within the **<appSettings>** node. These are the **ClientId**, **ClientSecret**, and **SqlAzureConnectionString**. The first two are used by the Microsoft-provided class, in TokenHelper.cs or .vb, to facilitate authenticating and communicating with SharePoint from the remote web application. The latter,  **SqlAzureConnectionString**, is used by the add-in to connect to the Azure SQL Database.
+The big change that needs to occur in the ASP.NET MVC web application is within the web.config file. Within this file there are three settings found within the **\<appSettings\>** node. These are the **ClientId**, **ClientSecret**, and **SqlAzureConnectionString**. The first two are used by the Microsoft-provided class, in TokenHelper.cs or .vb, to facilitate authenticating and communicating with SharePoint from the remote web application. The latter,  **SqlAzureConnectionString**, is used by the add-in to connect to the Azure SQL Database.
 
 In a SharePoint autohosted add-in, Office 365 fills in the values for these settings when the Azure website and Azure SQL Database are created when the add-in is installed. However, in a provider-hosted add-in, these must be manually set before the add-in is deployed.
 
@@ -300,7 +300,7 @@ The last step is to reconfigure the SharePoint Add-in project. The Visual Studio
     > [!IMPORTANT] 
     > If the existing ProductId was used, SharePoint returns the error "The provided add-in differs from another add-in with the same version and product ID" when the converted add-in is installed.
  
-7. Find the **<RemoteWebApplication>** element and update the **ClientId** attribute to be the same GUID that was obtained when registering the add-in with SharePoint and that was used in the Azure website's web.config add-in settings.
+7. Find the **\<RemoteWebApplication\>** element and update the **ClientId** attribute to be the same GUID that was obtained when registering the add-in with SharePoint and that was used in the Azure website's web.config add-in settings.
 
     ![Client ID attribute in app manifest](../images/ConvertAuto2ProviderFig22.jpg)
 

docs/sp-add-ins/create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-conte.md

@@ -1,7 +1,7 @@
 ---
 title: Create a provider-hosted add-in that includes a custom SharePoint list and content type
 description: Create a SharePoint Add-in that combines a cloud-hosted web application with custom SharePoint-hosted list templates, list instances, and custom content types by using the Office Developer Tools for Visual Studio. 
-ms.date: 12/26/2017
+ms.date: 06/13/2022
 ms.prod: sharepoint
 ms.localizationpriority: high
 ---
@@ -421,9 +421,9 @@ For the continuing example, you develop an ASP.NET web application. Take the fol
 
   <br/>
 
-9. Add the following code to parse the ATOM-formatted response XML. It uses the classes of the [System.Xml.Linq](https://msdn.microsoft.com/library/bb299195) namespace to parse the data that is returned and construct a [List<T>](https://msdn.microsoft.com/library/6sh2ey19) of the items from the SharePoint list. (You could also use the classes of the [System.Xml](https://msdn.microsoft.com/library/y3y47afh) namespace.) 
+9. Add the following code to parse the ATOM-formatted response XML. It uses the classes of the [System.Xml.Linq](https://msdn.microsoft.com/library/bb299195) namespace to parse the data that is returned and construct a [List\<T\>](https://msdn.microsoft.com/library/6sh2ey19) of the items from the SharePoint list. (You could also use the classes of the [System.Xml](https://msdn.microsoft.com/library/y3y47afh) namespace.) 
 
-  Note that, in the XML that SharePoint returns, the child elements of the **entry** element hold metadata about the list item. The actual row data of a SharePoint list item is nested two layers down in the **properties** element. For that reason the [Elements<T>](https://msdn.microsoft.com/library/bb348465) extension method is used twice to filter out the higher levels.
+  Note that, in the XML that SharePoint returns, the child elements of the **entry** element hold metadata about the list item. The actual row data of a SharePoint list item is nested two layers down in the **properties** element. For that reason the [Elements\<T\>](https://msdn.microsoft.com/library/bb348465) extension method is used twice to filter out the higher levels.
 
   ```csharp
     // Response markup parsing section
@@ -440,7 +440,7 @@ For the continuing example, you develop an ASP.NET web application. Take the fol
 
   <br/>
 
-10. Add the following LINQ query to construct an [IEnumerable<T>](https://msdn.microsoft.com/library/9eekhta0) collection of an anonymous type that has just the properties you need and no others. Note that although the code must refer to the item title field by its internal name `Title`, the property name in the anonymous type, to which the value is assigned, can be named `Character`. One effect of this is that when the collection is bound to a grid control, the more appropriate name **Character** appears on the page.
+10. Add the following LINQ query to construct an [IEnumerable\<T\>](https://msdn.microsoft.com/library/9eekhta0) collection of an anonymous type that has just the properties you need and no others. Note that although the code must refer to the item title field by its internal name `Title`, the property name in the anonymous type, to which the value is assigned, can be named `Character`. One effect of this is that when the collection is bound to a grid control, the more appropriate name **Character** appears on the page.
 
   ```csharp
     var entryFieldValues = from entry in entries

docs/sp-add-ins/include-a-web-part-in-a-webpage-on-the-add-in-web.md

@@ -1,7 +1,7 @@
 ---
 title: Include a web part on a webpage in the add-in web
 description: Include an out-of-the-box web part on a page in the add-in web of a SharePoint Add-in.
-ms.date: 06/22/2021
+ms.date: 06/13/2022
 ms.prod: sharepoint
 ms.localizationpriority: medium
 ---
@@ -25,7 +25,7 @@ For a code sample that illustrates the guidance of this topic, see [OfficeDev/Co
     ```
 
     > [!WARNING]
-    > It is possible to add a web part element, such as **<WebPartPages:XsltListViewWebPart>** as a child of the **WebPartZone**. But this is generally a bad practice in a SharePoint Add-in. If the add-in ever needs to be updated, a web part element inserted in the .aspx file can cause the update to fail in some scenarios with the message "A web part with this ID has already been added to this page." We recommend that you add web parts to the elements manifest for the page as described later in this procedure.
+    > It is possible to add a web part element, such as **\<WebPartPages:XsltListViewWebPart\>** as a child of the **WebPartZone**. But this is generally a bad practice in a SharePoint Add-in. If the add-in ever needs to be updated, a web part element inserted in the .aspx file can cause the update to fail in some scenarios with the message "A web part with this ID has already been added to this page." We recommend that you add web parts to the elements manifest for the page as described later in this procedure.
 
 1. Open the element manifest file for the page. This is usually called elements.xml and is located in the same project folder as the .aspx file.
 1. In the **File** element for the page, add a child **AllUsersWebPart** element, and set its **WebPartZoneID** to the value of the web part zone that you created on the page, as this example shows.