chore: fixes for serialization of batch 6.3

Author: carlota-moh

src/connections/destinations/catalog/urban-airship/index.md

@@ -29,6 +29,7 @@ or setting up automation rules.
 
 1) Include the Urban Airship dependency in the project's build.gradle file:
 
+```json
     repositories {
        ...
 
@@ -44,11 +45,11 @@ or setting up automation rules.
        // Urban Airship SDK
        compile 'com.urbanairship.android:segment-integration:1.0.+'
     }
-
+```
 
 2) Verify the `applicationId` is set in the project's build.gradle file:
 
-
+```json
     android {
        ...
 
@@ -58,57 +59,65 @@ or setting up automation rules.
           applicationId "com.example.application"
        }
     }
-
+```
 
 3) Add the Urban Airship Destination factory:
 
+```java
     Analytics analytics = new Analytics.Builder(context, writeKey)
        .use(UrbanAirshipIntegration.FACTORY)
        ...
        .build();
+```
 
 
 ### Enabling user notifications
 
 Once the Urban Airship destination is ready, you can enable user notifications with the following:
 
+```java
     analytics.onIntegrationReady(UrbanAirshipIntegration.URBAN_AIRSHIP_KEY, new Analytics.Callback<Object>() {
           @Override
           public void onReady(Object instance) {
              UAirship airship = (UAirship) instance;
              airship.getPushManager().setUserNotificationsEnabled(true);
           }
        });
-
+```
 
 ## iOS
 
 ### Setup
 
 1) Add the Urban Airship Segment Destination pod to your project's Podfile:
 
+```objc
     pod "UrbanAirship-iOS-Segment-Integration"
-
+```
 
 2) Use the Urban Airship Destination:
 
+```objc
     SEGAnalyticsConfiguration *config = [SEGAnalyticsConfiguration configurationWithWriteKey:@"YOUR_WRITE_KEY"];
 
     [config use:[SEGUrbanAirshipIntegrationFactory instance]];
 
     [SEGAnalytics setupWithConfiguration:config];
-
+``` 
 
 ### Enabling user notifications
 
 Once the Urban Airship destination is ready, you can enable user notifications with the following:
 
+```objc
     [UAirship push].userPushNotificationsEnabled = YES;
-
+```
 
 To listen for when the Urban Airship destination is ready, listen for the `SEGAnalyticsIntegrationDidStart` event in `NSNotificationCenter`:
 
+```objc
     [[[NSNotificationCenter defaultCenter] addObserver:self
                                               selector:@selector(airshipReady)
                                                   name:@"io.segment.analytics.integration.did.start"
                                                 object:[SEGUrbanAirshipIntegrationFactory instance].key];
+```

src/connections/destinations/catalog/user-com/index.md

@@ -52,7 +52,7 @@ Sending a `.group()` request allows to create or update a company profile and as
 
 The user that owns the `userId` on this event will be associated with this company.
 
