Update src/engage/audiences/send-audience-data.md

Co-authored-by: forstisabella <[email protected]>

Author: pwseg

src/engage/audiences/send-audience-data.md

@@ -14,7 +14,7 @@ Segment's Connections pipeline first collects and sends events from your source
 
 Once you've previewed your audience, you can choose to connect it to a destination or keep the audience in Segment and export it as a CSV file download.
 
-When you create an audience, Segment starts syncing your audience to the destinations you selected. Audiences are either sent to destinations as a boolean user-property or a user-list, depending on what the destination supports. Read more about [supported Destinations](/docs/engage/using-engage-data/#compatible-engage-destinations) in the Engage documentation.
+When you create an audience, Segment starts syncing your audience to the destinations you selected. Audiences are either sent to destinations as a boolean user-property or a user-list, depending on what the destination supports. Read more about [supported destinations](/docs/engage/using-engage-data/#compatible-engage-destinations) in the Engage documentation.
 
 For account-level audiences, you can send either a [Group](/docs/connections/spec/group) call and/or [Identify](/docs/connections/spec/identify) call. Group calls will send one event per account, whereas Identify calls will send an Identify call for each user in the account. This means that even if a user hasn't performed an event, Segment will still set the account-level computed trait on that user.