Skip to content

Commit e174e38

Browse files
Update src/connections/destinations/actions.md
Co-authored-by: forstisabella <[email protected]>
1 parent 986e587 commit e174e38

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/connections/destinations/actions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Destination Actions are available to all customers on all Segment plans. You do
3232
- You can use the [Event Tester](/docs/connections/test-connections) with Destination Actions. Event delivery metrics are collected and available in the destination information pages.
3333
- If you are using [Protocols](/docs/protocols/), Destination Actions actions are applied **after** [schema filters](/docs/protocols/enforce/schema-configuration/) and [transformations](/docs/protocols/transform/).
3434
- If you are using [Destination Filters](/docs/connections/destinations/destination-filters/), Actions are applied after the filters. They are not applied to data that is filtered out.
35-
- Destination Actions can not be accessed or modified using the Segment APIs yet.
35+
- Destination Actions can't be accessed or modified using the Segment APIs.
3636

3737
## Components of a Destination Action
3838

0 commit comments

Comments
 (0)