add screenshot

Author: gitName

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

@@ -41,17 +41,22 @@ Follow the steps in this article to:
 
 1. On the **Basics** tab, enter a descriptive **Display name**, resource **Name**, and optional **Description** for the workspace. Select **Next**.
 
-1. On the **Gateway** tab, configure settings for the workspace gateway:
+1. On the **Gateway** tab, configure settings for the workspace gateway.
 
-    * In **Gateway details**, select an existing gateway, or enter a new gateway name and select the number of scale **Units**. The gateway costs are based on the number of units. For more information, see [API Management pricing](https://aka.ms/apimpricing).
+    :::image type="content" source="media/how-to-create-workspace/create-workspace-gateway.png" alt-text="Screenshot of creating a workspace gateway in the portal.":::
 
-    * In **Network**, select a **Network configuration** for your workspace gateway. 
+    * Select **Create new** to create a new workspace gateway, or select **Use existing** to share an existing workspace gateway.
 
-        > [!IMPORTANT]
-        > Plan your workspace's network configuration carefully. You can't change the network configuration after you create the workspace.
-
-    * If you select a network configuration that includes private inbound or private outbound network access, select a **Virtual network** and **Subnet** to isolate the workspace gateway, or create a new one. For network requirements, see [Network resource requirements for workspace gateways](virtual-network-workspaces-resources.md).
+    * If you choose to create a new gateway:
+        * In **Gateway details**, enter a new gateway name and select the number of scale **Units**. The gateway costs are based on the number of units. For more information, see [API Management pricing](https://aka.ms/apimpricing).
 
+        * In **Network**, select a **Network configuration** for your workspace gateway. 
+    
+          > [!IMPORTANT]
+          > Plan your workspace's network configuration carefully. You can't change the network configuration after you create the workspace.
+    
+        * If you select a network configuration that includes private inbound or private outbound network access, select a **Virtual network** and **Subnet** to isolate the workspace gateway, or create a new one. For network requirements, see [Network resource requirements for workspace gateways](virtual-network-workspaces-resources.md).
+    
 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**.

articles/api-management/media/how-to-create-workspace/create-workspace-gateway.png

@@ -22,7 +22,7 @@ Workspaces function like "folders" within an API Management service:
 
 * Each workspace contains APIs, products, subscriptions, named values, and related resources. 
 * 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. 
-* Each workspace is associated with a *workspace gateway* for routing API traffic to the backend services of APIs in the workspace.
+* Each workspace is associated with one or more *workspace gateways* for routing API traffic to the backend services of APIs in the workspace.
 
 :::image type="content" source="media/workspaces-overview/workspace-concept.png" alt-text="Conceptual diagram of API Management service with workspaces.":::
 
@@ -60,7 +60,7 @@ While workspaces are managed independently from the API Management service and o
 
 ## Workspace gateway
 
-Each workspace can be associated with workspace gateways to enable runtime of APIs managed within the workspace. A workspace gateway is a standalone Azure resource with the same core functionality as the gateway built into your API Management service. Workspace gateways are managed independently from the API Management service and from each other.  
+Each workspace is associated with one or more workspace gateways to enable runtime of APIs managed within the workspace. A workspace gateway is a standalone Azure resource with the same core functionality as the gateway built into your API Management service. Workspace gateways are managed independently from the API Management service and from each other.  
 
 * For information on the cost of workspace gateways, see [API Management pricing](https://aka.ms/apimpricing).
 * For a detailed comparison of API Management gateways, see [API Management gateways overview](api-management-gateways-overview.md).
@@ -74,7 +74,7 @@ A workspace gateway can be either *dedicated* to a single workspace or *shared*
 
 * **Dedicated** - Provides isolation of runtime between workspaces, increasing API reliability, resiliency, and security and enabling attribution of runtime issues to a workspace.
 
-* **Shared** - Gateway settings including scale, hostname, networking, and TLS configuration, and computing resources such as CPU and memory, are shared by multiple workspaces on a gateway.
+* **Shared** - Shares gateway settings including scale, hostname, networking, and TLS configuration, and computing resources such as CPU and memory by multiple workspaces.
 
 <!--- Can a workspace be associated with both a dedicated g/w and a shared g/w?-->
 
@@ -87,7 +87,7 @@ Consider reliability, security, and cost when choosing a deployment model for wo
 
 ### Gateway hostname
 
-Each workspace gateway provides a unique hostname for APIs managed in that workspace. Default hostnames follow the pattern `<gateway-name>-<hash>.gateway.<region>.azure-api.net`. Currently, custom hostnames aren't supported for workspace gateways.
+Each workspace gateway provides a unique hostname for APIs managed in an associated workspace. Default hostnames follow the pattern `<gateway-name>-<hash>.gateway.<region>.azure-api.net`. Currently, custom hostnames aren't supported for workspace gateways.
 
 
 ### Network isolation
@@ -110,7 +110,7 @@ For a current list of regions where workspace gateways are available, see [Avail
 The following constraints currently apply to workspace gateways:
 
 * A workspace gateway needs to be in the same region as the API Management instance's primary Azure region and in the same subscription
-* To associate a shared gateway, a workspace must be in the same API Management instance
+* All workspaces that share a workspace gateway must be in the same API Management instance
 * A shared gateway can be associated with up to 30 workspaces (contact support to increase this limit)
 * A workspace can't be associated with a self-hosted gateway
 * Workspace gateways don't support inbound private endpoints