Merge branch 'develop' into DOCSPLAT-2993

Author: forstisabella

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

@@ -8,14 +8,13 @@ id: 54521fd525e721e32a72eea2
 Our Clicky destination code is open-source on GitHub. You can check out the code [in the @segment-integrations/analytics.js-integration-clicky](https://github.com/segment-integrations/analytics.js-integration-clicky){:target="_blank"} repository.
 
 
-## Getting Started
+## Getting started
 
 1. From the Segment web app, click **Catalog**.
 2. Search for "Clicky" in the Catalog, select it, and choose which of your sources to connect the destination to.
 3. In the destination settings, enter your Site ID in the settings. You can find your Site ID under the Preferences of your account.
 4. Segment automatically initializes Clicky's script with your Site ID upon loading analytics.js.
 
-
 ## Page
 
 If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like this:
@@ -62,7 +61,6 @@ analytics.track("My Custom Event", {
 
 When you use our [`track`](/docs/connections/spec/track/) method, a goal is created in Clicky. Only the event name and the revenue of the event (if it exists) will be included in the call. Clicky doesn't support any other event properties.
 
-
 ## Troubleshooting
 
 ### My visits aren't showing up in Clicky

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

@@ -5,7 +5,7 @@ id: 55677dfd0a20f4e22f0fb39a
 ---
 This destination is maintained by ClientSuccess.
 
-## Getting Started (for CSMs)
+## Getting started (for CSMs)
 
 If your engineers have already set up Segment, adding Segment data to ClientSuccess is straightforward. All you need to do is turn on the destination.
 
@@ -18,7 +18,7 @@ To turn on the destination, do the following:
 **Note:** Because ClientSuccess focuses on group level events, you must pass group information before your events will show up. If you turn on the ClientSuccess destination in Segment and don't see events in ClientSuccess after 24 hours, it may be that your engineers need to send group information to Segment using Segment's `group` call.
 
 
-## Getting Started (for Developers)
+## Getting started (for developers)
 
 ClientSuccess supports the `identify`, `group`, `track`, and `page` methods of Segment.
 

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

@@ -3,7 +3,7 @@ title: Drip Destination
 id: 54521fd525e721e32a72eeaa
 cmode-override: true
 ---
-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){:target="_blank"},(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){:target="_blank"}, (iOS and Android work using the server destination).
 
 ## Getting Started
 

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

@@ -44,7 +44,7 @@ Segment `identify` trait on the left to the Eloqua field on the right:
 | `title`                          | Title        |
 
 Follow the Segment spec to ensure proper mapping of these fields from Segment
-`identify` traits: /docs/connections/spec/identify/#traits.
+`identify` traits: [/docs/connections/spec/identify/#traits](/docs/connections/spec/identify/#traits).
 
 In addition, Segment supports mapping custom `identify` traits to Eloqua custom
 object fields. To do so, you can set up mappings in the settings for your

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

@@ -18,7 +18,7 @@ analytics.identify('userId123', {
 });
 ```
 
-A `userId` is required on all `identify` calls sent to Evergage. When you call `identify` Segment will call both `setUser` and `setUserField` in the [Evergage library](https://doc.evergage.com/display/EKB/Send+Data+to+Evergage+via+JavaScript){:target="_blank"} to insert both the `userId` and corresponding user traits into {{ integration.name}}.
+A `userId` is required on all `identify` calls sent to Evergage. When you call `identify` Segment will call both `setUser` and `setUserField` in the [Evergage library](https://doc.evergage.com/display/EKB/Send+Data+to+Evergage+via+JavaScript){:target="_blank"} to insert both the `userId` and corresponding user traits into Evergage.
 
 ## Group
 If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like:
@@ -29,7 +29,7 @@ analytics.group('companyId123', {
 });
 ```
 
-A `groupId` is required on all `group` calls sent to Evergage. When you call `group` Segment will call both `setCompany` and `setAccountField` in the [Evergage library](https://doc.evergage.com/display/EKB/Send+Data+to+Evergage+via+JavaScript){:target="_blank"} to insert both the `groupId` and corresponding group traits into {{ integration.name}}.
+A `groupId` is required on all `group` calls sent to Evergage. When you call `group` Segment will call both `setCompany` and `setAccountField` in the [Evergage library](https://doc.evergage.com/display/EKB/Send+Data+to+Evergage+via+JavaScript){:target="_blank"} to insert both the `groupId` and corresponding group traits into Evergage.
 
 ## Track
 If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: