Merge pull request #282054 from vhorne/fwm-rule-proc

freshness review

Author: prmerger-automator[bot]

articles/firewall-manager/rule-processing.md

@@ -5,7 +5,7 @@ services: firewall-manager
 author: vhorne
 ms.service: firewall-manager
 ms.topic: conceptual
-ms.date: 04/06/2023
+ms.date: 07/29/2024
 ms.author: victorh
 ---
 
@@ -15,12 +15,12 @@ Azure Firewall has NAT rules, network rules, and applications rules. The rules a
 
 ## Network rules and applications rules
 
-Network rules are applied first, then application rules. The rules are terminating. So if a match is found in network rules, then application rules aren't processed.  If no network rule matches, and if the packet protocol is HTTP/HTTPS, application rules then evaluate the packet. If still no match is found, then the packet is evaluated against the infrastructure rule collection. If there's still no match, then the packet is denied by default.
+Network rules are applied first, then application rules. The rules are terminating. So if a match is found in network rules, then application rules aren't processed. If no network rule matches, and if the packet protocol is HTTP/HTTPS, application rules then evaluate the packet. If still no match is found, then the packet is evaluated against the infrastructure rule collection. If there's still no match, then the packet is denied by default.
 
 ![General rule processing logic](media/rule-processing/rule-logic-processing.png)
 
 ### Example of processing logic
-Example scenario: three rule collection groups exist in an Azure Firewall Policy.  Each rule collection group has a series of application and network rules.
+Example scenario: three rule collection groups exist in an Azure Firewall Policy. Each rule collection group has a series of application and network rules.
 
 ![Rule execution order](media/rule-processing/rule-execution-order.png)