Alt text, adding note links to faq

Author: forstisabella

src/protocols/enforce/forward-blocked-events.md

@@ -10,7 +10,7 @@ Select the source you'll forward events to from the Blocked Events and Traits dr
 
 Since forwarding happens server to server, Segment recommends creating a [HTTP Tracking API source](/docs/connections/sources/catalog/libraries/server/http-api/), though any server-side source will work. 
 
-![](../images/blocked_event_forwarding.png)
+![A screenshot of the blocked events and traits section on the Schema Configuration settings page](../images/blocked_event_forwarding.png)
 
 > note ""
 > Only blocked events are forwarded to the source. Events with omitted traits are not forwarded. Instead, Segment inserts a `context.protocols` object into the event payload which contains the omitted properties or traits.

src/protocols/enforce/schema-configuration.md

@@ -8,9 +8,10 @@ redirect_from: '/protocols/enforce/'
 The Schema Configuration settings for each source can be used to selectively block events, or omit properties and traits from `.track()`, `.identify()` and `.group()` calls. Segment can permanently drop events that are not included in your Tracking Plan, depending on the settings you select. Segment can also block events with invalid properties or invalid property values.
 
 > warning "Blocked events not forwarded to a source are discarded"
-> Blocking is a serious step that you should only do after you have resolved any violations that appear when you first connect a Tracking Plan to a Source. Any blocked events that are not [forwarded to a separate source](/docs/protocols/enforce/forward-blocked-events) are permanently discarded and cannot be recovered.
+> Blocking is a serious step that you should only do after you have resolved any violations that appear when you first connect a Tracking Plan to a Source. Any blocked events that are not [forwarded to a separate source](/docs/protocols/enforce/forward-blocked-events) are permanently discarded and cannot be recovered. 
+> For more information about Tracking Plan versioning and blocking, see the [Protocols FAQ](/docs/protocols/faq/#protocols-tracking-plan).
 
-To enable blocking, go to the **Settings** tab for your source, and click on **Schema Controls**. See below for detailed descriptions for each of the configuration settings.
+To enable blocking, go to the **Settings** tab for your source, and click on **Schema Configuration**. See below for detailed descriptions for each of the configuration settings.
 
 ![A screenshot showing the Unplanned Events, Properties and Values table on the Schema Configuration settings page.](../images/event_blocking.png)