Update web-protection-overview.md

Author: denisebmsft

defender-endpoint/web-protection-overview.md

@@ -50,13 +50,13 @@ Web threat protection includes:
 > [!NOTE]
 > For processes other than Microsoft Edge and Internet Explorer, web protection scenarios leverage Network Protection for inspection and enforcement:
 > - IP is supported for all three protocols (TCP, HTTP, and HTTPS (TLS)).
-- Only single IP addresses are supported (no CIDR blocks or IP ranges) in custom indicators.
-- Encrypted URLs (full path) can only be blocked on first party browsers (Internet Explorer, Edge).
-- Encrypted URLs (FQDN only) can be blocked in third party browsers (i.e. other than Internet Explorer, Edge).
-- Full URL path blocks can be applied for unencrypted URLs.
+> - Only single IP addresses are supported (no CIDR blocks or IP ranges) in custom indicators.
+> - Encrypted URLs (full path) can only be blocked on first party browsers (Internet Explorer, Edge).
+> - Encrypted URLs (FQDN only) can be blocked in third party browsers (i.e. other than Internet Explorer, Edge).
+> - Full URL path blocks can be applied for unencrypted URLs.
+
+There might be up to two hours of latency (usually less) between the time the action is taken, and the URL and IP being blocked. For more information, see [Web threat protection](web-threat-protection.md).
 
-> There may be up to 2 hours of latency (usually less) between the time the action is taken, and the URL and IP being blocked.
-> For more information, see [Web threat protection](web-threat-protection.md).
 ### Custom indicators
 
 Custom indicator detections are also summarized in your organizations web threat reports under **Web threat detections over time** and **Web threat summary**.