fix broken links

Author: craigshoemaker

articles/container-apps/session-pool.md

@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: conceptual
-ms.date: 02/14/2025
+ms.date: 02/19/2025
 ms.author: cshoe
 ---
 
@@ -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-usage.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#identifiers)
 
 The following endpoints are available for managing sessions in a pool:
 
@@ -294,7 +294,7 @@ az containerapp sessionpool show \
 
 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-usage.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#identifiers).
 
 ## Image caching
 

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

@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: how-to
-ms.date: 02/14/2025
+ms.date: 02/19/2025
 ms.author: cshoe
 ms.custom: references_regions
 ms.collection: ce-skilling-ai-copilot
@@ -54,9 +54,9 @@ 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-usage.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#identifiers).
 
-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.
+When you interact with sessions in a pool, you use a [session identifier](sessions-usage.md#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.
 

articles/container-apps/sessions-custom-container.md

@@ -7,7 +7,7 @@ ms.service: azure-container-apps
 ms.custom:
   - ignite-2024
 ms.topic: conceptual
-ms.date: 02/14/2025
+ms.date: 02/19/2025
 ms.author: cshoe
 ms.collection: ce-skilling-ai-copilot
 ---

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

@@ -5,7 +5,7 @@ services: container-apps
 author: IshitaAsthana
 ms.service: azure-container-apps
 ms.topic: tutorial
-ms.date: 11/08/2024
+ms.date: 02/19/2025
 ms.author: iasthana
 ---
 

articles/container-apps/sessions-usage.md

@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: conceptual
-ms.date: 02/14/2025
+ms.date: 02/19/2025
 ms.author: cshoe
 ms.custom: references_regions, ignite-2024
 ---
@@ -26,7 +26,7 @@ A pool management endpoint follows this format:
 https://<SESSION_POOL_NAME>.<ENVIRONMENT_ID>.<REGION>.azurecontainerapps.io
 ```
 
-For more information managing session pools, see [session pools management endpoint](./session-pools.md#management-endpoint)
+For more information managing session pools, see [session pools management endpoint](./session-pool.md#management-endpoint)
 
 ## Forwarding requests to a session's container
 

articles/container-apps/sessions.md

@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: conceptual
-ms.date: 02/14/2025
+ms.date: 02/19/2025
 ms.author: cshoe
 ms.custom: references_regions, ignite-2024
 ---
@@ -65,7 +65,7 @@ The following states define this lifecycle:
 
 1. **Unallocated**: Once a session is done starting up, it's added to the pool and becomes available for allocation. For custom container sessions, you can specify how many ready sessions to maintain in the pool. This number should be increased if sessions are allocated faster than they're replenished.
 
-1. **Allocated**: When you send a request to a nonrunning session, the pool provides a new session and places it in an allocated state. Subsequent requests with the same session identifier are routed to the same session, allowing for efficient reuse without cold starts. Each allocated session is associated with a [session identifier](./sessions-usage.md#session-identifiers).
+1. **Allocated**: When you send a request to a nonrunning session, the pool provides a new session and places it in an allocated state. Subsequent requests with the same session identifier are routed to the same session, allowing for efficient reuse without cold starts. Each allocated session is associated with a [session identifier](./sessions-usage.md#identifiers).
 
 1. **Destroyed**: If a session doesn't receive requests for a duration defined by the `cooldownPeriodInSeconds` setting, the session and its Hyper-V sandbox are securely deleted. This automatic cleanup setup enhances resource management and security.