add q to faq, link to faq

Author: forstisabella

src/protocols/enforce/schema-configuration.md

@@ -8,7 +8,8 @@ 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 Configuration**. See below for detailed descriptions for each of the configuration settings.

src/protocols/faq.md

@@ -40,7 +40,7 @@ The Tracking Plan to Source relationship is a one-to-many relationship. This mea
 
 ### Can I duplicate a Tracking Plan in the Segment UI?
 
-You can duplicate Tracking Plans in the Segment web app by following the [instructions to copy a tracking plan](/docs/protocols/tracking-plan/create/#copy-a-tracking-plan). You can also use the [Tracking Plan API](/docs/protocols/apis-and-extensions/) to copy the underlying JSON schema from one Tracking Plan to another.
+You can duplicate Tracking Plans in the Segment web app by following the [instructions to copy a tracking plan](/docs/protocols/tracking-plan/create/#copy-a-tracking-plan). You can also use the [Public API](/docs/protocols/apis-and-extensions/) to copy the underlying JSON schema from one Tracking Plan to another.
 
 ### How do I handle versioning with mobile apps?
 
@@ -66,6 +66,12 @@ 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 a 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
+
+ <!--Ask Anand clarifying q: what happens to blocked events in this senario?-->
+
 ## Protocols Validation
 
 ### What is the difference between Violations Emails and the Violations page in the Segment UI?