From 9be3ba9c88066af393811e93aca032e0e5e30995 Mon Sep 17 00:00:00 2001
From: forstisabella <92472883+forstisabella@users.noreply.github.com>
Date: Thu, 16 Jan 2025 11:55:55 -0500
Subject: [PATCH] Update faq.md

---
 src/protocols/faq.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/protocols/faq.md b/src/protocols/faq.md
index e1badd7aaf..4bd937c661 100644
--- a/src/protocols/faq.md
+++ b/src/protocols/faq.md
@@ -144,7 +144,7 @@ The schema functionality is a _reactive_ way to clean up your data, where the Tr
 
 That being said, there are plenty of scenarios where the reactive Schema functionality solves immediate needs for customers. Often times, customers will use both Schema Controls and Tracking Plan functionality across their Segment Sources. For smaller volume Sources with less important data, the Schema functionality often works perfectly.
 
-### If I enable blocking, what happens to the blocked events? Are events just blocked from specific Destinations or the entire Segment pipeline?
+### If I enable blocking are events just blocked from specific Destinations or the entire Segment pipeline?
 
 Segment can block events from all Segment Destinations except for mobile device mode destinations.