Merge pull request #6967 from segmentio/dineshraj-arunmozhi-patch-1

pwseg · web-flow · commit 6cbfb87da1f7 · 2024-08-22T12:32:22.000-04:00
Update Engage FAQs Typo
diff --git a/src/engage/faqs.md b/src/engage/faqs.md
@@ -12,7 +12,7 @@ Yes. You can learn more about the Audience API by visiting the [Segment Public A
 
 ## Can I programmatically determine if a user belongs to a particular audience?
 
-Yes. Eecause Engage creates a trait with the same name as your audience, you can query the Profile API to determine if a user belongs to a particular audience. For example, to determine if the user with an email address of `bob@example.com` is a member of your `high_value_users` audience, you could query the following Profile API URL:
+Yes. Because Engage creates a trait with the same name as your audience, you can query the Profile API to determine if a user belongs to a particular audience. For example, to determine if the user with an email address of `bob@example.com` is a member of your `high_value_users` audience, you could query the following Profile API URL:
 
 ```
 https://profiles.segment.com/v1/namespaces/<namespace_id>/collections/users/profiles/email:bob@segment.com/traits?include=high_value_users
@@ -150,4 +150,4 @@ Based on Engage behavior, standard source events such as Page, Track and Identif
 
 ## Why can't I connect the audience/computed trait to an existing destination in my workspace?
 
-Engage will not allow you to connect an audience/computed trait to a destination that is already linked to a [Connections-based source](https://segment.com/docs/connections/sources/). Instead, create a new instance of the destination with the correct Engage space selected as the data source.
+Engage will not allow you to connect an audience/computed trait to a destination that is already linked to a [Connections-based source](/docs/connections/sources/). Instead, create a new instance of the destination with the correct Engage space selected as the data source.

-Original file line number
+Diff line change
 ## Can I programmatically determine if a user belongs to a particular audience?
 -Yes. Eecause Engage creates a trait with the same name as your audience, you can query the Profile API to determine if a user belongs to a particular audience. For example, to determine if the user with an email address of `[email protected]` is a member of your `high_value_users` audience, you could query the following Profile API URL:
 +Yes. Because Engage creates a trait with the same name as your audience, you can query the Profile API to determine if a user belongs to a particular audience. For example, to determine if the user with an email address of `[email protected]` is a member of your `high_value_users` audience, you could query the following Profile API URL:
 ```
 https://profiles.segment.com/v1/namespaces/<namespace_id>/collections/users/profiles/email:[email protected]/traits?include=high_value_users
 ## Why can't I connect the audience/computed trait to an existing destination in my workspace?
 -Engage will not allow you to connect an audience/computed trait to a destination that is already linked to a [Connections-based source](https://segment.com/docs/connections/sources/). Instead, create a new instance of the destination with the correct Engage space selected as the data source.
 +Engage will not allow you to connect an audience/computed trait to a destination that is already linked to a [Connections-based source](/docs/connections/sources/). Instead, create a new instance of the destination with the correct Engage space selected as the data source.