fix broken links

Author: craigshoemaker

articles/container-apps/session-pool.md

@@ -1,6 +1,6 @@
 ---
 title: Use session pools in Azure Container Apps
-description: Learn to run a container in a custom session in Azure Container Apps.
+description: Learn to use and manage session pools in Azure Container Apps.
 services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
@@ -267,7 +267,7 @@ This template creates a session pool with the following settings:
 > [!IMPORTANT]
 > The session identifier is sensitive information which requires a secure process as you create and manage its value. To protect this value, your application must ensure each user or tenant only has access to their own sessions.
 >
-> Failure to secure access to sessions could result in misuse or unauthorized access to data stored in your users' sessions. For more information, see [Session identifiers](sessions.md#session-identifiers)
+> Failure to secure access to sessions could result in misuse or unauthorized access to data stored in your users' sessions. For more information, see [Session identifiers](./sessions-usage.md#session-identifiers)
 
 The following endpoints are available for managing sessions in a pool:
 
@@ -292,9 +292,9 @@ az containerapp sessionpool show \
     --output tsv
 ```
 
-All requests to the pool management endpoint must include an `Authorization` header with a bearer token. To learn how to authenticate with the pool management API, see [Authentication](sessions.md#authentication).
+All requests to the pool management endpoint must include an `Authorization` header with a bearer token. To learn how to authenticate with the pool management API, see [Authentication](sessions-usage.md#authentication).
 
-Each API request must also include the query string parameter `identifier` with the session ID. This unique session ID enables your application to interact with specific sessions. To learn more about session identifiers, see [Session identifiers](sessions.md#session-identifiers).
+Each API request must also include the query string parameter `identifier` with the session ID. This unique session ID enables your application to interact with specific sessions. To learn more about session identifiers, see [Session identifiers](sessions-usage.md#session-identifiers).
 
 ## Image caching
 

articles/container-apps/sessions-code-interpreter.md

@@ -43,7 +43,7 @@ In the session pool, you can specify settings such as the maximum number of conc
 
 You can create a session pool using the Azure portal, Azure CLI, or Azure Resource Manager templates. After you create a session pool, you can use the pool's management API endpoints to manage and execute code inside a session.
 
-For more information about how to create and configure a session pool, see [Use session pools](./sessio-pool.md).
+For more information about how to create and configure a session pool, see [Use session pools](./session-pool.md).
 
 ## Code execution in a session
 
@@ -54,14 +54,12 @@ After you create a session pool, your application can interact with sessions in
 > [!IMPORTANT]
 > The session identifier is sensitive information which requires you to use a secure process to manage its value. Part of this process requires that your application ensures each user or tenant only has access to their own sessions.
 >
-> Failure to secure access to sessions could result in misuse or unauthorized access to data stored in your users' sessions. For more information, see [Session identifiers](sessions.md#session-identifiers)
+> Failure to secure access to sessions could result in misuse or unauthorized access to data stored in your users' sessions. For more information, see [Session identifiers](sessions-usage.md#session-identifiers).
 
-When you interact with sessions in a pool, you use a session identifier to reference each session A session identifier is a string that you define that is unique within the session pool. If you're building a web application, you can use the user's ID. If you're building a chatbot, you can use the conversation ID.
+When you interact with sessions in a pool, you use a [session identifier](sessions-usage.md#session-identifiers) to reference each session A session identifier is a string that you define that is unique within the session pool. If you're building a web application, you can use the user's ID. If you're building a chatbot, you can use the conversation ID.
 
 If there's a running session with the identifier, the session is reused. If there's no running session with the identifier, a new session is automatically created.
 
-To learn more about session identifiers, see [Sessions overview](./sessions.md#session-identifiers).
-
 ## Authentication
 
 Authentication is handled using Microsoft Entra tokens. Valid Microsoft Entra tokens are generated by an identity belonging to the *Azure ContainerApps Session Executor* and *Contributor* roles on the session pool.

articles/container-apps/sessions-tutorial-nodejs.md

@@ -131,7 +131,7 @@ To interact with the session pool's API, you must use an identity with the `Azur
 
 ## Get a bearer token
 
-For direct access to the session pool’s API, generate an access token to include in the `Authorization` header of your requests. Ensure the token contains an audience (`aud`) claim with the value `https://dynamicsessions.io`. For more information, see [authentication and authorization](./sessions.md?tabs=azure-cli#authentication) rules.
+For direct access to the session pool’s API, generate an access token to include in the `Authorization` header of your requests. Ensure the token contains an audience (`aud`) claim with the value `https://dynamicsessions.io`. For more information, see [authentication and authorization](./sessions-usage.md?tabs=azure-cli#authentication) rules.
 
 1. Get an access token.
 

articles/container-apps/sessions-usage.md

@@ -1,6 +1,6 @@
 ---
 title: Use dynamic sessions in Azure Container Apps
-description: Learn how when to use dynamic sessions in Azure Container Apps.
+description: Learn how to use dynamic sessions in Azure Container Apps.
 services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
@@ -192,7 +192,7 @@ If you're using an [large language model (LLM) framework integration](sessions-c
 
 If you're using the pool's management API endpoints directly, you must generate a token and include it in the `Authorization` header of your HTTP requests. In addition to the role assignments previously mentioned, token needs to contain an audience (`aud`) claim with the value `https://dynamicsessions.io`.
 
-##### [Azure CLI](#tab/azure-cli)
+##### [Azure CLI](#tab/cli)
 
 To generate a token using the Azure CLI, run the following command:
 

articles/container-apps/sessions.md

@@ -1,6 +1,6 @@
 ---
 title: Dynamic sessions in Azure Container Apps
-description: Learn how when to use dynamic sessions in Azure Container Apps.
+description: Learn about dynamic sessions in Azure Container Apps.
 services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
@@ -53,7 +53,7 @@ Azure Container Apps supports two types of sessions:
 
 To provide subsecond session allocation times, Azure Container Apps maintains a pool of ready but unallocated sessions. When your application makes a request for a session that hasn't been used before, the pool automatically assigns a new session for you. As sessions are allocated, the pool is automatically replenished to maintain a constant number of ready sessions.
 
-Each session pool is available to your app through a unique [pool management endpoint location](#working-with-sessions).
+Each session pool is available to your app through a [unique pool management endpoint location](sessions-usage.md).
 
 ## Session lifecycle