cleanup new docs [netlify-build]

alanjcharles · alanjcharles · commit 2a32eb8da19e · 2024-01-23T13:29:19.000-07:00
diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adobe-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adobe-swift.md
@@ -4,9 +4,7 @@ strat: adobe
 redirect_from: '/connections/destinations/catalog/omniture/'
 id: 5783cec280412f644ff14226
 ---
-Once you enable Adobe Analytics (formerly known as Omniture or Sitecatalyst) in Segment, you can start sending data from any of the Segment [libraries](/docs/connections/sources/catalog/) to an Adobe report suite. When you send events from Segment's mobile SDKs or Cloud-mode libraries, Segment translates that data using a mapping that you configure, and then passes it to the Adobe Analytics [Data Insertion API](https://docs.adobe.com/content/help/en/analytics/import/c-data-insertion-api.html){:target="_blank”}.
-
-The following documentation provides detailed explanation of how both destination the Device-mode and Cloud-mode components work. For FAQs about Device- vs Cloud-mode tracking, unique users, identifiers, and more, see the Best Practices page!
+Once you enable Adobe Analytics (formerly known as Omniture or Sitecatalyst) in Segment, you can start sending data from any of the Segment [libraries](/docs/connections/sources/catalog/) to an Adobe report suite. When you send events from Segment's mobile SDKs or Cloud-mode libraries, Segment translates that data using a mapping that you configure, and then passes it to the Adobe Analytics [Data Insertion API](https://docs.adobe.com/content/help/en/analytics/import/c-data-insertion-api.html){:target="_blank”}.The following documentation provides detailed explanation of the Device-mode functionality. 
 
 
 ## Planning for Adobe Analytics
diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/intercom-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/intercom-swift.md
@@ -10,13 +10,8 @@ id: 54521fd725e721e32a72eec6
 2.  Search for "Intercom" and select it in the results that appear.
 3.  Choose which Source to connect Intercom to.
 4.  Authorize your Intercom account in Segment and select the Intercom Account to sync with Segment.
