added mapping

Author: wtnlee

articles/virtual-wan/about-nva-hub.md

@@ -136,6 +136,14 @@ The following table describes the number of IP addresses available for NVA deplo
 
 The number of IP addresses that are consumed by a single NVA deployment is calculated separately for the internal and external interfaces. NVAs deployed in the same hub consume IP addresses from the same subnet as other NVAs and therefore all NVAs in the same hub contribute towards to hub's limit.
 
+The following table shows the number of NVA instances deployed for different scale units.
+
+|Scale Unit| Instances|
+|--|--|
+|2-20|2|
+|30-40|3|
+|60|4|
+|80|5|
 
 **Internal Interface**
 

articles/virtual-wan/how-to-nva-hub.md

@@ -60,7 +60,6 @@ Ensure your Virtual WAN hub has sufficient IP addresses to allow for scalability
 
 For more information on how Virtual WAN allocates IP addresses to NVAs in the hub, see [hub address space for NVAs documentation](about-nva-hub.md#hub-address-space).
 
-
 ## Assigning Permissions to Azure Managed Application
 
 Network Virtual Appliances that are deployed via Azure Marketplace Managed Application are deployed in a special resource group in your Azure tenant called the **managed resource group**. When you create a Managed Application in your subscription, a corresponding and separate **managed resource group** is created in your subscription. All Azure resources created by the Managed Application (including the Network Virtual Appliance) are deployed into the **managed resource group**.