Merge pull request #127332 from changeworld/patch-16

Fix typo: Auxillary -> Auxiliary

Author: v-dirichards

articles/virtual-wan/how-to-network-virtual-appliance-add-ip-configurations.md

@@ -45,7 +45,7 @@ The following table describes the types of Network Interfaces that are attached
 |--|--|--|--|
 | External/Public |Mandatory| One \<private IP, public IP\> pair|Yes|
 |Internal/Private| Mandatory | One private IP| Yes|
-|Additional/Auxillary| Optional| One private IP or one \<private, public IP\> pair| No|
+|Additional/Auxiliary| Optional| One private IP or one \<private, public IP\> pair| No|
 
 The following example describes an NVA in Virtual WAN hub where multiple IP configurations are assigned:
 
@@ -63,7 +63,7 @@ The following section describes known limitations and considerations associated
 ### Limitations
 
 * Each NVA NIC (External or Internal) can have at most three IP-configurations. This limit is to help ensure that there are sufficient IP addresses available in the Virtual WAN hub to allocate to NVA deployments.  
-* Additional/Auxillary NICs must have exactly one IP-configuration. You can't add additional IP addresses to Additional/Auxillary NICs.
+* Additional/Auxiliary NICs must have exactly one IP-configuration. You can't add additional IP addresses to Additional/Auxiliary NICs.
 * Azure Virtual WAN Hub routers initiates/accepts Border Gateway Protocol (BGP) sessions with the primary IP configuration of the internal/private NIC assigned to each NVA VM instance. Secondary IP configurations assigned to the internal/private NIC of NVA instances can't be used to establish BGP.
 * IP configurations must adhere to the following naming convention:
     * IP configurations on the private/internal NIC must have *privatenicipconfig* prefix. For example, *privatenicipconfig-1* is a valid name while *myprivateipconfig* isn't a valid name for private/internal NIC IP configurations.