Merge pull request #8050 from lopenchi/DOCSPLAT-2993

[DOCSPLAT-2993] Modifications for serialization

Author: forstisabella

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

@@ -11,7 +11,6 @@ When you enable Chartbeat in the Segment web app, your changes appear in the Seg
 
 Chartbeat is only supported on the client-side.
 
-- - -
 
 
 ## Page

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

@@ -8,7 +8,7 @@ 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.

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.
 
@@ -17,7 +17,8 @@ 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/cubitic/index.md

@@ -12,7 +12,6 @@ The Cubitic application key can be obtained by contacting signup@cubitic.io
 
 Cubitic supports the `identify` and `track` methods.
 
-- - -
 
 ## Identify
 

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

@@ -17,7 +17,6 @@ To get started with Cxense and Segment, you'll need the following:
 
 Assuming these criteria are met, you can add Cxense as a destination for your desired source in your Segment account.
 
-- - -
 
 ## Page
 

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

@@ -44,7 +44,7 @@ buildscript {
 apply plugin: 'com.google.gms.google-services'
 ```
 
-> warning "Use the `aar` package when adding the Segment-Firebase SDK"
+> warning "Use the aar package when adding the Segment-Firebase SDK"
 > The Firebase SDK requires Android resources which are available on `aar` packages.
 
 

src/connections/destinations/catalog/framed-io/index.md

@@ -8,7 +8,6 @@ Once your application is set up and instrumented with Segment, turn on Framed in
 
 Framed supports the `identify` and `track` methods.
 
-- - -
 
 ## Identify
 

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

@@ -19,7 +19,7 @@ You can use `identify` to create a lead or a contact when a website visitor fill
 ### User ID
 `userId` is a mandatory field which is used to identify the lead or contact in Freshsales. If your user identifier is not email, then email has to be a part of traits.
 
-<pre>
+```json
 {
   "userId": "97980cfea0067",
   "traits": {
@@ -32,11 +32,11 @@ You can use `identify` to create a lead or a contact when a website visitor fill
     }
   }
 }
-</pre>
+```
 
 By default, every `identity` is created as a lead. If you'd like an identity to be a contact, you'd need to pass `fs_contact` as `true` as a part of traits.
 
-<pre>
+```json
 {
   "userId" : "97980cfea0067",
   "traits" : {
@@ -50,7 +50,7 @@ By default, every `identity` is created as a lead. If you'd like an identity to
     }
   }
 }
-</pre>
+```
 
 ### Traits
 `traits` are pieces of information you know about a user that are included in an `identify` method.
@@ -72,7 +72,7 @@ As part of traits, you can send custom fields created in Freshsales by using the
 ### Objects:
 Accounts and Deals associated to a contact or lead can also be updated in Freshsales. The objects company and deal in the identity correspond to the Accounts and Deals in Freshsales. You can pass the `traits` of the company or the deal along with the respective objects in the identity.
 
-```
+```json
 {
   "userId" : "97980cfea0067",
   "traits" : {
@@ -98,7 +98,7 @@ You can track activities of your website visitors. If a user is subscribing to a
 ### Track request payload
 
 
-```
+```json
 {
   "userId" : "john.doe@example.com",
   "event": "Email Bounced",
@@ -120,7 +120,7 @@ When you call a `page` event, we send a pageview to Freshsales. You can send ext
 
 ### Sample Page request payload
 
-```
+```json
 {
   "userId" : "john.doe@example.com",
   "name": "Page view",

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

@@ -39,7 +39,7 @@ analytics.identify("userId");
 
 In addition, Segment will send over along any traits included in the `identify` call. The example call below would send over both `plan` and `logins`.
 
-```
+```js
 analytics.identify("userId123", {
   plan: "premium",
   logins: 5
@@ -50,7 +50,7 @@ analytics.identify("userId123", {
 
 Both `email` and `displayName` are special traits that will be passed to FullStory to be used in their interface as explained in [FullStory's docs](https://help.fullstory.com/hc/en-us/articles/360020828113){:target="_blank"}. These traits are optional.
 
-```
+```js
 analytics.identify("userId123", {
   email: "john.doe@example.com",
   displayName: "John Doe"
@@ -63,7 +63,7 @@ If you're not familiar with the Segment Specs, take a look to understand what th
 
 An example call would look like:
 
-```
+```js
 analytics.track('Product Purchased', {
     order_ID: '2969302398',
     category: 'boots',

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

@@ -10,14 +10,12 @@ This means you should remove Gauges' snippet from your page.
 
 Gauges starts automatically collecting data on your site.
 
-- - -
 
 
 ## Page
 
 When you call [`page`](/docs/connections/spec/page/), we call Gauges' `track` method with no arguments.
 
-- - -
 
 
 ## Troubleshooting