From 89c95ececa7f7ab08f81b141288344ed6510b0cd Mon Sep 17 00:00:00 2001
From: Markus Sarcletti <56821677+msarcletti@users.noreply.github.com>
Date: Wed, 4 Dec 2024 13:35:37 +0100
Subject: [PATCH] Update
 windows/security/operating-system-security/network-security/windows-firewall/rules.md

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

diff --git a/windows/security/operating-system-security/network-security/windows-firewall/rules.md b/windows/security/operating-system-security/network-security/windows-firewall/rules.md
index c8d1b08b14..64b6580098 100644
--- a/windows/security/operating-system-security/network-security/windows-firewall/rules.md
+++ b/windows/security/operating-system-security/network-security/windows-firewall/rules.md
@@ -35,7 +35,7 @@ When first installed, network applications and services issue a *listen call* sp
 - If the user has admin permissions, they're prompted. If they respond *No* or cancel the prompt, block rules are created. Two rules are typically created, one each for TCP and UDP traffic
 - If the user isn't a local admin and they are prompted, block rules are created. It doesn't matter what option is selected
 
-To avoid this, **disable** the notification prompt. This can be done using [PowerShell or command prompt](/windows/security/operating-system-security/network-security/windows-firewall/configure-with-command-line) or in the Windows Firewall with Advanced Security console on the 'Customize Settings' tab of each profile.
+To disable the notification prompt, you can use the [command line](/windows/security/operating-system-security/network-security/windows-firewall/configure-with-command-line) or the **Windows Firewall with Advanced Security** console
   
   :::column-end:::
   :::column span="2":::