Merge pull request #286324 from yash177-maker1/docs-editor/architecture-private-clouds-1725660528

Update architecture-private-clouds.md

Author: JamesJBarnett

articles/azure-vmware/architecture-private-clouds.md

@@ -53,7 +53,7 @@ When planning your Azure VMware Solution design, use the following table to unde
 >[!IMPORTANT]
 > This mapping is important for placing your private clouds in close proximity to your Azure native workloads, including integrated services such as Azure NetApp Files and Pure Cloud Block Store (CBS). 
 
-The Multi-AZ capability for Azure VMware Solution Stretched Clusters is also tagged in the following table. Customer quota for Azure VMware Solution is assigned by Azure region, and you are not able to specify the Availability Zone during private cloud provisioning. An auto selection algorithm is used to balance deployments across the Azure region. If you have a particular Availability Zone you want to deploy to, open a [Service Request](https://rc.portal.azure.com/#create/Microsoft.Support) with Microsoft requesting a "special placement policy" for your subscription, Azure region, Availability Zone, and SKU type. This policy remains in place until you request it be removed or changed.
+The Multi-AZ capability for Azure VMware Solution Stretched Clusters is also tagged in the following table. Customer quota for Azure VMware Solution is assigned by Azure region, and you aren't able to specify the Availability Zone during private cloud provisioning. An auto selection algorithm is used to balance deployments across the Azure region. If you have a particular Availability Zone you want to deploy to, open a [Service Request](https://rc.portal.azure.com/#create/Microsoft.Support) with Microsoft requesting a "special placement policy" for your subscription, Azure region, Availability Zone, and SKU type. This policy remains in place until you request it be removed or changed.
 
 **SKUs** marked in **bold** are of limited availability due to customer consumption and quota may not be available upon request. The AV64 SKU should be used instead when AV36, AV36P, or AV52 SKUs are limited.
 
@@ -62,18 +62,18 @@ AV64 SKUs are available per Availability Zone, the table below lists the Azure r
 | Azure region | Availability Zone | SKU   | Multi-AZ SDDC | AV64 FDs Supported |
 | :---         | :---:             | :---: | :---:         | :---:           |
 | Australia East | AZ01 | AV36P, AV64 | Yes |7|
-| Australia East | AZ02 | AV36, (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024) |
+| Australia East | AZ02 | AV36, AV64| No |7|
 | Australia East | AZ03 | AV36P, AV64 | Yes |7|
-| Australia South East | AZ01 | AV36 | No | N/A |
+| Australia Southeast | AZ01 | AV36 | No | N/A |
 | Brazil South | AZ02 | **AV36** | No | N/A |
-| Canada Central | AZ02 | AV36, **AV36P,** (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024)|
+| Canada Central | AZ02 | AV36, **AV36P,** AV64| No |7|
 | Canada East | N/A | AV36| No | N/A |
 | Central India | AZ03 | AV36P, (AV64 Planned H2 2024) | No |N/A (7 Planned H2 2024) |
 | Central US | AZ01 | AV36P, (AV64 Planned H2 2024) | No |N/A (7 Planned H2 2024) |
 | Central US | AZ02 | **AV36**, (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024) |
-| Central US | AZ03 | AV36P, (AV64 Planned H2 2024) | No |N/A (7 Planned H2 2024) |
+| Central US | AZ03 | AV36P, AV64| No |7|
 | East Asia | AZ01 | AV36, (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024) |
-| East US | AZ01 | **AV36P****,** (AV64 Planned H2 2024)| Yes |N/A (7 Planned H2 2024) |
+| East US | AZ01 | **AV36P**, AV64| Yes |7|
 | East US | AZ02 | **AV36P**, AV64 | Yes | 7 |
 | East US | AZ03 | **AV36**, **AV36P**, AV64 | Yes | 7 |
 | East US 2 | AZ01 | **AV36**, AV64 | No |7|
@@ -87,13 +87,13 @@ AV64 SKUs are available per Availability Zone, the table below lists the Azure r
 | Japan West | AZ01 | **AV36**, (AV64 Planned H2 2024) | No |N/A (7 Planned H2 2024) |
 | North Central US | AZ01 | **AV36**, AV64 | No |7|
 | North Central US | AZ02 | AV36P, AV64 | No |7|
-| North Europe | AZ02 | AV36, AV64 | No | 5 (7 Planned H2 2024) |
+| North Europe | AZ02 | AV36, AV64 | No |7|
 | Qatar Central | AZ03 | AV36P, (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024) |
 | South Africa North | AZ03 | AV36, (AV64 Planned H2 2024) | No |N/A (7 Planned H2 2024) |
 | South Central US | AZ01 | AV36, AV64 | No | 7 |
 | South Central US | AZ02 | **AV36P**, AV52, AV64 | No | 7 |
-| South East Asia | AZ02 | **AV36** | No | N/A |
-| Sweden Central | AZ01 | AV36 | No | N/A |
+| Southeast Asia | AZ02 | **AV36** | No | N/A |
+| Sweden Central | AZ01 | AV36, (AV64 Planned H2 2024)| No | N/A (7 Planned H2 2024)|
 | Switzerland North | AZ01 | **AV36**, AV64 | No | 7 |
 | Switzerland North | AZ03 | AV36P, (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024) |
 | Switzerland West | AZ01 | **AV36**, AV64 | No | 7 |
@@ -104,7 +104,7 @@ AV64 SKUs are available per Availability Zone, the table below lists the Azure r
 | UK West | AZ01 | AV36 | No | N/A |
 | West Europe | AZ01 | **AV36**, AV36P, AV52, AV64 | Yes | 7 |
 | West Europe | AZ02 | **AV36**, AV64 | Yes | 7 |
-| West Europe | AZ03 | AV36P, AV64 | Yes |N/A (7 Planned H2 2024|
+| West Europe | AZ03 | AV36P, AV64 | Yes |7|
 | West US | AZ01 | AV36, AV36P | No | N/A |
 | West US 2 | AZ01 | AV36 | No | N/A |
 | West US 2 | AZ02 | AV36P | No | N/A |