update limitations and sdk versions, remove supported regions section

Author: jcocchi

articles/cosmos-db/dedicated-gateway.md

@@ -60,7 +60,7 @@ Dedicated gateway nodes are independent from one another. When you provision mul
 
 For development, we recommend starting with one node but for production, you should provision three or more nodes for high availability. [Learn how to provision a dedicated gateway cluster with an integrated cache](how-to-configure-integrated-cache.md). Provisioning multiple dedicated gateway nodes allows the dedicated gateway cluster to continue to route requests and serve cached data, even when one of the dedicated gateway nodes is unavailable.
 
-The dedicated gateway is available in the following sizes. The integrated cache uses approximately 70% of the memory and the rest is reserved for routing requests to backend partitions.
+The dedicated gateway is available in the following sizes. The integrated cache uses approximately 50% of the memory and the rest is reserved for metadata and routing requests to backend partitions.
 
 | **Sku Name** | **vCPU** | **Memory**  |
 | ------------ | -------- | ----------- |
@@ -90,32 +90,9 @@ Like nodes within a cluster, dedicated gateway nodes across regions are independ
 The dedicated gateway has the following limitations:
 
 - Dedicated gateways are only supported on SQL API accounts
+- You can't provision a dedicated gateway in Azure Cosmos DB accounts with [availability zones](../availability-zones/az-region.md).
 - You can't use [role-based access control (RBAC)](how-to-setup-rbac.md) to authenticate data plane requests routed through the dedicated gateway
 
-## Supported regions
-
-The dedicated gateway isn't supported in every Azure region yet.
-
-Current list of supported Azure regions:
-
-| **Americas** | **Europe and Africa**  | **Asia Pacific**  |
-| ------------ | -------- | ----------- | 
-| Brazil South      | France Central    | Australia Central |
-| Canada Central  | France South    | Australia Central 2 |
-| Canada East     | Germany North   | Australia East |
-| Central US | Germany West Central | Australia Southeast |
-| Central US EUAP | North Europe | Central India |
-| East US | Norway East | East Asia |
-| East US 2 | Norway West | Japan West |
-| East US 2 EUAP | South Africa North | Japan East |
-| North Central US | Switzerland North | Korea Central |
-| South Central US | Switzerland West | Korea South |
-| West Central US | UAE Central | Southeast Asia |
-| West US | UAE North | West India |
-| West US 2 | UK South |  |
-|   | UK West | |
-|      | West Europe |  |
-
 
 ## Next steps
 

articles/cosmos-db/how-to-configure-integrated-cache.md

@@ -30,7 +30,7 @@ This article describes how to provision a dedicated gateway, configure the integ
 2. Fill out the **Dedicated gateway** form with the following details:
 
    * **Dedicated Gateway** - Turn on the  toggle to **Provisioned**. 
-   * **SKU** - Select a SKU with the required compute and memory size. The integrated cache will use approximately 70% of the memory, and the remaining 30% of memory is used for routing requests to the backend partitions.
+   * **SKU** - Select a SKU with the required compute and memory size. The integrated cache will use approximately 50% of the memory, and the remaining memory is used for metadata and routing requests to the backend partitions.
    *  **Number of instances** - Number of nodes. For development purpose, we recommend starting with one node of the D4 size. Based on the amount of data you need to cache and to achieve high availability, you can increase the node size after initial testing.
 
    :::image type="content" source="./media/how-to-configure-integrated-cache/dedicated-gateway-input.png" alt-text="An image that shows sample input settings for creating a dedicated gateway cluster" lightbox="./media/how-to-configure-integrated-cache/dedicated-gateway-input.png" border="false":::
@@ -74,9 +74,9 @@ Adjusting the `MaxIntegratedCacheStaleness` is supported in these versions of ea
 | SDK | Supported versions | Comment |
 | --- | ------------------ | ------- |
 | **.NET SDK v3** | *>= 3.19.0-preview* | Currently supported in the preview SDK versions only. |
-| **Java SDK v4** | *>= 4.16.0-beta*    | Currently supported in the preview SDK versions only. |
-| **Node.js SDK** | *>=3.16.0*          | - |
-| **Python SDK**  | *>=4.3.0b3*         | - |
+| **Java SDK v4** | *>= 4.34.0* | - |
+| **Node.js SDK** | *>=3.16.0* | - |
+| **Python SDK**  | *>=4.3.1* | - |
 
 ### [.NET](#tab/dotnet)