DOC-242 Destination Actions filters update

[markzegarelli]

@netlify /docs/connections/destinations/actions/

[netlify]

✔️ Deploy Preview for segment-docs ready!

🔨 Explore the source changes: fea4cae

🔍 Inspect the deploy log: https://app.netlify.com/sites/segment-docs/deploys/60e62e786b27de00074d5a59

😎 Browse the preview: https://deploy-preview-1724--segment-docs.netlify.app

[mshwery]

Made some suggestions. Take 'em or leave 'em

[mshwery]

Suggested change

**Subscriptions** handle the individual calls to the destination. In them, you define what type of call you want to make to the destination, and what triggers that call. Individual Destination Actions come enabled with some predefined subscriptions to handle common events like Screen calls, Identify calls, and Track calls. Subscriptions have two components that make this possible: **Triggers** and an **Action**.

**Subscriptions** allow you to subscribe to events that you'd like to trigger actions in the destination. In them, you define which types of events you want to subscribe to, which action they should trigger, and how they should be transformed when sending to the destination action. Some Destinations come enabled with some predefined subscriptions (presets) to provide recommended scenarios like Screen calls, Identify calls, and Track calls. Subscriptions have two components that make this possible: a **Trigger** and an **Action**.

Not sure if this is clearer.

[mshwery]

Suggested change

	**Triggers** enable you to define *when* the corresponding Action fires. As part of a Trigger, you can use condition-based filters to narrow the scope of the trigger.
	**Triggers** enable you to define *when* the corresponding Action fires. As part of a Trigger, you can use condition-based filters to narrow the scope of the trigger to particular kinds of Segment events.