Update anchor links to avoid warning

Author: juliakm

docs/boards/backlogs/add-link.md

@@ -261,7 +261,7 @@ For more information, see [Link to work items from pull requests, commits, and c
 
 ::: moniker range=">= azure-devops-2019" 
 
-<a id="link-github" />
+<a id="link-github"></a>
 
 ## Link work items to GitHub objects
 ::: moniker-end
@@ -508,7 +508,7 @@ From the **Add link** dialog, you can open a secondary dialog to help you choose
     - From Visual Studio: Select each work item that should link to the current work item. You can also press the SHIFT key while clicking to select a range of work items, or press the CTRL key while clicking to select multiple work items.  
 ::: moniker-end
 
-<a id="azure-cli" />
+<a id="azure-cli"></a>
 
 ::: moniker range="azure-devops" 
 

docs/boards/backlogs/add-work-items.md

@@ -177,7 +177,7 @@ There's no way to use Visual Studio 2019 to update a work item at this time.
 
 [Update work item](#update-work-item) | [Show work item details](#show-work-item) 
 
-<a id="update-work-item" />  
+<a id="update-work-item"></a>  
 
 ### Update a work item
 
@@ -228,7 +228,7 @@ ID    Type    Title                Assigned To          State
 864   Bug     Fix security issues  contoso@contoso.com  New
 ```
 
-<a id="show-work-item" />  
+<a id="show-work-item"></a>  
 
 #### Add comments to a discussion
 

docs/boards/backlogs/backlogs-overview.md

@@ -114,7 +114,7 @@ You build your project plan by creating a backlog of work items. These items rep
 
 [![Define stories conceptual image of tasks.](media/overview/gs-planning-define-stories.png)](create-your-backlog.md)[![Organize backlog conceptual image of tasks.](media/overview/gs-planning-organize-backlog.png)](organize-backlog.md)[![Manage bugs conceptual image of tasks.](media/overview/gs-planning-manage-bugs.png)](manage-bugs.md)[![Manage issues conceptual image of tasks.](media/overview/gs-planning-manage-issues.png)](manage-issues-impediments.md)
 
-<a id="stack-rank" />
+<a id="stack-rank"></a>
 
 ## Backlog priority or stack rank order
 
@@ -260,7 +260,7 @@ You can only use dragging to reorder or reparent work items assigned to area pat
 
 :::image type="content" source="../plans/media/config-teams/information-message-owned-by-other-team.png" alt-text="Screenshot of information message on team ownership.":::
 
-<a id="leaf-node" />
+<a id="leaf-node"></a>
 
 ## Display leaf node work items  
 

docs/boards/backlogs/create-your-backlog.md

@@ -128,7 +128,7 @@ To select another team, open the project and team selector. Select a different t
 
 Some teams like to track bugs along with requirements on the backlog. Other teams like to track bugs as tasks completed in support of a requirement, so that bugs appear on their [Taskboard](../sprints/task-board.md). Before you determine how to manage bugs, see [Configure and customize, Treat bugs as requirements or tasks](../configure-customize.md#show-bugs) and [Show bugs on backlogs and boards](../../organizations/settings/show-bugs-on-backlog.md). 
 
-<a id="convert-ideas" />
+<a id="convert-ideas"></a>
 
 ## Convert ideas into backlog items 
 
@@ -294,7 +294,7 @@ To plan a sprint, at a minimum, estimate the effort involved to implement each b
    :::column-end:::
 :::row-end:::
 
-<a id="show-hide-in-progress" />  
+<a id="show-hide-in-progress"></a>  
 
 ## Show or hide In Progress Items
 
@@ -324,7 +324,7 @@ Choose **In progress items** show or hide **In Progress** backlog items. If you
 
 You'd likely choose to hide **In Progress items** when you want to forecast work. For more information, see [Forecast your product backlog](../sprints/forecast.md).
 
-<a id="show-hide-completed" />  
+<a id="show-hide-completed"></a>  
 
 ::: moniker range=">= azure-devops-2020"
 

docs/boards/backlogs/filter-backlogs-boards-plans.md

@@ -725,7 +725,7 @@ To learn more about these other functions, see the following articles:
 ::: moniker-end 
 
 
-<a id="parent-filter" /> 
+<a id="parent-filter"></a> 
 
 ### Parent Work Item filter and Parent field
 
@@ -839,7 +839,7 @@ Filters remain in place until you explicitly clear them.  When you refresh your
 
 Once the board is filtered, you can choose the filter icon to hide the drop downs and view the applied filters on the board. The filter icon turns opaque to signify a filtered board.
 
-<a id="keep hierarchy" /> 
+<a id="keep hierarchy"></a> 
 
 ::: moniker range="azure-devops"
 
@@ -864,7 +864,7 @@ The keyword filter function filters lists or cards based on the fields displayed
 
 Filtering is case-insensitive. 
 
-<a id="characters-ignore" />  
+<a id="characters-ignore"></a>  
 
 ### Ignore characters by keyword filter criteria
 
@@ -905,7 +905,7 @@ Here we filter the Backlog with **Show Parents** enabled, to only show work item
 The filtered set is always a flat list, even if you've selected to show parents. 
 
 
-<a id="field-filter" />
+<a id="field-filter"></a>
 
 ## Filter based on a field  
 
@@ -992,7 +992,7 @@ Here, we choose two features on which to filter the board.
 
 The final board displays just those stories linked as child work items to the selected features.
 
-<a id="tags" />
+<a id="tags"></a>
 
 ## Filter based on tags
 

docs/boards/backlogs/manage-bugs.md

@@ -447,15 +447,15 @@ One of the methods used by Azure DevOps to support integration is to link object
 You can add a link from the work item or from the build and release objects. 
 
 
-<a id="development-control" />
+<a id="development-control"></a>
 
 ### Link work items to development 
 
 The **Development** control supports linking to and displaying links made to builds, Git commits and pull requests. Or, when a TFVC repository is used, it supports links to changesets and versioned items. Choosing the link opens the corresponding item in a new browser tab. For more information, see [Drive Git development from a work item](connect-work-items-to-git-dev-ops.md).  
 > [!div class="mx-imgBorder"]  
 > ![Development control on work item form with sample links to build, pull requests, and commits.](media/manage-bugs/development-links.png)  
 
-<a id="deployment-control" />
+<a id="deployment-control"></a>
 
 ### Link work items to releases   
 

docs/boards/backlogs/manage-issues-impediments.md

@@ -129,7 +129,7 @@ Impediments and issues don't appear on your backlog. Instead, you track them usi
 
 ::: moniker-end
 
-<a id="add-to-backlog" /> 
+<a id="add-to-backlog"></a> 
 
 ## Add issues or impediments to your product backlog  
 

docs/boards/backlogs/office/bulk-add-modify-work-items-excel.md

@@ -212,7 +212,7 @@ You can and can't do the following tasks from an Excel worksheet:
 
     :::image type="content" source="media/excel/2019-input-list-dialog.png" alt-text="Screenshot of Select input list.":::
 
-5.  <a id="step-5" />Your worksheet is now bound to your project as an input list (Query[None]), flat list.  
+5.  <a id="step-5"></a>Your worksheet is now bound to your project as an input list (Query[None]), flat list.  
 
 	:::image type="content" source="media/excel/2019-input-list.png" alt-text="Screenshot of Empty flat list connected to a project."::: 
 
@@ -300,7 +300,7 @@ You can add a hierarchy of work items linked using parent-child links or other t
 
     You can use the ![indent item in tree](media/bulk-modify-excel-indent-inline.png) or ![Outdent item in tree](media/bulk-modify-excel-outdent-inline.png) indent/outdent icons to demote or promote a work item within the tree hierarchy. The header at the top of the column should read **Title n**, if it doesn't, add a tree level.
 
-<a id="remove-tree-level" />
+<a id="remove-tree-level"></a>
 
 ### Remove a tree level
 
@@ -395,7 +395,7 @@ To convert your query list to an input list, follow these steps.
 
 	:::image type="content" source="media/excel/configure-list-properties-dialog-refresh-query.png" alt-text="Screenshot of Configure List properties dialog, Query.":::
 
-<a id="get-work-items" />
+<a id="get-work-items"></a>
 
 ## Add existing work items to your worksheet 
 

docs/boards/backlogs/remove-delete-work-items.md

@@ -138,7 +138,7 @@ To cause removed items to not show up in queries, you must add a clause that fil
 ::: moniker-end
 
 <a id="delete"> </a> 
-<a id="delete-work-items" />
+<a id="delete-work-items"></a>
 
 ### Delete work items   
 
@@ -203,8 +203,8 @@ You can delete work items in one of the following ways:
 	> The Delete work items confirmation dialog for on-premises Azure DevOps may indicate there are auto-delete settings (disabled). There are no settings you can enable or disable. There is only a background process which permanently deletes work items that have been set to delete.   
 ::: moniker-end
 
-<a id="restore" />
-<a id="restore-or-permanently-delete-work-items" />
+<a id="restore"></a>
+<a id="restore-or-permanently-delete-work-items"></a>
 
 ## Restore or destroy work items  
 
@@ -236,7 +236,7 @@ Restore deleted work items or permanently delete them from the web portal **Recy
 > [!NOTE]
 > Deleted test artifacts don't appear in the **Recycle Bin** and can't be restored. When you delete a test artifact, all of its associated child items, such as child test suites, test points across all configurations, testers (the underlying test case work item doesn't get deleted), test results history, and other associated history also get deleted.
 
-<a id="az-boards-cli" />
+<a id="az-boards-cli"></a>
 
 ::: moniker range="azure-devops" 
 

docs/boards/backlogs/set-up-your-backlog.md

@@ -70,7 +70,7 @@ As shown in the following image, (1) choose the team, (2) **Work**, (3) **Backlo
 Look up your team's Area Path(s) and Iteration Paths. For more information, see [Define area paths and assign to a team](../../organizations/settings/set-area-paths.md) and 
 [Define sprint paths and configure team iterations](../../organizations/settings/set-iteration-paths-sprints.md#activate). 
 
-<a id="sprint" />
+<a id="sprint"></a>
 
 ## Default sprint backlog and Taskboard work items
 
@@ -180,7 +180,7 @@ To learn more about checklists, see the following articles:
 ::: moniker-end
 
 
-<a id="customize-checklist-2019" />
+<a id="customize-checklist-2019"></a>
 
 ::: moniker range=">= azure-devops-2019"
 
@@ -205,7 +205,7 @@ Your team can also choose to hide or show one or more backlog levels. Feature te
 
 For more information, see [Select backlog navigation levels for your team](../../organizations/settings/select-backlog-navigation-levels.md). 
 
-<a id="add-custom-types" />
+<a id="add-custom-types"></a>
 
 ## Add custom work item types to your backlogs and portfolio backlog levels  
 
@@ -251,7 +251,7 @@ For more information, see the following resources:
 
 ::: moniker-end
 
-<a id="taskboard-types" /> 
+<a id="taskboard-types"></a> 
 
 ## Add custom work item types to your Taskboard
 

docs/boards/backlogs/work-item-template.md

@@ -169,7 +169,7 @@ Depending on the platform, version, and client you use, you might need to follow
 
 ### [Web portal](#tab/browser/)
 
-<a id="team-services-capture" /> 
+<a id="team-services-capture"></a> 
 
 ::: moniker range=">= azure-devops-2019"  
 
@@ -219,11 +219,11 @@ Templates captured through the web portal are assigned a GUID.
 
 ::: moniker-end  
 
-<a id="tfs-portal-capture" /> 
+<a id="tfs-portal-capture"></a> 
 
 ### [Visual Studio 2015](#tab/visual-studio/)
 
-<a id="team-explorer-capture" />
+<a id="team-explorer-capture"></a>
 
 To create work items from templates in Visual Studio or Team Explorer, you can use work item template files (.wt extension). These files are accessible from the Work Items page.
 
@@ -253,7 +253,7 @@ For each work item type, you can see and manage the templates that your team has
 
 ::: moniker range=">= azure-devops-2019"
 
-<a id="team-services-manage" /> 
+<a id="team-services-manage"></a> 
 
 1. From the web portal, open **Project settings**.
 
@@ -267,7 +267,7 @@ For each work item type, you can see and manage the templates that your team has
 
 ::: moniker-end
 
-<a id="team-services-manage" /> 
+<a id="team-services-manage"></a> 
 
 ::: moniker range="tfs-2018"
 
@@ -311,7 +311,7 @@ For example, choose **User Story** to view templates defined for capturing user
 
 ::: moniker-end
 
-<a id="define-template" />
+<a id="define-template"></a>
 
 ### Create a work item template 
 
@@ -336,7 +336,7 @@ From the work item type page, choose  :::image type="icon" source="../media/icon
 
 ### [Visual Studio 2015](#tab/visual-studio/)
 
-<a id="team-explorer-manage" />
+<a id="team-explorer-manage"></a>
 
 You can use Visual Studio with power tools to manage your own work item templates. For each work item type, you can see your defined templates and perform various actions on them. You can add, edit, delete, copy, and copy templates. You can share your templates with others by sending them the template URL or saving the template as a .wt file.
 
@@ -386,7 +386,7 @@ The main method used to add a work item using a template is to open the template
 
 You can apply a template to a single work item or do a bulk update of several work items.  
 
-<a id="team-services-apply" />
+<a id="team-services-apply"></a>
 
 ### [Web portal](#tab/browser/)
 
@@ -452,7 +452,7 @@ You can apply a template to a single work item or do a bulk update of several wo
 
 ### [Visual Studio 2015](#tab/visual-studio/)
 
-<a id="team-explorer-apply" />
+<a id="team-explorer-apply"></a>
 
 1. Open or run a query that lists the work item(s) whose fields you want to capture.  
 

docs/boards/best-practices-agile-project-management.md

@@ -346,7 +346,7 @@ For more information, see the following articles:
 - [Display rollup progress or totals](backlogs/display-rollup.md)
 - [Review team Delivery Plans](plans/review-team-plans.md)
 
-<a id="process-improvement" /> 
+<a id="process-improvement"></a>
 
 ## Process improvement  
 

docs/boards/boards/add-task-checklists.md

@@ -130,7 +130,7 @@ You can drag a task within a work item to reorder it. Or, you can drag the task
 
 Tasks or other child items you add as checklists are automatically assigned to the **Iteration Path** of their parent work item. To reassign a checklist item to a different sprint, you must open the item and change its **Iteration Path**. Or, open the sprint backlogs where it's currently defined and  drag it to the new sprint using the Planning pane. For more information, see [Assign backlog items to a sprint](../sprints/assign-work-sprint.md).  
 
-<a id="checklist-actions" /> 
+<a id="checklist-actions"></a> 
 
 ::: moniker range="azure-devops"
 

docs/boards/boards/wip-limits.md

@@ -27,7 +27,7 @@ For more information, see [Kanban overview](kanban-overview.md).
 
 [!INCLUDE [temp](../includes/prerequisites-team-settings.md)]
 
-<a id="Initial WIP" />
+<a id="Initial WIP"></a>
 
 ## Determine initial WIP limits
 
@@ -37,7 +37,7 @@ Have your team determine the initial WIP limits to set and how to use and monito
 * Set limits that don't exceed two or three items per team member that works within a stage. For example, if you have three team members and each team member can work on no more than two tasks at a time, the resulting WIP limit is 6 (= 3 developers X 2 tasks/developer).
 * Start with low limits to help your team discover bottlenecks more quickly and identify process issues to address.
 
-<a id="Keep within WIP" />
+<a id="Keep within WIP"></a>
 
 ## Keep within WIP limits
 
@@ -51,7 +51,7 @@ Although simple in theory, keeping within WIP limits can force individuals, team
 
 To gain the advantages of constraining work-in-progress, have your team meet frequently to discuss the process changes taking place.
 
-<a id="Keep within WIP" />
+<a id="Keep within WIP"></a>
 
 ## Identify bottlenecks
 
@@ -70,7 +70,7 @@ Such snapshots can show your team the following information:
 * How many and which items remained in a workflow stage/column for long periods of time  
 * How many items did the team complete at the end of a one, two, or three week period 
 
-<a id="Eliminate waste" />
+<a id="Eliminate waste"></a>
 
 ## Eliminate waste
 
@@ -87,7 +87,7 @@ Common wastes in software development include:
 
 Eliminating waste calls for team discussions to identify causes and solutions acceptable to the team.
 
-<a id="Set" />
+<a id="Set"></a>
 
 ## Set WIP limits