edits

Author: rchinn1

src/engage/using-engage-data.md

@@ -61,11 +61,11 @@ User-list destinations can have individual limits on how often Segment can sync
 
 The payloads sent from your Engage space to your destinations will be different depending on if you configured the destination to receive identify or track calls, and whether the payload is coming from a computed trait or audience. As a reminder, identify calls usually update a trait on a user profile or table, whereas track calls send a point-in-time event that can be used as a campaign trigger or a detailed record of when a user's audience membership or computed trait value was calculated.
 
-To view the events that are generated by an Engage Space's audience or computed traits, navigate to Unify settings / Debugger / to view the list of Sources that are configured to generate events per [each destination instance](https://segment.com/docs/engage/warehouses/#why-are-there-multiple-schemas-prefixed-with-engage_-in-my-warehouse-when-i-only-have-one-space:~:text=Segment%20currently%20can,schemas%20than%20spaces.). Each source will only generate events to its connected destinations, and under the Source's Debugger tab will be the most recent events generated by that source per the connected destinations' audiences and computed traits. 
+To view the events generated by an Engage Space's audience or computed traits, navigate to **Unify settings > Debugger** and view the list of sources that are configured to generate events per [each destination instance](/docs/engage/warehouses/#why-are-there-multiple-schemas-prefixed-with-engage_-in-my-warehouse-when-i-only-have-one-space:~:text=Segment%20currently%20can,schemas%20than%20spaces.). Each source will only generate events to connected destinations. From the source's Debugger tab, you'll find the most recent events generated by that source per the connected destinations' audiences and computed traits. 
 
-The full json body of an audience, computed trait, or journey event will have the audience's/trait's/journey's specific details found under the `context.personas` object. These fields can be useful when building out [Destination Filters](https://segment.com/docs/connections/destinations/destination-filters/), [Actions destination mappings](https://segment.com/docs/connections/destinations/actions/#set-up-a-destination-action), and [Functions](https://segment.com/docs/connections/functions/).
+In the full json body of an audience, computed trait, or journey, you'll find specific details under the `context.personas` object. These fields can be useful when building out [Destination Filters](/docs/connections/destinations/destination-filters/), [Actions destination mappings](/docs/connections/destinations/actions/#set-up-a-destination-action), and [Functions](/docs/connections/functions/).
 
-The integrations object in these payloads will appears as `{"All" : false,}` and only lists some destinations. This is due to the fact that each source has multiple destinations connected while each audience/trait may only have a subset of destinations connected to it. See [Filtering with the Integrations Object](https://segment.com/docs/guides/filtering-data/#filtering-with-the-integrations-object) for more information. The integrations object routing specific events to its specified destinations is also why a destination's [Delivery Overview](https://segment.com/docs/connections/delivery-overview/) tab will show a large number of events under the [Filtered at destination](https://segment.com/docs/connections/delivery-overview/#:~:text=Filtered%20at%20destination%3A%20Events,will%20be%20filtered%20out.) box, as that destination will only receive the events intended to be sent to it by which audiences/ traits/ journeys are connected to that specific destination.
+The integrations object in the payload displays as `{"All" : false,}` and only lists some destinations. This is due to the fact that each source has multiple destinations connected while each audience/trait may only have a subset of destinations connected to it. See [Filtering with the Integrations Object](/docs/guides/filtering-data/#filtering-with-the-integrations-object) for more information. The integrations object routing specific events to its specified destinations is also why a destination's [Delivery Overview](/docs/connections/delivery-overview/) tab will show a large number of events under the [Filtered at destination](/docs/connections/delivery-overview/#:~:text=Filtered%20at%20destination%3A%20Events,will%20be%20filtered%20out.) box, as that destination will only receive the events intended to be sent to it by audiences, traits, or journeys that are connected to that specific destination.
 
 ### Computed Trait generated events
 
@@ -138,7 +138,7 @@ Engage only sends events to the destination if the Computed Trait value has chan
 }
 ```
 
-`Track` events generated by an Audience have a key for the audience name, and a key for the audience value:
+`Track` events generated by an Audience have a key for the Audience name, and for the Audience value:
 
 ```js
 {