From 78b2e60ccae970c42eae1e1e8bfbe4fd6cdec8b1 Mon Sep 17 00:00:00 2001
From: msarcletti <56821677+msarcletti@users.noreply.github.com>
Date: Mon, 9 Oct 2023 15:34:47 +0200
Subject: [PATCH] Update
 windows/security/operating-system-security/network-security/windows-firewall/configure-the-windows-firewall-log.md

Co-authored-by: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com>
---
 .../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 7f6679dd97..d875961d63 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
@@ -50,7 +50,7 @@ If firewall logging is configured via Group Policy only, it also can happen that
 New-Item -ItemType Directory -Path $env:windir\System32\LogFiles\Firewall
 ```
 
-Verify if mpssvc has FullControl on the folder and the files.
+Verify if MpsSvc has *FullControl* on the folder and the files.
 Open an elevated PowerShell and use these commands. Make sure to use the correct path.
 
 ```