From aabd947fff140449541ba3cdc9bc5b1e5eb0e25a Mon Sep 17 00:00:00 2001
From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com>
Date: Tue, 21 Nov 2023 14:51:53 -0500
Subject: [PATCH] updates

---
 .openpublishing.redirection.windows-security.json             | 4 ++--
 .../network-security/windows-firewall/index.md                | 2 +-
 .../network-security/windows-firewall/tools.md                | 4 ++--
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/.openpublishing.redirection.windows-security.json b/.openpublishing.redirection.windows-security.json
index 3ec41a760f..be07145db2 100644
--- a/.openpublishing.redirection.windows-security.json
+++ b/.openpublishing.redirection.windows-security.json
@@ -8007,7 +8007,7 @@
     },
     {
       "source_path": "windows/security/operating-system-security/network-security/windows-firewall/windows-firewall-with-advanced-security-administration-with-windows-powershell.md",
-      "redirect_url": "/windows/security/operating-system-security/network-security/configure-with-command-line",
+      "redirect_url": "/windows/security/operating-system-security/network-security/windows-firewall/configure-with-command-line",
       "redirect_document_id": false
     },
     {
@@ -8017,7 +8017,7 @@
     },
     {
       "source_path": "windows/security/operating-system-security/network-security/windows-firewall/best-practices-configuring.md",
-      "redirect_url": "/windows/security/operating-system-security/network-security/configure",
+      "redirect_url": "/windows/security/operating-system-security/network-security/windows-firewall/configure",
       "redirect_document_id": false
     },
     {
diff --git a/windows/security/operating-system-security/network-security/windows-firewall/index.md b/windows/security/operating-system-security/network-security/windows-firewall/index.md
index a70e90f998..f1d2d5e956 100644
--- a/windows/security/operating-system-security/network-security/windows-firewall/index.md
+++ b/windows/security/operating-system-security/network-security/windows-firewall/index.md
@@ -37,7 +37,7 @@ Windows Firewall offers several benefits to address your organization's network
 
 The default behavior of Windows Firewall is to:
 
-- block all incoming traffic, unless solicited or maching a *rule*
+- block all incoming traffic, unless solicited or matching a *rule*
 - allow all outgoing traffic, unless matching a *rule*
 
 ### Firewall rules
diff --git a/windows/security/operating-system-security/network-security/windows-firewall/tools.md b/windows/security/operating-system-security/network-security/windows-firewall/tools.md
index 81d8ce2a84..f77a0e77df 100644
--- a/windows/security/operating-system-security/network-security/windows-firewall/tools.md
+++ b/windows/security/operating-system-security/network-security/windows-firewall/tools.md
@@ -121,9 +121,9 @@ An important Windows Firewall feature you can use to mitigate damage during an a
 
 Shields up can be achieved by checking **Block all incoming connections, including those in the list of allowed apps** setting found in either the Windows Settings app or Control Panel.
 
-![Incoming connections.](images/fw06-block.png)
+:::image type="content" alt-text="Screenshot of the Windows Security app showing incoming connections." source="images/fw06-block.png":::
 
-:::image type="content" alt-text="Firewall cpl." source="images/fw07-legacy.png":::
+:::image type="content" alt-text="Screenshot of the Control Panel Firewall applet." source="images/fw07-legacy.png":::
 
 By default, the Windows Firewall blocks everything unless there's an exception rule created. The *shield up* option overrides the exceptions. For example, the Remote Desktop feature automatically creates firewall rules when enabled. However, if there's an active exploit using multiple ports and services on a host, you can, instead of disabling individual rules, use the shields up mode to block all inbound connections, overriding previous exceptions, including the rules for Remote Desktop. The Remote Desktop rules remain intact but remote access can't work as long as shields up is active.