Override the Drip destination connection modes (#2813)

Author: markzegarelli

src/_data/catalog/overrides.yml

@@ -1,6 +1,18 @@
 # This file is manually generated. When you add or remove an item, add or remove
 # it from the `overrides-list.yml` too.
 items:
+- slug: drip
+  id: 54521fd525e721e32a72eeaa
+  connection_modes:
+    device:
+      web: true
+      mobile: true
+      server: false
+    cloud:
+      web: false
+      mobile: true
+      server: true
+
 - slug: clevertap
   id: 5711271880412f644ff13150
   connection_modes:

src/connections/destinations/catalog/drip/index.md

@@ -1,8 +1,9 @@
 ---
 title: Drip Destination
 id: 54521fd525e721e32a72eeaa
+cmode-override: true
 ---
-Our Drip destination code is all open-source on GitHub if you want to check it out: [Javascript](https://github.com/segment-integrations/analytics.js-integration-drip),(iOS and Android work using the server destination).
+The Drip destination code is all open-source on GitHub if you want to check it out: [Javascript](https://github.com/segment-integrations/analytics.js-integration-drip),(iOS and Android work using the server destination).
 
 ## Getting Started
 
@@ -11,11 +12,11 @@ When you enable Drip in the Segment web app, your changes appear in the Segment
 
 ## Identify
 
-When you call [`identify`](/docs/connections/spec/identify/) on analytics.js, we call [`identify`](/docs/connections/spec/identify/) on Drip and pass through all of the user traits that were included on that call. You must pass email as a trait to identify the user to Drip. Note that if you want to do cross-domain tracking, after you've enabled it in the Drip UI, you'll need to pass `email` as a trait on the identify call on both domains.
+When you call [`identify`](/docs/connections/spec/identify/) on analytics.js, Segment calls [`identify`](/docs/connections/spec/identify/) on Drip and passes through all of the user traits that were included on that call. You must pass email as a trait to identify the user to Drip. Note that if you want to do cross-domain tracking, after you've enabled it in the Drip UI, you'll need to pass `email` as a trait on the identify call on both domains.
 
 ## Track
 
-When you call [`track`](/docs/connections/spec/track/), we'll send the event to Drip with the event `name` and all `properties` that you specified. If you include `revenue` as a property, it will get passed to Drip as the conversion value of this event.
+When you call [`track`](/docs/connections/spec/track/), Segment sends the event to Drip with the event `name` and all `properties` that you specified. If you include `revenue` as a property, it will get passed to Drip as the conversion value of this event.
 
 **Note:**
 - If you are sending custom server side events, you must include an `email` property of the user that the event belongs to.