chore: Update some docs to improve the result on migration

Author: CristhianMotoche

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

@@ -84,7 +84,7 @@ Collections are the groupings of resources Segment pulls from your source. In yo
 | segments                 | A list of segments associated with the user                                                                                                          |
 | tags                     | A list of tags associated with the user                                                                                                              |
 | last_seen_ip             | An ip address (e.g. "1.2.3.4") representing the last ip address the user visited your application from. (Used for updating location_data)            |
-| user_agent_data          | Data about the last user agent the user was seen using. To update this value use `last\_seen\_user\_agent`                                           |
+| user_agent_data          | Data about the last user agent the user was seen using. To update this value use `last_seen_user_agent`                                              |
 | custom_attributes        | The custom attributes you have set on the user (case sensitive)                                                                                      |
 
 ## Companies
@@ -120,7 +120,7 @@ Collections are the groupings of resources Segment pulls from your source. In yo
 | unsuscribed_from_emails | Whether the Lead is unsubscribed from emails                                                                                                 |
 | location_data           | A Location Object relating to the Lead. To update location_data use `last_seen_ip` which will be translated to the appropriate location_data |
 | last_seen_ip            | An ip address (e.g. "1.2.3.4") representing the last ip address the user visited your application from. (Used for updating location_data)    |
-| user_agent_data         | Data about the last user agent the user was seen using. To update this value use `last\_seen\_user\_agent`                                   |
+| user_agent_data         | Data about the last user agent the user was seen using. To update this value use `last_seen_user_agent`                                      |
 | companies               | A list of companies for the user                                                                                                             |
 | avatar                  | An avatar object for the Lead                                                                                                                |
 

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
-  a. If you don't already have a REST service setup, follow [these steps](http://developers.marketo.com/rest-api/custom-services/){:target="_blank"}.
-  b. Then, copy the "Client ID" and "Client Secret" parameters.
+  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)
-  c. Paste the "Client ID" and "Client Secret" into the Segment Marketo source settings.
+  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.
 

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

@@ -20,7 +20,7 @@ Qualtrics maintains this source. For any issues with the source, [contact the Qu
 4. Click **Add Source** to save your settings.
 5. Log in to your Qualtrics Account. Navigate to Workflows, select a workflow to send Segment events from, and add a new Segment task.
 6. From within the Segment task, after connecting with your Segment workspace API token, select your Qualtrics source and continue to set up the task with the event, data mapping, and more.
-- Your workspace token will need Source Admin permissions, at a minimum.
+   - Your workspace token will need Source Admin permissions, at a minimum.
 7. For more information on the Qualtrics Segment task, view the [Qualtrics support page](https://www.qualtrics.com/support/integrations/twilio-segment/twilio-segment-task/){:target="_blank"}.
 
 ## Stream

src/connections/sources/catalog/cloud-apps/quin-ai/index.md

@@ -12,7 +12,7 @@ This source is maintained by Quin Audience Engine. For any issues with the sourc
 1. From your workspace's Source page, click **Add Source**.
 2. Search for "Quin AI" in the Sources Catalog, select Quin AI, and click **Add Source**.
 3. On the next screen, give the Source a name configure any other settings.
-  - The name is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The name can be anything, but Segment recommends using something that reflects the source itself and distinguishes amongst your environments (eg. QuinAI_Prod, QuinAI_Staging, QuinAI_Dev).
+    - The name is used as a label in the Segment app, and Segment creates a related schema name in your warehouse. The name can be anything, but Segment recommends using something that reflects the source itself and distinguishes amongst your environments (eg. QuinAI_Prod, QuinAI_Staging, QuinAI_Dev).
 4. Click **Add Source** to save your settings.
 5. Copy the Write key from the Segment UI.
 6. 6. Log in to your [Quin account](https://portal.quinengine.com/){:target="_blank”} and navigate to **Integrations > Segment > Settings**.