review

Author: gitName

articles/api-management/how-to-create-workspace.md

@@ -59,7 +59,8 @@ Follow the steps in this article to:
 
 1. Select **Next**. After validation completes, select **Create**.
 
-It can take from several minutes to up to several hours to create the workspace, a new workspace gateway (if selected), and related resources. To track the deployment progress in the Azure portal, go to the gateway's resource group. In the left menu, under **Settings**, select **Deployments**.
+    > [!NOTE]
+    > Creation of a new workspace gateway, if selected, can take up to several hours to complete. To track the deployment progress in the Azure portal, go to the gateway's resource group. In the left menu, under **Settings**, select **Deployments**.
 
 After the deployment completes, the new workspace appears in the list on the **Workspaces** page. Select the workspace to manage its settings and resources.
 

articles/api-management/workspaces-overview.md

@@ -72,7 +72,7 @@ Workspace gateways are managed independently from the API Management service and
 
 ### Associate workspaces with a workspace gateway
 
- Depending on your organization's needs, you can associate one workspace or up to several workspaces with a workspace gateway. 
+ Depending on your organization's needs, you can associate one workspace or multiple workspaces with a workspace gateway. 
 
 > [!NOTE]
 > Associating multiple workspaces with a workspace gateway is available only for workspace gateways created after March 1, 2025. 
@@ -85,7 +85,7 @@ Consider reliability, security, and cost when choosing a deployment model for wo
 
 * **Use dedicated gateways for mission-critical workloads** - To maximize API reliability and security, assign each mission-critical workspace to its own gateway, avoiding shared use with other workspaces.
 * **Balance reliability, security, and cost** - Associate multiple workspaces with a gateway to balance reliability, security, and cost for non-critical workloads. Distributing workspaces across at least two gateways helps prevent issues, such as resource exhaustion or configuration errors, from impacting all APIs within the organization.
-* **Use distinct gateways for different use cases** - Group workspaces on a gateway based on a use case or network requirements. For instance, separate internal and external APIs by assigning them to different gateways.
+* **Use distinct gateways for different use cases** - Group workspaces on a gateway based on a use case or network requirements. For instance, you can distinguish between internal and external APIS by assigning them to separate gateways, each with its own network configuration.
 **Prepare to quarantine troubled workspaces** - Use a proxy, such as Azure Application Gateway or Azure Front Door, in front of shared workspace gateways to simplify moving a workspace that's causing resource exhaustion to a different gateway, preventing impact on other workspaces sharing the gateway.
 
 > [!NOTE]