acrolinx

Author: v-dirichards

articles/firewall-manager/overview.md

@@ -87,7 +87,7 @@ Azure Firewall Manager has the following known issues:
 |Branch to branch traffic with private traffic filtering enabled|Branch to branch traffic can be inspected by Azure Firewall in secured hub scenarios if Routing Intent is enabled. |Enable Routing Intent on your Virtual WAN Hub by setting Inter-hub to **Enabled** in Azure Firewall Manager. See [Routing Intent documentation](../virtual-wan/how-to-routing-policies.md) for more information about this feature. The only Virtual WAN routing configuration that enables branch to branch private traffic is routing intent. |
 |All Secured Virtual Hubs sharing the same virtual WAN must be in the same resource group.|This behavior is aligned with Virtual WAN Hubs today.|Create multiple Virtual WANs to allow Secured Virtual Hubs to be created in different resource groups.|
 |Bulk IP address addition fails|The secure hub firewall goes into a failed state if you add multiple public IP addresses.|Add smaller public IP address increments. For example, add 10 at a time.|
-|DDoS Protection not supported with secured virtual hubs|DDoS Protection isn't integrated with vWANs.|Investigating<br><br>You can now associate a public IP address created in your tenants to secured hubs. The public IP addressess can be configured with Azure DDoS Protection. For more information, see [Customer provided public IP address support in secured hubs (preview)](../firewall/secured-hub-customer-public-ip.md).|
+|DDoS Protection not supported with secured virtual hubs|DDoS Protection isn't integrated with vWANs.|Investigating<br><br>You can now associate a public IP address created in your tenants to secured hubs. The public IP addresses can be configured with Azure DDoS Protection. For more information, see [Customer provided public IP address support in secured hubs (preview)](../firewall/secured-hub-customer-public-ip.md).|
 |Activity logs not fully supported|Firewall policy doesn't currently support Activity logs.|Investigating|
 |Description of rules not fully supported|Firewall policy doesn't display the description of rules in an ARM export.|Investigating|
 |Azure Firewall Manager overwrites static and custom routes causing downtime in virtual WAN hub.|You shouldn't use Azure Firewall Manager to manage your settings in deployments configured with custom or static routes. Updates from Firewall Manager can potentially overwrite static or custom route settings.|If you use static or custom routes, use the Virtual WAN page to manage security settings and avoid configuration via Azure Firewall Manager.<br><br>For more information, see [Scenario: Azure Firewall - custom](../virtual-wan/scenario-route-between-vnets-firewall.md).|