first draft

Author: siddomala

articles/virtual-wan/about-virtual-hub-routing-preference.md

@@ -43,14 +43,15 @@ This section explains the route selection algorithm in a virtual hub along with
    * **AS Path**
 
       1. Prefer routes with the shortest BGP AS-Path length irrespective of the source of the route advertisements. For example, whether the routes are learned from on-premises connected via S2S VPN or ER.
-      1. Prefer routes from connections local to the virtual hub over routes learned from remote hub.
+      1. Prefer routes from connedctions local to the virtual hub over routes learned from remote hub.
       1. If there are routes from both ER and S2S VPN connections, then see below. Else proceed to the next rule.
          * If all the routes are local to the virtual hub, then choose routes from ER connections.
          * If all the routes are through remote virtual hubs, then choose routes from S2S VPN connections.
 
 **Things to note:**
 
 * When there are multiple virtual hubs in a Virtual WAN scenario, a virtual hub selects the best routes using the route selection algorithm described above, and then advertises them to the other virtual hubs in the virtual WAN.
+* For a given set of destination route-prefixes, if the ExpressRoute routes are preferred and the ExpressRoute connection subsequently goes down, then routes from S2S VPN or SD-WAN NVA connections will be preferred for traffic destined to the same route-prefixes. When the ExpressRoute connection is restored, traffic destined for these route-prefixes will continue to prefer the S2S VPN or SD-WAN NVA connections. 
 
 ## Routing scenarios
 

articles/virtual-wan/virtual-wan-faq.md

@@ -432,6 +432,8 @@ You’ll only be able to update your virtual hub router if all the resources (ga
 
 If you have already configured BGP peering between your Virtual WAN hub and an NVA in a spoke VNet, then you will have to [delete and then recreate the BGP peer](create-bgp-peering-hub-portal.md). Since the virtual hub router's IP addresses change after the upgrade, you will also have to reconfigure your NVA to peer with the virtual hub router's new IP addresses. These IP addresses are represented as the "virtualRouterIps" field in the Virtual Hub's Resource JSON.
 
+If your Virtual WAN hub is connected to a combination of spoke virtual networks in the same region as the hub and a separate region than the hub, then you may need to delete and recreate your spoke virtual network connections after upgrading. We are actively working on removing this requirement. 
+
 If the update fails for any reason, your hub will be auto recovered to the old version to ensure there is still a working setup.
 
 >[!NOTE]