relative link fix

pwseg · web-flow · commit 51afaf3f6034 · 2024-08-22T12:31:02.000-04:00
diff --git a/src/engage/faqs.md b/src/engage/faqs.md
@@ -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 number	Diff line change
`@@ -150,4 +150,4 @@ Based on Engage behavior, standard source events such as Page, Track and Identif`
`150`	`150`
`151`	`151`	`## Why can't I connect the audience/computed trait to an existing destination in my workspace?`
`152`	`152`
`153`		`-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.`
	`153`	`+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.`