added A to Q&A, content edits

Author: forstisabella

src/protocols/enforce/schema-configuration.md

@@ -7,12 +7,12 @@ 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.
+> 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 and blocking, see the [Protocols FAQ](/docs/protocols/faq/#protocols-tracking-plan).
+> 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.
+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)
 

src/protocols/faq.md

@@ -66,11 +66,11 @@ Yes. [Tracking Plan Libraries](/docs/protocols/tracking-plan/libraries/) makes i
 
 No. Unfortunately it's not yet possible to automatically transfer events from a Tracking Plan to Libraries. To import events into a new event library, import them directly from a source.
 
-### Can I transfer Tracking Plans between production and staging environments?
+### Can I transfer a Tracking Plan between production and staging environments?
 
-Yes. Using the [Public API](/docs/protocols/apis-and-extensions/), you can copy the underlying JSON schema from a Tracking Plan in one workspace to another. Any blocked events in the original Tracking Plan
+Yes. Using the [Public API](/docs/protocols/apis-and-extensions/), you can copy a Tracking Plan's JSON schema from one Workspace to another. 
 
- <!--Ask Anand clarifying q: what happens to blocked events in this senario?-->
+If you set up event blocking for 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