Enhance details on resource allocation and networking

Expanded the explanation of custom sizes and virtual network deployment for Azure Container Instances.

Author: staleycyn

learn-pr/wwl-azure/configure-azure-container-instances/includes/3-review.md

@@ -26,12 +26,12 @@ Let's review some of the [benefits of using Azure Container Instances](/azure/co
 
 - **Public IP connectivity and DNS names**. Containers can be directly exposed to the internet with an IP address and FQDN (fully qualified domain name).
 
-- **Custom sizes**. Container nodes can be scaled dynamically to match actual resource demands for an application.
+- **Custom sizes**. You specify CPU cores (from 0.1 to 4 vCPU) and memory (from 0.1 to 16 GB) for each container at deployment time. Resource allocation is fixed for the lifetime of the container group.
 
 - **Persistent storage**. Containers support direct mounting of Azure Files file shares.
 
 - **Linux and Windows containers**. Container Instances can schedule both Windows and Linux containers. Specify the operating system type when you create your container groups.
 
 - **Coscheduled groups**. Container Instances supports scheduling of multi-container groups that share host machine resources.
 
-- **Virtual network deployment**. Container Instances can be deployed into an Azure virtual network.
+- **Virtual network deployment**. Linux container groups can be deployed into an Azure virtual network for private communication with other Azure resources. Virtual network deployed containers receive no public IP address and communicate only within the virtual network or peered networks.