Apply suggestions from code review

Co-authored-by: Craig Shoemaker <[email protected]>

Author: anthonychu

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

@@ -216,7 +216,7 @@ This template creates a session pool with the following settings:
 
 #### Image caching
 
-When a session pool is created or updated, Azure Container Apps caches the container image in the pool. This caching helps to speed up the process of creating new sessions.
+When a session pool is created or updated, Azure Container Apps caches the container image in the pool. This caching helps speed up the process of creating new sessions.
 
 Because the image is cached, any changes to the image aren't automatically reflected in the sessions. To update the image in the sessions, you must update the session pool with a new image tag. Use a unique tag for each image update to ensure that the new image is pulled.
 
@@ -285,7 +285,7 @@ There are two ways to use managed identities with custom container session pools
 * **Resource access**: Use the session pool's managed identity in a session to access other Microsoft Entra protected resources. Due to its security implications, this capability is disabled by default.
 
     > [!IMPORTANT]
-    > If you enable access to managed identity in a session, any code or programs running in the session can create Entra tokens for the pool's managed identity. Because sessions typically run untrusted code, it's recommended to use this feature with caution.
+    > If you enable access to managed identity in a session, any code or programs running in the session can create Entra tokens for the pool's managed identity. Since sessions typically run untrusted code, use this feature with caution.
 
 # [Azure CLI](#tab/azure-cli)
 

articles/container-apps/sessions.md

@@ -83,7 +83,7 @@ The identifier must be a string that is 4 to 128 characters long and can contain
 
 #### Protecting session identifiers
 
-The session identifier is sensitive information which must be managed securely. Your application must ensure each user or tenant only has access to their own sessions.
+The session identifier is sensitive information which you must manage securely. Your application needs to ensure each user or tenant only has access to their own sessions.
 
 The specific strategies that prevent misuse of session identifiers differ depending on the design and architecture of your app. However, your app must always have complete control over the creation and use of session identifiers so that a malicious user can't access another user's session.