Minor changes

Author: pwseg

src/engage/journeys/send-data.md

@@ -46,13 +46,13 @@ To use Trait Activation with Journeys:
 
 ## What events are sent to destinations?
 
-The data type you send to a destination depends on whether the destination is an Event destination, or a List destination.
+The data type you send to a destination depends on whether the destination is an Event destination or a List destination.
 
-To view the events that are generated by an Engage Space's Journeys, 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 that get generated by an Engage Space's Journeys, navigate to **Unify settings > Debugger** to view the list of sources that are configured to generate events for [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 generates events only to its connected destinations. Under the source's Debugger tab, you'll find the most recent events generated by that source according the connected destinations' audiences and computed traits. 
 
-The full json body of a journey event will have the 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/).
+The full JSON body of a journey event will have the journey's specific details found 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 journey 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 journeys are connected to that specific destination.
+The integrations object in these payloads will appear as `{"All" : false,}` and only list some destinations. This is due to the fact that each source has multiple destinations connected, while each journey 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 according to the journeys that are connected to that specific destination.
 
 ### Event destination
 
@@ -67,7 +67,7 @@ When the user enters the step:
   "context": {
     "personas": {
       "computation_class": "audience", // the type of computation
-      "computation_id": "aud_###", // the audience's id found in the URL
+      "computation_id": "aud_###", // the audience's ID, found in the URL
       "computation_key": "j_o_###", // the configured journey key that appears on user profile
       "namespace": "spa_###", // the Engage Space's ID
       "space_id": "spa_###" // the Engage Space's ID
@@ -90,7 +90,7 @@ When the user enters the step:
   "context": {
     "personas": {
       "computation_class": "audience", // the type of computation
-      "computation_id": "aud_###", // the audience's id found in the URL
+      "computation_id": "aud_###", // the audience's ID found in the URL
       "computation_key": "j_o_###", // the configured journey key that appears on user profile
       "namespace": "spa_###", // the Engage Space's ID
       "space_id": "spa_###" // the Engage Space's ID