remove html tags and links - part 2

cebundy · cebundy · commit d99fe79741ff · 2024-10-11T14:14:31.000-07:00
diff --git a/docs/boards/faqs.yml b/docs/boards/faqs.yml
@@ -171,7 +171,7 @@ sections:
     questions: 
       - question: What's the difference between a backlog and a board?  
         answer: | 
-          Each backlog and board represents a filtered set of work items based on team area path and iteration path assignments. Backlogs list work items, boards display work items as cards. To understand how the filtering is applied, see [About teams and Agile tools, Team defaults referenced by backlogs and boards](../organizations/settings/about-teams-and-settings.md#team-defaults).
+          Each backlog and board represents a filtered set of work items based on team area path and iteration path assignments. Backlogs list work items, boards display work items as cards. To understand how the filtering is applied, see [About teams and Agile tools, Team defaults referenced by backlogs and boards](../organizations/settings/about-teams-and-settings.md#team-defaults-referenced-by-backlogs-and-board).
 
       - question: How do I add a backlog or board?  
         answer: | 
diff --git a/docs/cli/quick-reference.md b/docs/cli/quick-reference.md
@@ -37,14 +37,14 @@ To start using Azure DevOps CLI, see [Get started with Azure DevOps CLI](index.m
 :::row:::
    :::column span="1":::
       #### Area and Iteration Paths
-      - [Add a project area path](../organizations/settings/set-area-paths.md#add-area) 
+      - [Add a project area path](../organizations/settings/set-area-paths.md#add-an-area-path) 
       - [Add a project iteration](../organizations/settings/set-iteration-paths-sprints.md#add-project-iteration)
       - [Delete or update a project iteration path](../organizations/settings/set-iteration-paths-sprints.md#ename-or-move-an-iteration)
-      - [List project area paths](../organizations/settings/set-area-paths.md#list-areas) 
+      - [List project area paths](../organizations/settings/set-area-paths.md#list-project-areas) 
       - [List project iteration paths](../organizations/settings/set-iteration-paths-sprints.md#list-project-iteration) 
       - [List team areas paths](../organizations/settings/set-area-paths.md#list-team-area-paths) 
       - [List team iteration paths](../organizations/settings/set-iteration-paths-sprints.md#list-team-iterations) 
-      - [Remove area path from a team](../organizations/settings/set-area-paths.md#remove-area-path-from-team)
+      - [Remove area path from a team](../organizations/settings/set-area-paths.md#remove-an-area-path-from-a-team)
       - [Rename or move a project area path](../organizations/settings/set-area-paths.md#rename-move-project-area-path) 
       - [Set team area paths](../organizations/settings/set-area-paths.md#set-team-area-paths) 
       - [Set team iteration paths](../organizations/settings/set-iteration-paths-sprints.md#select-team-sprints-and-set-the-default-iteration-path) 
diff --git a/docs/organizations/settings/about-areas-iterations.md b/docs/organizations/settings/about-areas-iterations.md
@@ -50,7 +50,7 @@ If you're new to managing projects and teams, do the following steps to configur
 
 1. Determine the number and names of **Area Paths** needed to categorize your work. At a minimum, add one area path for each team you define.
 2. Decide on the number and names of teams you want to support. For more information, see [About teams and Agile tools](about-teams-and-settings.md).
-3. Open **Project settings > Project configuration** and define the area paths to support steps 1 and 2 at the project level. Follow these steps: [Open Project Settings, Project configuration](set-area-paths.md#open-project-settings) and [Add area paths](set-area-paths.md#add-areas).
+3. Open **Project settings > Project configuration** and define the area paths to support steps 1 and 2 at the project level. Follow these steps: [Open Project Settings, Project configuration](set-area-paths.md#open-project-settings-list-project-areas)) and [Add area paths](set-area-paths.md#add-an-area-path).
 4. Define the teams needed to support step 2. For more information, see [Add a team, move from one default team to several teams](add-teams.md).
 5. Open the team configuration and assign the default and other area paths to each team. Follow these steps: [Open team settings](set-area-paths.md#list-team-iterations) and [Set team default area paths](set-area-paths.md#team-area-paths).
 6. Assign work items to the area paths you defined. Use [bulk modify](../../boards/backlogs/bulk-modify-work-items.md) to modify several work items at once.
@@ -89,7 +89,7 @@ Avoid creating an overly complex area structure. While you can use areas to part
 
 Follow these steps to configure **Iteration Paths** for your project and teams:
 
-1. Define the area paths and teams using the guidance in [Define area paths and assign to a team](set-area-paths.md#guidance).
+1. Define the area paths and teams using the guidance in [Define area paths and assign to a team](set-area-paths.md#get-started).
 2. Determine the length of the iteration you want to support. We recommend that all teams use the same sprint cadence.
 3. Decide whether you want a flat structure or a hierarchy of sprints and releases.
 4. Open **Project settings > Project configuration** and define the iteration paths to support steps 2 and 3 at the project level. Follow these steps: [Open Project Settings, Project configuration](set-iteration-paths-sprints.md#open-project-settings) and [Add iterations and set iteration dates](set-iteration-paths-sprints.md#add-iterations-and-set-iteration-dates.
diff --git a/docs/organizations/settings/about-teams-and-settings.md b/docs/organizations/settings/about-teams-and-settings.md
@@ -16,8 +16,6 @@ ms.date: 04/04/2022
 
 [!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
 
-<a id="teams"></a>
-
 Learn how you can structure and use your teams and Agile tools to support your growing organization. When your team grows beyond its intended size&mdash;typically anywhere from 6 to 9 members&mdash;you might consider moving from a one team structure to a two-team structure. You can then set up a hierarchical team structure, which provides several advantages to managers for tracking progress across teams. For the step-by-step procedure to add a team, see [Add another team](add-teams.md).
 
 [!INCLUDE [temp](../../boards/includes/note-configure-customize.md)]
@@ -84,7 +82,6 @@ For more information about each tool and the configuration settings for each too
 
 Many of these tools are built from system queries that reference the team area path. For instance, a team's default area path filters the work items that appear on a team's backlog. Work items created using an Agile tool auto-assign the areas and iterations based on team defaults.  
 
-<a id="team-defaults"></a>
 
 ## Team defaults referenced by backlogs and boards
 
@@ -199,7 +196,7 @@ Several tools also reference the team's default and selected Iteration Path or s
 
 
 > [!NOTE]  
-> 1. Agile tools filter items based on the team's selected area path(s). Teams can choose [whether to include or exclude items assigned to subarea paths](../../organizations/settings/set-area-paths.md#team-area-paths).  
+> 1. Agile tools filter items based on the team's selected area path(s). Teams can choose [whether to include or exclude items assigned to subarea paths](../../organizations/settings/set-area-paths.md#set-team-area-paths).  
 > 2. Work items whose **State** equals *Closed*, *Done*, or *Removed* (corresponding to a *Completed* category state) don't appear on portfolio and product backlogs.  
 > 3. You can add custom workflow states and assign them to one of three state categories. The [state categories](../../boards/work-items/workflow-and-state-categories.md)"> determine which work items appear on backlog and board views.   
 > 4. Boards, sprint backlogs, and taskboards only show the last node in a hierarchy, called the leaf node. For example, if you link items within a hierarchy that is four levels deep, only the items at the fourth level appear on the board, sprint backlog, and task board. For more information, see [parent-child links between items](../../boards/backlogs/resolve-backlog-reorder-issues.md).  
@@ -214,7 +211,6 @@ Also, the following articles walk you through the steps for configuring teams, a
 - [Portfolio management](../../boards/plans/portfolio-management.md)
 - [Implement Scaled Agile Framework to support epics, release trains, and multiple backlogs](../../boards/plans/scaled-agile-framework.md)
 
-<a id="team-group"> </a>
 
 ## Team groups 
 
diff --git a/docs/organizations/settings/set-area-paths.md b/docs/organizations/settings/set-area-paths.md
@@ -25,8 +25,6 @@ To understand how the system uses area paths, see [About area and iteration path
 
 ## Prerequisites
 
-<a name="permissions"></a>
-
 - If you don't have a project yet, [create one now](../projects/create-project.md).
 - Ensure you're a member of the **Project Administrators** group to add an area path under the root node or edit or delete any child node. To acquire these permissions, see [Change project-level permissions](../security/change-project-level-permissions.md).
 - Have one or more of the following permissions set to **Allow**, to add, edit, and manage area paths under a node:   
@@ -40,7 +38,6 @@ To understand how the system uses area paths, see [About area and iteration path
 
 For naming restrictions on area paths, see [About areas and iterations, Naming restrictions](about-areas-iterations.md#naming-restrictions).
 
-<a id="guidance"></a>
 
 ## Get started
 
@@ -52,15 +49,14 @@ If you're new to managing projects and teams, the most straight forward sequence
 
 1. Determine the number and names of area paths that you want to support to categorize your work. At a minimum, add one area path for each team you define. For more information, review [About areas and iterations](about-areas-iterations.md).
 2. Determine the number and names of teams you want to support. For more information, review [About teams and Agile tools](about-teams-and-settings.md).
-3. Open **Project settings>Project configuration** and define the area paths to support steps 1 and 2 at the project level. Follow the steps provided later in this article: [Open Project Settings, Project configuration](#open-project-settings) and [Add area paths](#add-areas).
+3. Open **Project settings>Project configuration** and define the area paths to support steps 1 and 2 at the project level. Follow the steps provided later in this article: [Open Project Settings, Project configuration](#open-project-settings-list-project-areas) and [Add area paths](#add-an-area-path).
 4. Define the teams you need to support step 2. For more information, see [Add a team, move from one default team to several teams](add-teams.md).  
 5. Open the team configuration and assign the default and additional area path(s) to each team. Follow the steps provided later in this article: [Open team settings](#list-team-iterations) and [Set team default area path(s)](#team-area-paths).
 6. Assign the area path of work items to an area path you defined. Use [bulk modify](../../boards/backlogs/bulk-modify-work-items.md) to modify several work items at once.
 
 > [!NOTE]
 > While you can assign the same area path to more than one team, doing so can cause problems if two teams claim ownership over the same set of work items. For more information, see [About boards and Kanban, Limitations of multi-team board views](../../boards/boards/kanban-overview.md).
 
-
 As needed, you can do the following actions at any time:
 
 - Add additional child nodes
@@ -70,15 +66,10 @@ As needed, you can do the following actions at any time:
 - Rename a team
 - Change the area path assignments made to a team
 
-<a id="open-project-settings"></a>
-<a id="open-admin-context"></a>
-<a id="admin-intro-team-services"></a>
-
+## List project areas
 
 [!INCLUDE [temp](../../includes/version-selector.md)]
 
-## Open Project Settings, list project areas
-
 ::: moniker range=">= azure-devops-2019"
 
 Define both areas and iterations for a project from the **Project Settings** > **Boards** > **Project configuration**.
@@ -98,19 +89,12 @@ Define both areas and iterations for a project from the **Project Settings** > *
 
 ::: moniker-end
 
-
-<a id="admin-intro-team-services"></a> 
-
-   
-
-
 #### [Azure DevOps CLI](#tab/azure-devops-cli)
 
 ::: moniker range="azure-devops"
 
-[List project area paths](#list-areas) | [Add a project area path](#add-area) | [List team areas paths](#list-team-area-paths) | [Set team area paths](#set-team-area-paths) | [Rename or move a project area path](#rename-move-project-area-path) | [Remove area path from a team](#remove-area-path-from-team)
+[List project area paths](#list-project-areas) | [Add a project area path](#add-an-area-path) | [List team areas paths](#list-team-area-paths) | [Set team area paths](#set-team-area-paths) | [Rename or move a project area path](#rename-move-project-area-path) | [Remove area path from a team](#remove-an-area-path-from-a-team)
 
-<a id="list-areas"></a> 
 
 You can list the area paths defined for a project using [az boards area project list](/cli/azure/boards/area/project#az-boards-area-project-list). To get started, see [Get started with Azure DevOps CLI](../../cli/index.md).  
 
@@ -153,11 +137,7 @@ ID     Identifier                            Name                Path
 
 [!INCLUDE [temp](../../includes/note-cli-not-supported.md)]
 
-* * *
-
-<a id="add-areas"></a>
-<a id="add-areas-team-services"></a>
-<a id="tfs-15-area-paths"></a>
+---
 
 ## Add an area path 
 
@@ -178,8 +158,6 @@ Only one area is defined, by default. Add area paths under the root area path fo
 
 #### [Azure DevOps CLI](#tab/azure-devops-cli)
 
-<a id="add-area"></a> 
-
 ::: moniker range="azure-devops"  
 
 You can add area paths to a project using [az boards area project create](/cli/azure/boards/area/project#az-boards-area-project-create). To get started, see [Get started with Azure DevOps CLI](../../cli/index.md). 
@@ -233,13 +211,9 @@ ID     Identifier                            Name    Path
 
 [!INCLUDE [temp](../../includes/note-cli-not-supported.md)]
 
-* * *
-
-
-
-<a id="open-team-settings"></a>
+---
 
-## Open team settings, list team area paths  
+## List team area paths  
 
 You set team defaults from team settings. If you're not a team administrator, [get added as one](add-team-administrator.md). Only team or project administrators can change team settings. 
  
@@ -260,13 +234,8 @@ You set team defaults from team settings. If you're not a team administrator, [g
 ::: moniker-end
 
 
-
-
-
 #### [Azure DevOps CLI](#tab/azure-devops-cli)
 
-<a id="list-team-area-paths"></a> 
-
 ::: moniker range="azure-devops"
 
 You can list the area paths defined for a team using [az boards area team list](/cli/azure/boards/area/team#az-boards-area-team-list). To get started, see [Get started with Azure DevOps CLI](../../cli/index.md).  
@@ -296,8 +265,7 @@ Fabrikam Fiber\Service Delivery  True                 True
 
 [!INCLUDE [temp](../../includes/note-cli-not-supported.md)]
 
-* * *
-
+---
 
 ::: moniker range=">= azure-devops-2019"  
 
@@ -324,10 +292,7 @@ You define both areas and iterations from **Project Settings > Team configuratio
 
 ::: moniker-end
 
-<a id="default-iteration">  </a>
-<a id="team-area-paths">  </a>
-
-## Set team area path(s)
+## Set team area paths
 
 All work items that are assigned to a team area path appear on the backlogs and boards for that team. You can select one or more area paths and optionally include their subarea paths. Choose to include subarea paths when you want to support rollup views of work done across several teams or areas.
 
@@ -397,8 +362,6 @@ The default area path determines the default area path assigned to work items th
 
 #### [Azure DevOps CLI](#tab/azure-devops-cli)
 
-<a id="set-team-area-paths"></a> 
-
 ::: moniker range="azure-devops"
 
 You can set the default area path for a team or add an area path, using [az boards area team add](/cli/azure/boards/area/team#az-boards-area-team-add).  To get started, see [Get started with Azure DevOps CLI](../../cli/index.md). 
@@ -435,10 +398,7 @@ Fabrikam Fiber\Voice                   True                 True
 
 [!INCLUDE [temp](../../includes/note-cli-not-supported.md)]
 
-* * *
-
-<a name="rename-delete"></a>
-<a id="rename-move-project-area-path"></a>   
+---
 
 ## Rename or move an Area Path
 
@@ -495,8 +455,6 @@ ID     Identifier                            Name           Path
 55412  b00f86a2-3d49-4ad2-af01-da2537947baa  Voice and Web  \Fabrikam Fiber\Area\Voice and Web  False
 ```
 
-<a id="remove-area-path-from-team"></a> 
-
 ### Remove an area path from a team 
 
 To remove an area path from a team, use [`az boards area team remove`](/cli/azure/boards/area/team#az-boards-area-team-remove).
@@ -527,9 +485,7 @@ az boards area team remove --path "\Fabrikam Fiber\Service Delivery\Voice" --tea
 
 [!INCLUDE [temp](../../includes/note-cli-not-supported.md)]
 
-* * *
-
-<a name="delete-area-path"></a>
+---
 
 ## Delete an Area Path
 
diff --git a/docs/organizations/settings/set-iteration-paths-sprints.md b/docs/organizations/settings/set-iteration-paths-sprints.md
@@ -40,7 +40,7 @@ Newly created projects contain a single, root area path that corresponds to the
 If you're new to managing projects and teams, complete the following steps:
 
 1. Review [Configure and customize Azure Boards](../../boards/configure-customize.md).
-1. Define the area paths and teams following the guidance provided in [Define area paths and assign to a team](set-area-paths.md#guidance).  
+1. Define the area paths and teams following the guidance provided in [Define area paths and assign to a team](set-area-paths.md#get-started).  
 1. Determine the length of the iteration you want to support. Recommended practice is to have all teams use the same sprint cadence. For guidance, review [About areas and iterations](about-areas-iterations.md).
 1. Determine if you want a flat structure or hierarchy of sprints and releases.
 1. Open **Project settings>Project configuration** and define the iteration paths to support steps 2 and 3 at the project level. Follow the steps provided later in this article: [Open Project Settings, Project configuration](#list-project-iterations) and [Add iterations and set iteration dates](#iterations). 
