Merge pull request #1542 from segmentio/irinasayshi-patch-3

Update forward-violations.md

Author: markzegarelli

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

@@ -11,7 +11,7 @@ Select the source you'll forward events to from the Blocked Events and Traits dr
 ![](../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.**
+> 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.
 
 > note ""
-> Billing Note: Events forwarded to another Source count towards to your MTU counts. Blocking and discarding events does not contribute to your MTU counts.**
+> Billing Note: Events forwarded to another Source count towards to your MTU counts. Blocking and discarding events does not contribute to your MTU counts.

src/protocols/validate/forward-violations.md

@@ -5,7 +5,9 @@ title: Forward Violations
 {% include content/plan-grid.md name="protocols" %}
 
 
-You can forward Violations (data that does not conform to your Protocols tracking plan) to a Segment Source to enable custom notifications, dashboards and further analysis in any Segment destination that accepts cloud-mode data. To set up forwarding, visit your Source settings tab and select which Source you want to forward events to from the dropdown. Similar to [Blocked Event forwarding](/docs/protocols/enforce/forward-blocked-events/), we recommend that you create a new Source for violations.
+You can forward Violations (data that does not conform to your Protocols tracking plan) to a Segment Source to enable custom notifications, dashboards and further analysis in any Segment destination that accepts cloud-mode data. 
+
+To set up forwarding, navigate to the settings tab of the Source, then Schema Configuration. Select the source you'll forward events to from the Forwarding Settings Violations dropdown. Similar to [Blocked Event forwarding](/docs/protocols/enforce/forward-blocked-events/), Segment recommends that you create a new Source for violations.
 
 ![](../images/violation_forwarding.png)
 
@@ -48,6 +50,8 @@ Violations are sent to the selected Source as `analytics.track()` calls. The cal
     }
 ```
 
-**Billing Note: Enabling Violation forwarding generates one (1) additional MTU in your workspace, total. If you are on an API billing plan, you are charged for the increased API volume generated by the forwarded violations.**
+> note ""
+> Billing Note: Enabling Violation forwarding generates one (1) additional MTU in your workspace, total. If you are on an API billing plan, you are charged for the increased API volume generated by the forwarded violations.
 
-**Schema and debugger Note:`Violation Generated` events do not appear in the source's Schema tab. They do appear as Violation Generated events in the [debugger](/docs/connections/sources/debugger/).**
+> note ""
+> Schema and debugger Note:`Violation Generated` events do not appear in the source's Schema tab. They do appear as Violation Generated events in the [debugger](/docs/connections/sources/debugger/).