-Any custom traits of the `.group()` call will follow same logic as `Identify` method. Semantic traits that are mapped are: `address`, `description`, `email`, `employees`, `name`, `phone`. **NOTE**: to make sure types of custom traits defined in database reflect your expectations, visit **App settings > Companies > Company attributes** at [app.user.com](https://user.com/en{:target="_blank"}
+Any custom traits of the `.group()` call will follow same logic as `Identify` method. Semantic traits that are mapped are: `address`, `description`, `email`, `employees`, `name`, `phone`. **NOTE**: to make sure types of custom traits defined in database reflect your expectations, visit **App settings > Companies > Company attributes** at [app.user.com](https://user.com/en){:target="_blank"}
 
 ## Troubleshooting
 

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

@@ -98,8 +98,6 @@ In an account, events can have at most 25 attributes of each data type type (i.e
 
 The `reset` call must be invoked when a user is logged out.
 
-- - -
-
 ## Features
 
 ### Push Notifications

src/connections/destinations/catalog/whale-alerts/index.md

@@ -28,15 +28,17 @@ This is an introduction to how Segment and Whalr work together and how to get Wh
 
 The first step is to send Whalr your customer's email addresses using the Segment IDENTIFY call.  You should send this the first time a lead is identified with an email address, and  every time a user logs in after that.  This is sent as a JSON message in the standard Segment format, and the minimum information required is:
 
-	{
-	  "type" : "identify",
+```json
+{
+  "type": "identify",
 
-	  "userId" : [however you identify your customer],
+  "userId": [however you identify your customer],
 
-	  "traits" : {
-			    "email" : [email address]
-				  }
-	}
+  "traits": {
+    "email": [email address]
+  }
+}
+```
 
 As Segment notes, using the email address as a unique identifier is not a good idea because emails change, people have multiple email addresses, etc.  However, if that's how you're set up, Whalr supports it, you just need to supply the email address twice: once as the userID and once as the email address.
 
@@ -48,7 +50,9 @@ In addition, studies show a negative correlation between the number fields and t
 
 As noted above, by default Segment sends a PAGE event every time a customer visits a page.   You can also create custom messages using the TRACK method.   You can track any event you are interested in, such as signing up to a newsletter or responding to a campaign.  For example, you might add the following JavaScript code to an email signup form on your website:
 
-	analytics.track("email signup")
+```js
+analytics.track("email signup")
+```
 
 Segment adds a host of information, such as userId, IP address, location, browser type, UTM tracking codes, etc. Whalr then adds its own contextual information, such as how often a person visits, how big the company he works for is, etc.  The more detail Whalr has, the better our machine learning algorithms can learn the contextual clues that reflect buying behaviour, and notify you which customers are exhibiting this behavior.  Whalr analyzes profiles, events, engagement (by individuals and groups), and many other metrics to predict which customers will buy based on matching their behavior to past buying behaviors observed. Just as Netflix can recommend a movie with 90% confidence, Whalr can tell you a customer will convert with 90% probability. Stop wasting your time trying to chase every contact, or ignoring valuable contacts just because they signed up with a gmail address!  Whalr isn't analytics, it's customer-specific, and it empowers your sales team to do what they do best--sell!
 

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

@@ -11,8 +11,8 @@ The [Wishpond JavaScript (browser) Integration](https://github.com/wishpond-dev/
 Wishpond works with Segment's client-side JavaScript library: Analytics.js.
 
 
-1.  From your Segment UI's Destinations page click on "Add Destination".
-2.  Search for "Wishpond" in the Catalog, select it, and choose which of your sources to connect the destination to.
+1. From your Segment UI's Destinations page click on "Add Destination".
+2. Search for "Wishpond" in the Catalog, select it, and choose which of your sources to connect the destination to.
 3. In the destination settings, enter your Merchant ID and Trackey Key from Wishpond's ["API Keys" dialog](https://www.wishpond.com/central/welcome?api_keys=true){:target="_blank"}. These are also found in your Wishpond Account in the "API Keys" dropdown under your account name in the top right corner.
 4. Segment automatically initializes Wishpond's Tracking Code with your Tracking Key and Merchant ID when it next loads Analytics.js.
 
@@ -69,7 +69,6 @@ A new event will be added to the lead that the current session is tracking. The
 
 To more details how Wishpond's identify works  visit [Wishpond API Docs: #track](http://developers.wishpond.com/#tracking-events){:target="_blank"}.
 
-- - -
 ## Troubleshooting/ FAQ
 
 ### Destination is not working properly

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

@@ -1,7 +1,7 @@
 ---
 title: Worthy Destination
 rewrite: true
----​
+---
 
 [Worthy.ai](https://worthy.ai){:target="_blank"} helps advertisers improve their marketing efficiency through using predictive analytics and signal testing.
 

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

@@ -2,7 +2,7 @@
 title: Youbora Destination
 id: 59c04bd6432df886f42eea37
 ---
-### Web Destination
+## Web Destination
 
 When you enable Youbora in the Segment web app, your changes appear in the Segment CDN in about 45 minutes, and then Analytics.js starts asynchronously loading Youbora's JavaScript onto your page. (This means you should remove Youbora's snippet from your page.)