From 1ecd193386af9e7d5ceade788ebdf4393bbed5c0 Mon Sep 17 00:00:00 2001
From: Stephanie Savell <101299710+v-stsavell@users.noreply.github.com>
Date: Mon, 9 Oct 2023 10:23:34 -0500
Subject: [PATCH] Update
 windows/security/operating-system-security/network-security/windows-firewall/configure-the-windows-firewall-log.md

---
 .../windows-firewall/configure-the-windows-firewall-log.md      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/security/operating-system-security/network-security/windows-firewall/configure-the-windows-firewall-log.md b/windows/security/operating-system-security/network-security/windows-firewall/configure-the-windows-firewall-log.md
index b6d0f091f4..daa952247d 100644
--- a/windows/security/operating-system-security/network-security/windows-firewall/configure-the-windows-firewall-log.md
+++ b/windows/security/operating-system-security/network-security/windows-firewall/configure-the-windows-firewall-log.md
@@ -52,7 +52,7 @@ Sometimes the Windows Firewall log files aren't created, or the events aren't wr
   - the log folder in a custom path doesn't exist
   In both cases, you must create the folder manually or via script, and add the permissions for MpsSvc
 
-If firewall logging is configured via Group Policy only, it also can happen that the `firewall` folder is not created in the default location `%windir%\System32\LogFiles\`. The same can happen if a custom path to a non-existant folder is configered via Group Policy. In this case, create the folder manually or via script and add the permissions for MPSSVC.  
+If firewall logging is configured via Group Policy only, it also can happen that the `firewall` folder is not created in the default location `%windir%\System32\LogFiles\`. The same can happen if a custom path to a non-existent folder is configured via Group Policy. In this case, create the folder manually or via script and add the permissions for MPSSVC.  
 
 ```PowerShell
 New-Item -ItemType Directory -Path $env:windir\System32\LogFiles\Firewall