Fixes

Author: lopenchi

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

@@ -34,19 +34,20 @@ Identify calls that do not have a User ID value will not be sent to Hotjar.
 
 Currently, the Hotjar Identify API **does not** support ingesting values passed as nested objects or lists over your identify Spec:
 
-```js
+```json
 "traits": {
-    "name": "Peter Gibbons",
-    "email": "peter@example.com",
-    "plan": "premium",
-    "logins": 5,
-    "address": {
-      "street": "6th St",
-      "city": "San Francisco",
-      "state": "CA",
-      "postalCode": "94103",
-      "country": "USA"
-    }
+  "name": "Peter Gibbons",
+  "email": "peter@example.com",
+  "plan": "premium",
+  "logins": 5,
+  "address": {
+    "street": "6th St",
+    "city": "San Francisco",
+    "state": "CA",
+    "postalCode": "94103",
+    "country": "USA"
+  }
+}
 ```
 
 In the example above, Hotjar rejects all the values in the `address` field.
@@ -62,8 +63,8 @@ Currently, the Hotjar Events API **does not** support ingesting event properties
 ```js
 analytics.track("Experiment Viewed", {
   experiment_id: "1234",
-  experiment_name: "new_upsell_UX"
-  variation_id: "1234b"
+  experiment_name: "new_upsell_UX",
+  variation_id: "1234b",
   variation_name: "variant"
 });
 ```

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

@@ -23,7 +23,7 @@ If you would like to use `track` event data, create a `Segment Product Usage Sca
 
 If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like:
 
-```
+```js
 analytics.identify('userId123', {
   email: 'john.doe@example.com',
   firstName: 'John',
@@ -45,7 +45,7 @@ Identify calls will be sent to Hydra as an `identify` event. Upon receiving an I
 
 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:
 
-```
+```js
 analytics.track('Device deploy started',
   "properties": {
     "feature": "Device management",

src/connections/sources/catalog/cloud-apps/marketo/index.md

@@ -36,10 +36,10 @@ You will need Admin permissions to your Marketo account.
 2. Go to **Admin > Munchkin** to find your Munchkin Account ID.
 ![Screenshot of the Tracking Code section of Marketo's Munchkin page.](images/Image2018-04-30at5.28.54PM.png)
 3. Go to Admin > LaunchPoint
-  1. If you don't already have a REST service setup, follow [these steps](http://developers.marketo.com/rest-api/custom-services/){:target="_blank"}.
-  2. Then, copy the "Client ID" and "Client Secret" parameters.
-  ![Screenshot of the Details section of the LaunchPoint page.](images/Image2018-04-30at5.29.32PM.png)
-  3. Paste the "Client ID" and "Client Secret" into the Segment Marketo source settings.
+   1. If you don't already have a REST service setup, follow [these steps](http://developers.marketo.com/rest-api/custom-services/){:target="_blank"}.
+   2. Then, copy the "Client ID" and "Client Secret" parameters.
+   ![Screenshot of the Details section of the LaunchPoint page.](images/Image2018-04-30at5.29.32PM.png)
+   3. Paste the "Client ID" and "Client Secret" into the Segment Marketo source settings.
 
 Data should start flowing into your warehouse in the next few hours.