updating KI

Author: wtnlee

articles/virtual-wan/whats-new.md

@@ -109,7 +109,7 @@ The following features are currently in gated public preview. After working with
 |10 |Unable to update route tables and routing configuration (propagated route table and label)  for on-premises (VPN, ExpressRoute, NVA) connections. | When a Virtual WAN hub and its gateway(s) are in different Azure resource groups, updating routing configuration results in a "resource not found" error. | March 2025| This issue is caused by a code defect in Azure portal. Use Terraform, PowerShell, CLI or REST API to manage your Virtual WAN deployment.|
 |11| Hub won't advertise routes to VPN sites | When a customer uses Route-Maps for the first time it triggers an upgrade. After the upgrade is complete, If VPN sites aren't advertising routes to the hub, the hub won't advertise routes to the VPN sites. | December 2024 | If the VPN sites start adverting any routes to the hub, the hub will start adverting routes again.|
 |12| Virtual Hub router does not select local routes over remote. | When the same route is advertised from on-premises to Azure to multiple Virtual WAN hubs, the local Virtual WAN hub may experience a race condition where a route learnt from a remote hub may be selected over a route learnt from a local on-premises site. This happens in scenarios where the local route's AS-PATH length is 2 or more AS-PATH lengths **longer** than that of the remote hub. For example, the race condition is triggered when the local VPN route has AS-PATH length 4 and the remote VPN route has AS-PATH length 2.| | Ensure the difference in AS-PATH length between local and remote routes is at most 1. In the example provided in the description of this known issue, you can increase the AS-PATH length of the remote VPN route, or decrease the length of the local VPN route by modifying on-premises AS-PATH pre-pending or applying [route maps](route-maps-about.md).   |
-|13|Incomplete activity log and resource change history| Operations on certain Virtual WAN hub resources and connected Virtual Networks are not properly tracked by Azure Resource Manager, resulting in incomplete activity log and resource change history (change analysis). ||None|
+|13|Incomplete activity log and resource change history| Certian operations on certain Virtual WAN hub and connected Virtual Networks are not properly tracked by Azure Resource Manager, resulting in incomplete activity log and resource change history (change analysis). ||None|
 
 ## Next steps