Merge pull request #107875 from BigMorty/dedicated-tweeks

small tweeks to a few articles

Author: ShannonLeavitt

articles/container-apps/disaster-recovery.md

@@ -16,7 +16,10 @@ Azure Container Apps uses [availability zones](../availability-zones/az-overview
 
 Availability zones are unique physical locations within an Azure region. Each zone is made up of one or more data centers equipped with independent power, cooling, and networking. To ensure resiliency, there's a minimum of three separate zones in all enabled regions. You can build high availability into your application architecture by co-locating your compute, storage, networking, and data resources within a zone and replicating in other zones.
 
-By enabling Container Apps' zone redundancy feature, replicas are automatically randomly distributed across the zones in the region.  Traffic is load balanced among the replicas.  If a zone outage occurs, traffic will automatically be routed to the replicas in the remaining zones.
+By enabling Container Apps' zone redundancy feature, replicas are automatically distributed across the zones in the region.  Traffic is load balanced among the replicas.  If a zone outage occurs, traffic will automatically be routed to the replicas in the remaining zones.
+
+> [!NOTE]
+> There is no extra charge for enabling zone redundancy, but it only provides benefits when you have 2 or more replicas, with 3 or more being ideal since most regions that support zone redundancy have 3 zones.
 
 In the unlikely event of a full region outage, you have the option of using one of two strategies:
 

articles/container-apps/networking.md

@@ -27,7 +27,7 @@ There are two architectures in Container Apps: the Consumption only architecture
 
 | Architecture Type | Description |
 |-----------|-------------|
-| Workload profiles architecture (preview) | Supports user defined routes (UDR) and egress through NAT Gateway. The minimum required subnet size is /27. |
+| Workload profiles architecture (preview) | Supports user defined routes (UDR) and egress through NAT Gateway when using a custom virtual network. The minimum required subnet size is /27. |
 | Consumption only architecture | Doesn't support user defined routes (UDR) and egress through NAT Gateway. The minimum required subnet size is /23. |
 
 ## Accessibility Levels
@@ -52,6 +52,9 @@ As you create a custom VNet, keep in mind the following situations:
   - You can define the subnet range used by the Container Apps environment.
   - You can restrict inbound requests to the environment exclusively to the VNet by deploying the environment as [internal](vnet-custom-internal.md).
 
+> [!NOTE]
+> When you provide your own virtual network, additional [managed resources](networking.md#managed-resources) are created, which incur billing.
+
 As you begin to design the network around your container app, refer to [Plan virtual networks](../virtual-network/virtual-network-vnet-plan-design-arm.md) for important concerns surrounding running virtual networks on Azure.
 
 :::image type="content" source="media/networking/azure-container-apps-virtual-network.png" alt-text="Diagram of how Azure Container Apps environments use an existing V NET, or you can provide your own.":::

articles/container-apps/quotas.md

@@ -23,7 +23,7 @@ The *Is Configurable* column in the following tables denotes a feature maximum m
 | Environments | Region |  Up to 15 | Yes | Limit up to 15 environments per subscription, per region.<br><br>For example, if you deploy to three regions you can get up to 45 environments for a single subscription. |
 | Container Apps | Environment | Unlimited | n/a | |
 | Revisions | Container app | 100 | No | |
-| Replicas | Revision | 30 | Yes | |
+| Replicas | Revision | 300 | Yes | |
 
 ## Consumption plan