Fixing broken links

Author: kainawroth

articles/azure-monitor/app/app-insights-overview.md

@@ -35,10 +35,10 @@ Application Insights provides many experiences to enhance the performance, relia
 
 ### Usage
 
-* [Users, sessions, and events](usage.md#explore-usage-demographics-and-statistics): Determine when, where, and how users interact with your web app.
-* [Funnels](usage.md#discover-how-customers-are-using-your-application-with-application-insights-funnels): Analyze conversion rates to identify where users progress or drop off in the funnel.
-* [Flows](usage.md#analyze-user-navigation-patterns-with-user-flows-in-application-insights): Visualize user paths on your site to identify high engagement areas and exit points.
-* [Cohorts](usage.md#application-insights-cohorts): Group users by shared characteristics to simplify trend identification, segmentation, and performance troubleshooting.
+* [Users, sessions, and events](usage.md#the-users-sessions-and-events-segmentation-tool): Determine when, where, and how users interact with your web app.
+* [Funnels](usage.md#discover-with-funnels-how-customers-use-your-application): Analyze conversion rates to identify where users progress or drop off in the funnel.
+* [Flows](usage.md#analyze-user-navigation-patterns-with-user-flows): Visualize user paths on your site to identify high engagement areas and exit points.
+* [Cohorts](usage.md#analyze-a-specific-set-of-users-sessions-events-or-operations-repeatedly-with-cohorts): Group users by shared characteristics to simplify trend identification, segmentation, and performance troubleshooting.
 
 ### Code analysis
 

articles/azure-monitor/app/asp-net-core.md

@@ -874,7 +874,7 @@ Our [Service Updates](https://azure.microsoft.com/updates/?service=application-i
 
 ## Next steps
 
-* [Explore user flows](./usage.md#analyze-user-navigation-patterns-with-user-flows-in-application-insights) to understand how users move through your app.
+* [Explore user flows](./usage.md#analyze-user-navigation-patterns-with-user-flows) to understand how users move through your app.
 * [Configure a snapshot collection](./snapshot-debugger.md) to see the state of source code and variables at the moment an exception is thrown.
 * [Use the API](./api-custom-events-metrics.md) to send your own events and metrics for a detailed view of your app's performance and usage.
 * Use [availability tests](./availability-overview.md) to check your app constantly from around the world.

articles/azure-monitor/app/javascript-feature-extensions.md

@@ -142,7 +142,7 @@ appInsights.loadAppInsights();
 
 If you want to set this optional setting, see [Set the authenticated user context](https://github.com/microsoft/ApplicationInsights-JS/blob/master/API-reference.md#setauthenticatedusercontext). 
 
-If you're using a HEART workbook with the Click Analytics plug-in, you don't need to set the authenticated user context to see telemetry data. For more information, see the [HEART workbook documentation](./usage-heart.md#confirm-that-data-is-flowing).
+If you're using a HEART workbook with the Click Analytics plug-in, you don't need to set the authenticated user context to see telemetry data. For more information, see the [HEART workbook documentation](./usage.md#confirm-that-data-is-flowing).
 
 ## Use the plug-in
 
@@ -552,9 +552,9 @@ See the dedicated [troubleshooting article](/troubleshoot/azure/azure-monitor/ap
 
 ## Next steps
 
-- [Confirm data is flowing](./javascript-sdk.md#confirm-data-is-flowing).
-- See the [documentation on utilizing HEART workbook](usage-heart.md) for expanded product analytics.
-- See the [GitHub repository](https://github.com/microsoft/ApplicationInsights-JS/tree/master/extensions/applicationinsights-clickanalytics-js) and [npm Package](https://www.npmjs.com/package/@microsoft/applicationinsights-clickanalytics-js) for the Click Analytics Autocollection Plug-in.
-- Use [Events Analysis in the Usage experience](usage-segmentation.md) to analyze top clicks and slice by available dimensions.
-- See [Log Analytics](../logs/log-analytics-tutorial.md#write-a-query) if you aren’t familiar with the process of writing a query. 
-- Build a [workbook](../visualize/workbooks-overview.md) or [export to Power BI](../logs/log-powerbi.md) to create custom visualizations of click data.
+* [Confirm data is flowing](./javascript-sdk.md#confirm-data-is-flowing).
+* See the [documentation on utilizing HEART workbook](usage.md#analyze-product-usage-with-heart) for expanded product analytics.
+* See the [GitHub repository](https://github.com/microsoft/ApplicationInsights-JS/tree/master/extensions/applicationinsights-clickanalytics-js) and [npm Package](https://www.npmjs.com/package/@microsoft/applicationinsights-clickanalytics-js) for the Click Analytics Autocollection Plug-in.
+* Use [Events Analysis in the Usage experience](usage.md#the-users-sessions-and-events-segmentation-tool) to analyze top clicks and slice by available dimensions.
+* See [Log Analytics](../logs/log-analytics-tutorial.md#write-a-query) if you aren’t familiar with the process of writing a query. 
+* Build a [workbook](../visualize/workbooks-overview.md) or [export to Power BI](../logs/log-powerbi.md) to create custom visualizations of click data.

articles/azure-monitor/app/overview-dashboard.md

@@ -172,9 +172,9 @@ Application Insights Logs provides a rich query language that you can use to ana
 
 ## Next steps
 
-* [Funnels](./usage.md#discover-how-customers-are-using-your-application-with-application-insights-funnels)
-* [Retention](./usage.md#retention-how-many-users-come-back)
-* [User flows](./usage.md#analyze-user-navigation-patterns-with-user-flows-in-application-insights)
+* [Funnels](./usage.md#discover-with-funnels-how-customers-use-your-application)
+* [Retention](./usage.md#user-retention-analysis-for-web-applications)
+* [User flows](./usage.md#analyze-user-navigation-patterns-with-user-flows)
 * In the tutorial, you learned how to create custom dashboards. Now look at the rest of the Application Insights documentation, which also includes a case study.
    > [!div class="nextstepaction"]
    > [Deep diagnostics](../app/devops.md)

articles/azure-monitor/app/usage.md

@@ -8,7 +8,9 @@ ms.reviewer: mmcc
 
 # Usage analysis with Application Insights
 
-Which features of your web or mobile app are most popular? Do your users achieve their goals with your app? Do they drop out at particular points, and do they return later? [Application Insights](./app-insights-overview.md) is a powerful tool for monitoring the performance and usage of your applications. It provides insights into how users interact with your app, identifies areas for improvement, and helps you understand the impact of changes. With this knowledge, you can make data-driven decisions about your next development cycles.
+Which features of your web or mobile app are most popular? Do your users achieve their goals with your app? Do they drop out at particular points, and do they return later?
+
+[Application Insights](./app-insights-overview.md) is a powerful tool for monitoring the performance and usage of your applications. It provides insights into how users interact with your app, identifies areas for improvement, and helps you understand the impact of changes. With this knowledge, you can make data-driven decisions about your next development cycles.
 
 This article covers the following areas:
 
@@ -61,11 +63,11 @@ Three of the **Usage** panes use the same tool to slice and dice telemetry from
 
 Clicking **View More Insights** displays the following information:
 
-* Application Performance: Sessions, Events, and a Performance evaluation related to users' perception of responsiveness.
+* **Application Performance:** Sessions, Events, and a Performance evaluation related to users' perception of responsiveness.
 
-* Properties: Charts containing up to six user properties such as browser version, country or region, and operating system.
+* **Properties:** Charts containing up to six user properties such as browser version, country or region, and operating system.
 
-* Meet Your Users: View timelines of user activity.
+* **Meet Your Users:** View timelines of user activity.
 
 ### Explore usage demographics and statistics
 
@@ -81,13 +83,15 @@ Find out when people use your web app, what pages they're most interested in, wh
 
 Explore different groups of users by adjusting the query options at the top of the Users pane:
 
-* **During**: Choose a time range.
-* **Show**: Choose a cohort of users to analyze.
-* **Who used**: Choose custom events, requests, and page views.
-* **Events**: Choose multiple events, requests, and page views that will show users who did at least one, not necessarily all, of the selected options.
-* **By value x-axis**: Choose how to categorize the data, either by time range or by another property, such as browser or city.
-* **Split By**: Choose a property to use to split or segment the data.
-* **Add Filters**: Limit the query to certain users, sessions, or events based on their properties, such as browser or city.
+| Option          | Description                                                                                                                               |
+|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------|
+| During          | Choose a time range.                                                                                                                      |
+| Show            | hoose a cohort of users to analyze.                                                                                                       |
+| Who used        | Choose custom events, requests, and page views.                                                                                           |
+| Events          | Choose multiple events, requests, and page views that will show users who did at least one, not necessarily all, of the selected options. |
+| By value x-axis | Choose how to categorize the data, either by time range or by another property, such as browser or city.                                  |
+| Split By        | Choose a property to use to split or segment the data.                                                                                    |
+| Add Filters     | Limit the query to certain users, sessions, or events based on their properties, such as browser or city.                                 |
 
 #### Meet your users
 
@@ -227,7 +231,7 @@ public class MyTelemetryInitializer : ITelemetryInitializer
 
 ### [.NET Core](#tab/aspnetcore)
 
-For [ASP.NET Core](asp-net-core.md#add-telemetryinitializers) applications, add a new telemetry initializer to the Dependency Injection service collection in the `Program.cs` class.
+For [ASP.NET Core](asp-net-core.md#add-telemetryinitializers) applications, add a new telemetry initializer to the Dependency Injection service collection in the `Program.cs` class:
 
 ```csharp
 using Microsoft.ApplicationInsights.Extensibility;
@@ -316,7 +320,9 @@ The User Flows tool starts from an initial custom event, exception, dependency,
 To begin answering questions with the User Flows tool, choose an initial custom event, exception, dependency, page view or request to serve as the starting point for the visualization:
 
 1. Select the link in the **What do users do after?** title or select **Edit**.
+
 1. Select a custom event, exception, dependency, page view or request from the **Initial event** dropdown list.
+
 1. Select **Create graph**.
 
 The **Step 1** column of the visualization shows what users did most frequently after the initial event. The items are ordered from top to bottom and from most to least frequent. The **Step 2** and subsequent columns show what users did next. The information creates a picture of all the ways that users moved through your site.
@@ -328,8 +334,11 @@ If some of the page views, custom events, and exceptions aren't relevant to you,
 If page views or custom events are missing that you expect to see in the visualization:
 
 * Check the **Excluded events** section on the **Edit** menu.
+
 * Use the plus buttons on **Others** nodes to include less-frequent events in the visualization.
+
 * If the page view or custom event you expect is sent infrequently by users, increase the time range of the visualization on the **Edit** menu.
+
 * Make sure the custom event, exception, dependency, page view or request you expect is set up to be collected by the Application Insights SDK in the source code of your site. Learn more about [collecting custom events](./api-custom-events-metrics.md).
 
 If you want to see more steps in the visualization, use the **Previous steps** and **Next steps** dropdown lists above the visualization.
@@ -376,7 +385,9 @@ You might define a cohort of users who have all tried a new feature in your app.
 Your team defines an engaged user as anyone who uses your app five or more times in a given month. In this section, you define a cohort of these engaged users.
 
 1. Select **Create a Cohort**.
+
 1. Select the **Template Gallery** tab to see a collection of templates for various cohorts.
+
 1. Select **Engaged Users -- by Days Used**.
 
     There are three parameters for this cohort:
@@ -470,16 +481,21 @@ To use the Impact analysis workbook, in your Application Insights resources go t
 :::image type="content" source="./media/usage-impact/selected-event.png" alt-text="Screenshot that shows where to choose an initial page view, custom event, or request." lightbox="./media/usage-impact/selected-event.png":::
 
 1. From the **Selected event** dropdown list, select an event.
+
 1. From the **analyze how its** dropdown list, select a metric.
+
 1. From the  **Impacting event** dropdown list, select an event.
+
 1. To add a filter, use the **Add selected event filters** tab or the **Add impacting event filters** tab.
 
 ### Is page load time affecting how many people convert on my page?
 
 To begin answering questions with the Impact workbook, choose an initial page view, custom event, or request.
 
 1. From the **Selected event** dropdown list, select an event.
+
 1. Leave the **analyze how its** dropdown list on the default selection of **Duration**. (In this context, **Duration** is an alias for **Page Load Time**.)
+
 1. From the **Impacting event** dropdown list, select a custom event. This event should correspond to a UI element on the page view you selected in step 1.
 
    :::image type="content" source="./media/usage-impact/impact.png" alt-text="Screenshot that shows an example with the selected event as Home Page analyzed by duration." lightbox="./media/usage-impact/impact.png":::
@@ -491,7 +507,9 @@ Impact supports both standard and custom properties and measurements. Use whatev
 ### Do users from different countries or regions convert at different rates?
 
 1. From the **Selected event** dropdown list, select an event.
+
 1. From the **analyze how its** dropdown list, select **Country or region**.
+
 1. From the **Impacting event** dropdown list, select a custom event that corresponds to a UI element on the page view you chose in step 1.
 
    :::image type="content" source="./media/usage-impact/regions.png" alt-text="Screenshot that shows an example with the selected event as GET analyzed by country and region." lightbox="./media/usage-impact/regions.png":::
@@ -503,13 +521,15 @@ Under the hood, the Impact analysis workbook relies on the [Pearson correlation
 The basic breakdown of how Impact analysis works is listed here:
 
 * Let *A* = the main page view, custom event, or request you select in the **Selected event** dropdown list.
+
 * Let *B* = the secondary page view or custom event you select in the **impacts the usage of** dropdown list.
 
 Impact looks at a sample of all the sessions from users in the selected time range. For each session, it looks for each occurrence of *A*.
 
 Sessions are then broken into two different kinds of *subsessions* based on one of two conditions:
 
 * A converted subsession consists of a session ending with a *B* event and encompasses all *A* events that occur prior to *B*.
+
 * An unconverted subsession occurs when all *A*s occur without a terminal *B*.
 
 How Impact is ultimately calculated varies based on whether we're analyzing by metric or by dimension. For metrics, all *A*s in a subsession are averaged. For dimensions, the value of each *A* contributes *1/N* to the value assigned to *B*, where *N* is the number of *A*s in the subsession.
@@ -533,16 +553,21 @@ These dimensions are measured independently, but they interact with each other.
 :::image type="content" source="media/usage-overview/heart-funnel.png" alt-text="Diagram that shows the funnel relationship between HEART dimensions. The funnel path is Adoption to Engagement to Retention to Happiness. Task Success is a driver of this funnel.":::
 
 * Adoption, engagement, and retention form a user activity funnel. Only a portion of users who adopt the tool come back to use it.
+
 * Task success is the driver that progresses users down the funnel and moves them from adoption to retention.
+
 * Happiness is an outcome of the other dimensions and not a stand-alone measurement. Users who have progressed down the funnel and are showing a higher level of activity are ideally happier.
 
 ### Get started
 
 #### Prerequisites
 
 * **Azure subscription**: [Create an Azure subscription for free](https://azure.microsoft.com/free/)
+
 * **Application Insights resource**: [Create an Application Insights resource](create-workspace-resource.md#create-a-workspace-based-resource)
+
 * **Click Analytics**: Set up the [Click Analytics Autocollection plug-in](javascript-feature-extensions.md).
+
 * **Specific attributes**: Instrument the following attributes to calculate HEART metrics.
 
     | Source         | Attribute            | Description                                |
@@ -608,11 +633,17 @@ The workbook shows metric trends for the HEART dimensions split over seven tabs.
 The tabs are:
 
 * **Summary**: Summarizes usage funnel metrics for a high-level view of visits, interactions, and repeat usage.
+
 * **Adoption**: Helps you understand the penetration among the target audience, acquisition velocity, and total user base.
+
 * **Engagement**: Shows frequency, depth, and breadth of usage.
+
 * **Retention**: Shows repeat usage.
+
 * **Task success**: Enables understanding of user flows and their time distributions.
+
 * **Happiness**: We recommend using a survey tool to measure customer satisfaction score (CSAT) over a five-point scale. On this tab, we've provided the likelihood of happiness via usage and performance metrics.
+
 * **Feature metrics**: Enables understanding of HEART metrics at feature granularity.
 
 > [!WARNING]

articles/azure-monitor/includes/azure-monitor-app-insights-opentelemetry-faqs.md

@@ -91,7 +91,7 @@ The following chart breaks out OpenTelemetry feature support for each language.
 | [Offline storage and automatic retries](../app/opentelemetry-configuration.md#offline-storage-and-automatic-retries)  | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |
 | [Exception reporting](../app/asp-net-exceptions.md)                                                                   | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |
 | [Logs collection](../app/asp-net-trace-logs.md)                                                                       | :white_check_mark: | :warning:          | :white_check_mark: | :white_check_mark: |
-| [Custom Events](../app/usage-overview.md#custom-business-events)                                                      | :warning:          | :warning:          | :warning:          | :white_check_mark: |
+| [Custom Events](../app/usage.md#track-user-interactions-with-custom-events)                                                      | :warning:          | :warning:          | :warning:          | :white_check_mark: |
 | [Microsoft Entra authentication](../app/azure-ad-authentication.md)                                                   | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |
 | [Live metrics](../app/live-stream.md)                                                                                 | :white_check_mark: | :white_check_mark: | :white_check_mark: | :white_check_mark: |
 | [Live Metrics Filtering](../app/live-stream.md#select-and-filter-your-metrics)                                        | :x:                | :x:                | :x:                | :x:                |