fixes

Author: forstisabella

src/protocols/enforce/schema-configuration.md

@@ -5,12 +5,10 @@ redirect_from: '/protocols/enforce/'
 
 {% include content/plan-grid.md name="protocols" %}
 
-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.
+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.
-> 
-> For more information about Tracking Plan versioning, 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 Configuration**. See below for detailed descriptions for each of the configuration settings.
 

src/protocols/faq.md

@@ -70,7 +70,7 @@ No. Unfortunately it's not yet possible to automatically transfer events from a
 
 Yes. Using the [Public API](/docs/protocols/apis-and-extensions/), you can copy a Tracking Plan's JSON schema from one Workspace to another. 
 
-If you set up event blocking alongside your original tracking plan, you must connect to the same Source and configure identical Schema Controls in your other Workspace so that blocked events behave as expected.
+If you [discarded events](/docs/protocols/enforce/schema-configuration) as a part of your original Tracking Plan, you must connect to the same Source and configure identical Schema Controls in your other Workspace so that blocked events behave as expected.
 
 ## Protocols Validation