review

Author: gitName

articles/api-management/api-management-key-concepts.md

@@ -105,9 +105,7 @@ Using the developer portal, API consumers can:
 
 ## Federated API management with workspaces
 
-Azure API Management supports several deployment models for managing an organization's API portfolio - for example, use a centralized instance managed entirely by an API platform team, or deploy separate instances managed independently by API teams. The models offer different degrees of centralized control over the API platform infrastructure, API governance, and API discovery. 
-
-For organizations that want to empower decentralized teams to develop and manage their own APIs with the advantages of centralized API governance and discovery, API Management offers first-class support for a federated model with *workspaces*.
+For organizations that want to empower decentralized teams to develop and manage their own APIs with the advantages of centralized API governance and discovery, API Management offers first-class support for a federated API management model with *workspaces*.
 
 [!INCLUDE [workspaces-benefits](../../includes/workspaces-benefits.md)]
 

articles/api-management/workspaces-overview.md

@@ -36,7 +36,7 @@ Federated API management provides:
 In Azure API Management, use *workspaces* to implement federated API management. Workspaces function like "folders" within an API Management service:
 
 * Each workspace contains APIs, products, subscriptions, named values, and related resources. See the API Management [REST API reference](/rest/api/apimanagement/workspace?view=rest-apimanagement-2023-09-01-preview&preserve-view=true) for a full list of resources and operations supported in workspaces.
-* Teams' access to resources within a workspace is managed through Azure's role-based access control (RBAC) with built-in or custom roles assignable to Microsoft Entra accounts. 
+* Teams' access to resources within a workspace is managed through Azure's role-based access control (RBAC) with built-in or custom roles assignable to Microsoft Entra accounts and scoped to a workspace. 
 * Each workspace is associated with one or more [workspace gateways](#workspace-gateway) for routing API traffic to the backend services of APIs in the workspace.
 * The platform team can apply API policies spanning APIs in workspaces, monitor the platform by viewing the logs for all workspaces, and implement a centralized API discovery experience with a developer portal.