fixing standard setup wording

Author: fosteramanda

articles/ai-services/agents/concepts/standard-agent-setup.md

@@ -32,23 +32,12 @@ By bundling these BYO features (file storage, search, and thread storage), the s
 Your existing Azure Cosmos DB for NoSQL Account used in standard setup must have a total throughput limit of at least **3000 RU/s**. Both **Provisioned Throughput** and **Serverless** modes are supported.
 
 When you use standard setup, **three containers** will be provisioned in your existing Cosmos DB account, and **each container requires 1000 RU/s**.
-
 * thread-message-store: End-user conversations
 * system-thread-message-store: Internal system messages
-* agent-entity-store: Model inputs and outputs
+* agent-entity-store: Agent metadata including their instructions, tools, name, etc.
 
 ## Project-Level Data Isolation
-
-Azure AI Foundry enforces project-level data isolation by default. When you configure your own resources in the project capability host: 
-* **Azure Storage**: Two Blob containers are automatically provisioned: 
-    * One for uploaded files 
-    * One for intermediate system data (for example, chunks, embeddings) 
-* **Azure Cosmos DB**: Three containers are provisioned under a dedicated enterprise_memory database: 
-    * thread-message-store: End-user conversations 
-    * system-thread-message-store: Internal system messages 
-    * agent-entity-store: Model inputs and outputs 
-
-This default behavior was chosen to reduce configuration complexity while still enforcing strict data boundaries—ensuring each project has a clean, isolated storage footprint without requiring manual setup. 
+Standard setup enforces project-level data isolation by default. Two blob storage containers will automatically be provisioned in your storage account, one for files and one for intermediate system data (chunks, embeddings) and three containers will be provisioned in your Cosmos DB, one for user systems, one for system messages, and one for user inputs related to created agents such as their instructions, tools, name, etc. This default behavior was chosen to reduce setup complexity while still enforcing strict data boundaries between projects.
 
 ## Capability hosts
 **Capability hosts** are sub-resources on both the Account and Project, enabling interaction with the Azure AI Foundry Agent Service. 

articles/ai-services/agents/environment-setup.md

@@ -18,14 +18,14 @@ Creating your first agent with Azure AI Foundry Agent Service is a two-step proc
 1. Set up your agent environment.
 1. Create and configure your agent using either the SDK of your choice or the Azure Foundry Portal. 
 
-Use this article to learn more about setting up your agents.
+Use this article to learn more about setting up your agent environment.
 
 ### Required permissions 
 
 | Action                                                                 | Required Role                   |
 |------------------------------------------------------------------------|----------------------------------|
 | Create an account and project                                          | Azure AI Account Owner           |
-| **Standard Setup Only:** Assign RBAC for required resources (Cosmos DB, Search, Storage, etc.) | Role Based Access Administrator  |
+| **Standard Setup Only:** Assign RBAC for required resources (Cosmos DB, Search, Storage, etc.) | Role Based Access Control Administrator  |
 | Create and edit agents                                                 | Azure AI User                    |
 
 ## Set up your agent environment
@@ -37,7 +37,7 @@ Agents are scoped at the project level, which ensures data isolation—agents wi
 * An Azure subscription - [Create one for free](https://azure.microsoft.com/free/cognitive-services).
 * Ensure that the individual creating the account and project has the **Azure AI Account Owner** role at the subscription scope
 * If configuring **Standard Setup**, the same individual must also have permissions to assign roles to required resources (Cosmos DB, Search, Storage).
-    * The built-in role needed is **Role Based Access Administrator**.
+    * The built-in role needed is **Role Based Access Control Administrator**.
     * Alternatively, having the **Owner** role at the subscription level also satisfies this requirement.
     * The key permission needed is: `Microsoft.Authorization/roleAssignments/write`