Update auth

Author: anthonychu

articles/container-apps/sessions.md

@@ -60,7 +60,7 @@ You can configure pools to set the maximum number of sessions that can be alloca
 
 A session is a sandboxed environment that runs your code or application. Each session is isolated from other sessions and from the host environment with a [Hyper-V](/windows-server/virtualization/hyper-v/hyper-v-technology-overview) sandbox. Optionally, you can enable network isolation to further enhance security.
 
-You interact with sessions in a session pool using an HTTP API. Each session pool has a unique pool management endpoint.
+You interact with sessions in a session pool by sending HTTP requests. Each session pool has a unique pool management endpoint.
 
 For code interpreter sessions, you can also use an integration with an [LLM framework](./sessions-code-interpreter.md#llm-framework-integrations).
 
@@ -97,7 +97,7 @@ Example strategies include:
 
 ### Authentication
 
-Authentication is handled using Microsoft Entra (formerly Azure Active Directory) tokens. Valid Microsoft Entra tokens are generated by an identity belonging to the *Azure ContainerApps Session Executor* and *Contributor* roles on the session pool.
+When you send HTTP requests to a session, authentication is handled using Microsoft Entra (formerly Azure Active Directory) tokens. Valid Microsoft Entra tokens are generated by an identity belonging to the *Azure ContainerApps Session Executor* role on the session pool.
 
 To assign the roles to an identity, use the following Azure CLI commands: