From 7d941d7967892016fe2cbfa7babe78c1fa7ec386 Mon Sep 17 00:00:00 2001
From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com>
Date: Fri, 17 Nov 2023 10:43:52 -0500
Subject: [PATCH] updates

---
 .../windows-firewall/index.md                 | 19 ++++++++-----------
 1 file changed, 8 insertions(+), 11 deletions(-)

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 865abc5760..5860ceff3a 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
@@ -40,6 +40,8 @@ The default behavior of Windows Firewall is to:
 - block all incoming traffic, unless solicited or maching a *rule*
 - allow all outgoing traffic, unless matching a *rule*
 
+### Firewall rules
+
 *Firewall rules* identify communication to be allowed or blocked, and the conditions for this to happen. The rules offer an extensive selection of conditions to identify traffic, including:
 
 - source and destination IP addresses
@@ -54,17 +56,12 @@ The default behavior of Windows Firewall is to:
 
 Windows Firewall offers three network profiles: domain, private and public. The network profiles are used to assign rules. For example, you can allow a specific application to communicate on a private network, but not on a public network.
 
-### :::image type="icon" source="images/domain-network.svg" border="false"::: Domain network
-
-The *domain network* profile is automatically applied to a device that is joined to an Active Directory domain, when it detects the availability of a domain controller. This network profile cannot be set manually.
-
-### :::image type="icon" source="images/private-network.svg" border="false"::: Private network
-
-The *private network* profile is designed for private networks such as a home network. It can be set on a network interface by an administrator.
-
-### :::image type="icon" source="images/public-network.svg" border="false"::: Public network
-
-The *public network* profile is designed with higher security in mind for public networks, like Wi-Fi hotspots, coffee shops, airports, hotels, etc. It's the default profile for unidentified networks.
+    #### :::image type="icon" source="images/domain-network.svg" border="false"::: Domain network
+    The *domain network* profile is automatically applied to a device that is joined to an Active Directory domain, when it detects the availability of a domain controller. This network profile cannot be set manually.
+    #### :::image type="icon" source="images/private-network.svg" border="false"::: Private network
+    The *private network* profile is designed for private networks such as a home network. It can be set on a network interface by an administrator.
+    #### :::image type="icon" source="images/public-network.svg" border="false"::: Public network
+    The *public network* profile is designed with higher security in mind for public networks, like Wi-Fi hotspots, coffee shops, airports, hotels, etc. It's the default profile for unidentified networks.
 
 ## Next steps