-
-    You can choose which account to sync from the drop down menu in the top right. If you are using [server-side sources](/docs/connections/sources#server), Segment starts passing data through once you activate the Destination. For other libraries  continue reading below.
 5. [Find your "App ID" in the Intercom UI](https://docs.intercom.com/faqs-and-troubleshooting/getting-set-up/where-can-i-find-my-app-id){:target="_blank"} or by navigating to the Gear Menu and clicking on "App Settings" followed by "API Keys". It should look something like `9iefb489`.
 
-Your changes appear in the Segment CDN in about 45 minutes, and then Analytics.js starts asynchronously loading Intercom's `library.js` onto your page.
-
-This means you should remove Intercom's snippet from your page.
 
 ## Adding the dependency
 
diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/localytics-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/localytics-swift.md
@@ -3,12 +3,20 @@ title: Analytics Swift Localytics Plugin
 id: 54521fd925e721e32a72eed0
 ---
 
+Our Analytics-Swift Localytics Destination Plugin is open sourced on GitHub. Feel free to
+[check it out here](https://github.com/segment-integrations/analytics-swift-localytics).
+
 ## Getting Started
 
 The Analytics-Swift Localytics Session Plugin provides session tracking support to your applications via this plugin for [Analytics-Swift](https://github.com/segmentio/analytics-swift)
 
-> success ""
-> This plugin simply adds session data for Localytics, and events are sent via Cloud Mode.
+# Getting Started
+
+1.  From the Segment Destinations page click **Add Destination**.
+2.  Search for `Localytics` and select it in the results that appear.
+3.  Choose which Source to connect `Localytics` to.
+4.  Add your `Localytics` App Key to the Destination setting.
+
 
 ## Adding the dependency
 
@@ -51,3 +59,19 @@ let analytics = Analytics(configuration: Configuration(writeKey: "<YOUR WRITE KE
 analytics.add(plugin: LocalyticsDestination())
 ```
 Your events will now be given Localytics session data and start flowing to Localytics via Cloud Mode.
+
+
+## Identify
+
+When you call [`identify`](/docs/connections/spec/identify/), we'll set the Localytics
+customer Id, and set any special Localytics traits you provide, such as `name`,
+or `email`, and any custom traits as well.
+
+## Track
+
+Whenever you call [`track`](/docs/connections/spec/track/), we'll log an event with
+Localytics. [`track`](/docs/connections/spec/track/) takes the name of the event and any
+optional properties you want to associate with the event.
+
+- - -
+
diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/nielsen-dcr.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/nielsen-dcr.md
@@ -14,9 +14,6 @@ There will be an NDA to sign prior to accessing the download. Nielsen requires y
 
 You must also go through a pre-certification process with your Nielsen representative before shipping this implementation to production.
 
-> success ""
-> This plugin simply adds session data for Nielsen-DCR, and events are sent via Cloud Mode.
-
 ## Adding the dependency
 
 ### via Xcode
@@ -55,4 +52,4 @@ let analytics = Analytics(configuration: Configuration(writeKey: "<YOUR WRITE KE
                     .trackApplicationLifecycleEvents(true))
 analytics.add(plugin: NielsenDCRDestination())
 ```
-Your events will now be given Nielsen-DCR session data and start flowing to Nielsen-DCR via Cloud Mode.
+Your events will now be given Nielsen-DCR session data and start flowing to Nielsen-DCR via Device Mode.
diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/nielsen-dtvr-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/nielsen-dtvr-swift.md
@@ -12,10 +12,7 @@ In order to get started with Nielsen-DTVR and retrieve an `appid` to configure t
 There will be an NDA to sign prior to accessing the download. Nielsen requires you fill out your company info and have a Nielsen representative before getting started.
 
 You must also go through the pre-certification process as outlined here with your Nielsen representative before shipping this implementation to production. The Nielsen-DTVR destination in the Segment dashboard is in private beta. You will need to talk to your Segment customer service representative to get started.
-
-
-> success ""
-> This plugin simply adds session data for Nielsen-DTVR, and events are sent via Cloud Mode.
+ata for Nielsen-DTVR, and events are sent via Cloud Mode.
 
 ### Adding the dependency
 
@@ -58,4 +55,4 @@ analytics.add(plugin: NielsenDTVRDestination())
 ```
 
 
-Your events will now be given Nielsen-DTVR session data and start flowing to Nielsen-DTVR via Cloud Mode.
+Your events will now be given Nielsen-DTVR session data and start flowing to Nielsen-DTVR via Device Mode.
diff --git a/src/connections/sources/catalog/libraries/mobile/kotlin-android/destination-plugins/intercom-kotlin-android.md b/src/connections/sources/catalog/libraries/mobile/kotlin-android/destination-plugins/intercom-kotlin-android.md
@@ -10,12 +10,8 @@ id: 54521fd725e721e32a72eec6
 2.  Search for "Intercom" and select it in the results that appear.
 3.  Choose which Source to connect Intercom to.
 4.  Authorize your Intercom account in Segment and select the Intercom Account to sync with Segment.
-
-    You can choose which account to sync from the drop down menu in the top right. If you are using [server-side sources](/docs/connections/sources#server), Segment starts passing data through once you activate the Destination. For other libraries  continue reading below.
 5. [Find your "App ID" in the Intercom UI](https://docs.intercom.com/faqs-and-troubleshooting/getting-set-up/where-can-i-find-my-app-id){:target="_blank"} or by navigating to the Gear Menu and clicking on "App Settings" followed by "API Keys". It should look something like `9iefb489`.
 
-Your changes appear in the Segment CDN in about 45 minutes, and then Analytics.js starts asynchronously loading Intercom's `library.js` onto your page.
-
 This means you should remove Intercom's snippet from your page.
 
 ## Adding the dependency
@@ -51,9 +47,7 @@ Just under your Analytics-Kotlin library setup, call `analytics.add(plugin = ...
     analytics.add(plugin = IntercomDestination(applicationContext))
 ```
 
-Your events will now begin to flow to Intercom in device mode.
-
-
+Your events will now begin to flow to Intercom in Device mode.
 
 ## Identify
 
diff --git a/src/connections/sources/catalog/libraries/mobile/kotlin-android/destination-plugins/localytics-kotlin-android.md b/src/connections/sources/catalog/libraries/mobile/kotlin-android/destination-plugins/localytics-kotlin-android.md
@@ -7,6 +7,12 @@ Our Analytics-Kotlin Localytics Destination Plugin is open sourced on GitHub. Fe
 
 ## Getting Started
 
+1.  From the Segment Destinations page click **Add Destination**.
+2.  Search for `Localytics` and select it in the results that appear.
+3.  Choose which Source to connect `Localytics` to.
+4.  Add your `Localytics` App Key to the Destination setting.
+
+
 Once the Segment library is integrated with your site or app, toggle Localytics
 on in your Segment destinations, and add your application's **App Key** which
 you can find in your Localytics app settings. These new settings will take up to
@@ -76,7 +82,7 @@ Just under your Analytics-Kotlin library setup, call `analytics.add(plugin = ...
     analytics.add(plugin = LocalyticsDestination())
 ```
 
-Your events will now begin to flow to Localytics in device mode.
+Your events will now begin to flow to Localytics in Device Mode.
 
 
 ## Identify
