Update broken anchor links

andrewconnell · andrewconnell · commit 14ddc265d33a · 2021-01-07T07:18:00.000-05:00
diff --git a/docs/sp-add-ins/create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-conte.md b/docs/sp-add-ins/create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-conte.md
@@ -86,7 +86,7 @@ In the procedures of this section, you create a SharePoint Add-in that includes
 
 You add SharePoint components to an add-in exactly as you would add them to a classic farm solution. However, not every kind of SharePoint component can be included in a SharePoint Add-in. The purposes these components serve are accomplished in other ways in SharePoint Add-ins. 
 
-For detailed information about what kinds of SharePoint components can be included in a SharePoint Add-in and how to include them in a project, see [Types of SharePoint components that can be in a SharePoint Add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#TypesOfSPComponentsInApps).
+For detailed information about what kinds of SharePoint components can be included in a SharePoint Add-in and how to include them in a project, see [Types of SharePoint components that can be in a SharePoint Add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#types-of-sharepoint-components-that-can-be-in-a-sharepoint-add-in).
     
 For purposes of the continuing example, use the following procedures, which provide examples of using Visual Studio to add custom columns, content types, list templates, and list instances to a SharePoint Add-in.
     
diff --git a/docs/sp-add-ins/explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in.md b/docs/sp-add-ins/explore-the-app-manifest-structure-and-the-package-of-a-sharepoint-add-in.md
@@ -18,7 +18,7 @@ A SharePoint Add-in package is a file that has an ".app" extension and that comp
 - **Add-in manifest**: This is a required file that is named appmanifest.xml. It tells SharePoint about some important properties of the add-in, such as its title and the permissions it needs to run. For more information about the contents of this file, see [Add-in for SharePoint manifest file](#AppManifest).
     
  
-- **SharePoint solution packages**: Optionally, the add-in may include a SharePoint solution package (.wsp file) that contains the components of the add-in web. These components may include pages, list instances, views, documents, web-scoped features, and other SharePoint components. (For more information about what SharePoint components can be included in a SharePoint Add-in, see  [Types of SharePoint components that can be in a SharePoint Add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#TypesOfSPComponentsInApps).) The .wsp file may also contain Office Add-ins. The components in the .wsp file are deployed to the add-in web. For an example of an add-in package that includes a SharePoint solution package, see [Create a provider-hosted add-in that includes a custom SharePoint list and content type](create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-conte.md).
+- **SharePoint solution packages**: Optionally, the add-in may include a SharePoint solution package (.wsp file) that contains the components of the add-in web. These components may include pages, list instances, views, documents, web-scoped features, and other SharePoint components. (For more information about what SharePoint components can be included in a SharePoint Add-in, see  [Types of SharePoint components that can be in a SharePoint Add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#types-of-sharepoint-components-that-can-be-in-a-sharepoint-add-in).) The .wsp file may also contain Office Add-ins. The components in the .wsp file are deployed to the add-in web. For an example of an add-in package that includes a SharePoint solution package, see [Create a provider-hosted add-in that includes a custom SharePoint list and content type](create-a-provider-hosted-add-in-that-includes-a-custom-sharepoint-list-and-conte.md).
     
  
 - **Host web features with Custom Actions or add-in parts**: In addition to the SharePoint components that are deployed to the add-in web, a SharePoint Add-in can also deploy one or more custom actions (shortcut menu items or ribbon extensions) to the host web. This is accomplished by including in the add-in package a feature that is not inside the package's .wsp file and that deploys the components that go to the host web. This "loose" feature is called a host web feature. 
diff --git a/docs/sp-add-ins/host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md b/docs/sp-add-ins/host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md
@@ -21,21 +21,21 @@ Figure 1 shows a host web with two SharePoint Add-ins installed. Add-in 1 has re
 
 For example, suppose that an add-in, with SharePoint components beyond just the UI elements that can be deployed to a host web, is installed on a host website at the following URL: 
 
-    ```txt
-    https://www.fabrikam.com/sites/Marketing
-    ```
+```txt
+https://www.fabrikam.com/sites/Marketing
+```
 
 The SharePoint Add-in will be deployed to a newly created website with a URL like the following:
 
-    ```txt
-    http://add-in-bdf2016ea7dacb.fabrikamadd-ins.com/sites/Marketing/Scheduler
-    ```
+```txt
+http://add-in-bdf2016ea7dacb.fabrikamadd-ins.com/sites/Marketing/Scheduler
+```
 
 Note that this URL has the following structure:
 
-    ```txt
-    https://` _Add-in_Prefix_ `-` _Add-in_ID_ `.` _Add-in_Base_Domain_ `/` _Domain_Relative_URL_of_Host_Web_ `/` _Add-in_Name_
-    ```
+```txt
+https://` _Add-in_Prefix_ `-` _Add-in_ID_ `.` _Add-in_Base_Domain_ `/` _Domain_Relative_URL_of_Host_Web_ `/` _Add-in_Name_
+```
 
 The placeholders are defined as follows:
 
@@ -57,7 +57,7 @@ There are two primary reasons why SharePoint components are deployed to add-in w
 In general, a SharePoint Add-in can contain one or more of the components in the following list. With certain exceptions, these components must be deployed in **Web**-scoped Features that are inside a SharePoint solution package (.wsp) file.
 
 > [!NOTE]
-> The components that are marked with an asterisk (\*) are discussed in more detail in the section [Caveats for deploying SharePoint components](#SpecialCases) later in this article.
+> The components that are marked with an asterisk (\*) are discussed in more detail in the section [Caveats for deploying SharePoint components](#caveats-for-deploying-sharepoint-components) later in this article.
 
 - Features (**Web**-scoped only)
 - Custom actions (including shortcut menu items and ribbon customizations)\*
@@ -93,8 +93,8 @@ The following are some caveats and details concerning the deployment of certain
 
     You can also define a custom site type for the add-in web. There are two major steps to doing this:
 
-        - Include a custom [WebTemplate Element (Web Template)](https://msdn.microsoft.com/library/ff4ba91a-cc5f-47ff-9101-a7651f452185%28Office.15%29.aspx), an onet.xml file, and possibly other associated files, in the add-in web Feature for your add-in. Deploy the web template in the Web-scoped Feature in a .wsp file inside the add-in package as usual.
-        - Add a [WebTemplate element (PropertiesDefinition complexType) (SharePoint Add-in Manifest)](https://msdn.microsoft.com/library/62302903-e97a-a9a3-a64e-13176a7c4e1e%28Office.15%29.aspx) to the add-in manifest as a child of the **Properties** element, and set its **Id** attribute to the GUID of the add-in web Feature and the value of the **Name** attribute of the [WebTemplate Element (Web Template)](https://msdn.microsoft.com/library/ff4ba91a-cc5f-47ff-9101-a7651f452185%28Office.15%29.aspx). Note that the GUID must be hyphenated and wrapped in braces "{}", and the GUID and template name are separated by the "#" character. The following is an example:
+    - Include a custom [WebTemplate Element (Web Template)](https://msdn.microsoft.com/library/ff4ba91a-cc5f-47ff-9101-a7651f452185%28Office.15%29.aspx), an onet.xml file, and possibly other associated files, in the add-in web Feature for your add-in. Deploy the web template in the Web-scoped Feature in a .wsp file inside the add-in package as usual.
+    - Add a [WebTemplate element (PropertiesDefinition complexType) (SharePoint Add-in Manifest)](https://msdn.microsoft.com/library/62302903-e97a-a9a3-a64e-13176a7c4e1e%28Office.15%29.aspx) to the add-in manifest as a child of the **Properties** element, and set its **Id** attribute to the GUID of the add-in web Feature and the value of the **Name** attribute of the [WebTemplate Element (Web Template)](https://msdn.microsoft.com/library/ff4ba91a-cc5f-47ff-9101-a7651f452185%28Office.15%29.aspx). Note that the GUID must be hyphenated and wrapped in braces "{}", and the GUID and template name are separated by the "#" character. The following is an example:
 
         ```XML
         <WebTemplate Id="{81dd4ae5-873b-4759-9838-4ad9c3dd2952}#NewSiteType" />
diff --git a/docs/sp-add-ins/localize-sharepoint-add-ins.md b/docs/sp-add-ins/localize-sharepoint-add-ins.md
@@ -10,7 +10,7 @@ localization_priority: Normal
 # Localize SharePoint Add-ins
  
 > [!NOTE] 
-> This topic assumes that you are familiar with the basic creation of SharePoint Add-ins, and with SharePoint features, the distinction between add-in webs and host webs, [the kind of SharePoint components that can be in an add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#TypesOfSPComponentsInApps), and the basics of localization with .resx files.
+> This topic assumes that you are familiar with the basic creation of SharePoint Add-ins, and with SharePoint features, the distinction between add-in webs and host webs, [the kind of SharePoint components that can be in an add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#types-of-sharepoint-components-that-can-be-in-a-sharepoint-add-in), and the basics of localization with .resx files.
  
 <a name="Prerequisites"> </a>
 
@@ -35,7 +35,7 @@ Also, be aware of the following:
 
 ## Localize the add-in web components
 
-An add-in web can contain specific kinds of SP components. For more information about the kinds of SharePoint components that can be in a SharePoint Add-in, see [Types of SharePoint components that can be in a SharePoint Add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#TypesOfSPComponentsInApps). To localize components that are deployed to an add-in web, you add .resx files in modules in the same feature that contains the add-in web component. You reference the resources in the markup of the component. How you do this is explained later in this article. However, custom site pages in a SharePoint Add-in use JavaScript string variable files instead of .resx files, as described later in this section.
+An add-in web can contain specific kinds of SP components. For more information about the kinds of SharePoint components that can be in a SharePoint Add-in, see [Types of SharePoint components that can be in a SharePoint Add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#types-of-sharepoint-components-that-can-be-in-a-sharepoint-add-in). To localize components that are deployed to an add-in web, you add .resx files in modules in the same feature that contains the add-in web component. You reference the resources in the markup of the component. How you do this is explained later in this article. However, custom site pages in a SharePoint Add-in use JavaScript string variable files instead of .resx files, as described later in this section.
  
 > [!NOTE] 
 > Resource files cannot be shared by multiple add-in web features. For each feature in the .wsp file, you have to create separate sets of resource files.
diff --git a/docs/sp-add-ins/set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md b/docs/sp-add-ins/set-up-an-on-premises-development-environment-for-sharepoint-add-ins.md
@@ -126,7 +126,7 @@ The registry path will change in future versions of Visual Studio.
 <a name="SP15appdevonprem_bk_configure"> </a>
 ## Configure an isolated add-in ___domain in SharePoint
 
-Before you carry out any procedures in this section, read [Host webs, add-in webs, and the isolated ___domain](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#IsolatedDomain).
+Before you carry out any procedures in this section, read [Host webs, add-in webs, and the isolated ___domain](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#host-webs-add-in-webs-and-the-isolated-___domain).
 
 You must create an isolated ___domain in your test SharePoint farm. Also, your SharePoint installation needs a general wildcard host header ___domain where it can provision SharePoint-hosted add-ins.
 
@@ -188,7 +188,7 @@ Perform the steps in the following procedure to create an isolated add-in ___domain
 
     ```
 
-7. Specify your add-in prefix (see [Host webs, add-in webs, and the isolated ___domain](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#IsolatedDomain)) by typing the following code in the SharePoint Management Shell:
+7. Specify your add-in prefix (see [Host webs, add-in webs, and the isolated ___domain](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#host-webs-add-in-webs-and-the-isolated-___domain)) by typing the following code in the SharePoint Management Shell:
     
     ```
       Set-SPAppSiteSubscriptionName -Name "add-in" -Confirm:$false
diff --git a/docs/sp-add-ins/update-add-in-web-components-in-sharepoint.md b/docs/sp-add-ins/update-add-in-web-components-in-sharepoint.md
@@ -25,7 +25,7 @@ Other articles in the [Upgrading Features](https://msdn.microsoft.com/library/e9
 
 With a SharePoint-hosted add-in, you can only use XML markup to update an add-in, and there are some limits on how you can declaratively change an add-in in an update. In a provider-hosted add-in, you can implement an [UpdatedEventEndpoint handler](create-a-handler-for-the-update-event-in-sharepoint-add-ins.md) to do things that can't be done declaratively.
 
-Adding components to an add-in is easy. Any component that is eligible to be included in an add-in can also be added in an update (for details, see [Types of SharePoint components that can be in a SharePoint Add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#TypesOfSPComponentsInApps)). But when you want to modify an existing component declaratively, consider the following points. 
+Adding components to an add-in is easy. Any component that is eligible to be included in an add-in can also be added in an update (for details, see [Types of SharePoint components that can be in a SharePoint Add-in](host-webs-add-in-webs-and-sharepoint-components-in-sharepoint.md#types-of-sharepoint-components-that-can-be-in-a-sharepoint-add-in)). But when you want to modify an existing component declaratively, consider the following points. 
 
 - The data type of a list or content type field (column) cannot be changed after its initial deployment in any circumstance. In particular, do not change the data type of a field as part of an add-in update (*not even programmatically*). As an alternative, you can add a new field. If the add-in includes custom item create, edit, or view forms, be sure to make corresponding changes in these forms. For example, add UI for the new field and remove UI for the old one. (In a provider-hosted add-in, you can programmatically move data from the old field to the new one and then delete the old.)
 
