From e7c80563d4a7945300c42a40d929816f40063e6d Mon Sep 17 00:00:00 2001
From: markzegarelli <mark.zegarelli@segment.com>
Date: Tue, 12 Oct 2021 11:41:12 -0700
Subject: [PATCH 1/2] DOC-337 Add content about dest functions

---
 .../functions/destination-functions.md           | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/src/connections/functions/destination-functions.md b/src/connections/functions/destination-functions.md
index 5e18974251..59281e233a 100644
--- a/src/connections/functions/destination-functions.md
+++ b/src/connections/functions/destination-functions.md
@@ -408,7 +408,21 @@ If any of your deployed function instances are failing consistently, they will a
 
 ### Data control
 
-You can use [Destination Filters](/docs/connections/destinations/destination-filters/) or [Privacy Portal](/docs/privacy/portal/) to manage what events and, of those events, which event properties are sent to your destination function.
+In addition to [Destination Filters](/docs/connections/destinations/destination-filters/) and [Privacy Portal](/docs/privacy/portal/) to manage which events and properties are sent to your destination function, you can reference the destination function directly in the integrations object of the Segment payload. For example:
+
+```json
+...
+"integrations": {
+  "All": false,
+  "Amplitude": true,
+  "Customer.io": true,
+  "Google Analytics": true,
+  "My Destination Function (My Workspace)": true
+}
+...
+```
+
+In the example above, the integrations object directly references and enables the `My Destination Function`. Be sure to include the workspace name in which the Destination Function is created, as shown. Like all items in the integration object, Destination Functions (and workspace names) are case sensitive. 
 
 ## Destination functions FAQs
 

From f8b838f913d308640f287a3311ea7ebe48dd1beb Mon Sep 17 00:00:00 2001
From: markzegarelli <mark.zegarelli@segment.com>
Date: Tue, 12 Oct 2021 14:42:46 -0700
Subject: [PATCH 2/2] Update src/connections/functions/destination-functions.md

Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
---
 src/connections/functions/destination-functions.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/connections/functions/destination-functions.md b/src/connections/functions/destination-functions.md
index 59281e233a..f392178231 100644
--- a/src/connections/functions/destination-functions.md
+++ b/src/connections/functions/destination-functions.md
@@ -408,7 +408,7 @@ If any of your deployed function instances are failing consistently, they will a
 
 ### Data control
 
-In addition to [Destination Filters](/docs/connections/destinations/destination-filters/) and [Privacy Portal](/docs/privacy/portal/) to manage which events and properties are sent to your destination function, you can reference the destination function directly in the integrations object of the Segment payload. For example:
+In addition to using [Destination Filters](/docs/connections/destinations/destination-filters/) and the [Privacy Portal](/docs/privacy/portal/) to manage which events and properties are sent to your destination function, you can reference the destination function directly in the integrations object of the Segment payload. For example:
 
 ```json
 ...