From ac951fcbdc940aa4513476e37ae79df953a220ed Mon Sep 17 00:00:00 2001
From: Nilanjana Ganguly <74384702+ngangulyms@users.noreply.github.com>
Date: Wed, 11 Oct 2023 10:51:49 -0700
Subject: [PATCH] Update
 windows/security/operating-system-security/network-security/windows-firewall/best-practices-configuring.md

Co-authored-by: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com>
---
 .../windows-firewall/best-practices-configuring.md              | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/security/operating-system-security/network-security/windows-firewall/best-practices-configuring.md b/windows/security/operating-system-security/network-security/windows-firewall/best-practices-configuring.md
index 0eab04c64d..37c7bd40cd 100644
--- a/windows/security/operating-system-security/network-security/windows-firewall/best-practices-configuring.md
+++ b/windows/security/operating-system-security/network-security/windows-firewall/best-practices-configuring.md
@@ -213,7 +213,7 @@ When creating an inbound or outbound rule, you should specify details about the
 
 Windows Firewall now supports the use of Windows Defender Application Control (WDAC) Application ID (AppID) tags in firewall rules. With this capability, Windows Firewall rules can now be scoped to an application or a group of applications by referencing process tags, without using absolute path or sacrificing security. There are two steps for this configuration: 
 
-**Step 1: Deploy WDAC AppId Tagging Policies**
+### Step 1: Deploy WDAC AppId Tagging Policies
 
 A Windows Defender Application Control (WDAC) policy needs to be deployed which specifies individual applications or groups of applications to apply a PolicyAppId tag to the process token(s). Then, the admin can define firewall rules which are scoped to all processes tagged with the matching PolicyAppId.