Update Actions destinations info

Author: pwseg

src/connections/functions/insert-functions.md

@@ -164,13 +164,13 @@ If you don't supply a function for an event type, Segment throws an `EventNotSup
 
 You can read more about [error handling](#destination-insert-functions-logs-and-errors) below.
 
-## Insert Functions and Actions Destinations
+## Insert Functions and Actions destinations
 
 There are a couple of behavorial nuances to consider when using Insert Functions with Actions destinations.
 
-One thing to keep in mind is that Insert Functions block Actions destinations from triggering multiple mapping subscriptions for a single payload. If you have a single payload coming through the pipeline that you expect to trigger multiple mapping subscriptions in your configuration, that will work as expected without an Insert Function enabled. With an Insert Function enabled, however, when a payload that is meant to trigger multiple mappings subscriptions is seen you will find that none of the mappings subscriptions will fire. Please ensure that your payloads are only configured to trigger a single mapping subscription if you have an Insert Function enabeld on that destination.
+Insert Functions block Actions destinations from triggering multiple mapping subscriptions for a single payload. If you have a single payload coming through the pipeline that you expect to trigger multiple mapping subscriptions in your configuration, it will work as expected without an Insert Function enabled. With an Insert Function enabled, however, when a payload that is meant to trigger multiple mappings subscriptions is seen, no mappings subscriptions will fire. If you have an Insert Function enabled for a destination, make sure that you configure your payloads so that they only trigger a single mapping subscription.
 
-Another thing to know is that a payload must come into the pipeline with the attributes that allow it to match your mapping triggers. You can't use an Insert Function to change the event to match your mapping triggers. If an event comes into an Actions destiantion and already matches a mapping trigger, that mapping subscription will fire. If a payload does not come to the Actions destination matching a mapping trigger, even if an Insert Function is meant to alter the event to allow to to match a trigger, it will not fire that mapping subscription. The mapping trigger is seen first in the pipeline so a payload won't make it to the Insert Function at all if it doesn't come into the pipeline matching a mapping trigger. 
+A payload must also come into the pipeline with the attributes that allow it to match your mapping triggers. You can't use an Insert Function to change the event to match your mapping triggers. If an event comes into an Actions destination and already matches a mapping trigger, that mapping subscription will fire. If a payload doesn't come to the Actions destination matching a mapping trigger, even if an Insert Function is meant to alter the event to allow it to match a trigger, it won't fire that mapping subscription. Segment sees the mapping trigger first in the pipeline, so a payload won't make it to the Insert Function at all if it doesn't come into the pipeline matching a mapping trigger. 
 
 ## Create settings and secrets