chore: Modify to simplify migration

Author: CristhianMotoche

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

@@ -81,8 +81,6 @@ analytics.screen({
 })
 ```
 
-- - -
-
 ## Troubleshooting
 
 ### Property values have maximum length of 255 characters

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

@@ -48,11 +48,11 @@ analytics.track('Login Button Clicked')
 Send [Group](/docs/connections/spec/group) calls to tie a user to an org. There are two IDs that are relevant in a group call: the userId, which belongs and refers to the user, and the groupId, which belongs and refers to the specific group.  A user can belong to multiple groups, each associated with a different groupId, but the user will have only one userId linked to each of these different groups.
 
 ```js
- analytics.group("0e8c78ea9d97a7b8185e8632", {
-name: "Initech",
-industry: "Technology",
-employees: 329,
-plan: "enterprise",
-"total billed": 830
+analytics.group("0e8c78ea9d97a7b8185e8632", {
+  name: "Initech",
+  industry: "Technology",
+  employees: 329,
+  plan: "enterprise",
+  "total billed": 830
 });
-```
+```

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

@@ -103,5 +103,13 @@ All other fields are then added to the user's profile as custom fields within In
 
 Segment sends Identify calls to Inkit as an `identify` event.
 
-
-SELECT COUNT(*) FROM destination_config WHERE destination_id = '54521fd525e721e32a72ee8f' AND enabled = 1 AND id IN (SELECT config_id FROM destination_config_options_2 WHERE option_name = 'canOmitAppsFlyerId' AND value = 'false')
+```sql
+SELECT COUNT(*)
+FROM   destination_config
+WHERE  destination_id = '54521fd525e721e32a72ee8f'
+       AND enabled = 1
+       AND id IN (SELECT config_id
+                  FROM   destination_config_options_2
+                  WHERE  option_name = 'canOmitAppsFlyerId'
+                         AND value = 'false')
+```

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

@@ -55,7 +55,7 @@ analytics.track({
 
 The Segment Track event above would be transformed and transmitted to Kable as:
 
-```curl
+```bash
 curl --request POST \
      --url https://live.kable.io/api/v1/events/create \
      --header 'Accept: application/json' \

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

@@ -43,8 +43,6 @@ Whenever you call [`track`](/docs/connections/spec/track/), we'll log an event w
 Localytics. [`track`](/docs/connections/spec/track/) takes the name of the event and any
 optional properties you want to associate with the event.
 
-- - -
-
 ## Push Notifications
 
 Push notifications on Android require a bit of extra work to setup.

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

@@ -7,7 +7,7 @@ id: 54521fd925e721e32a72eed2
 
 1. Lytics uses Segment's JavaScript library so make sure to [go through our quickstart guide to get set up on that first](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/).
 
-2) Once you're recording data enable Lytics on your destination page using your Customer ID number, which can be found in the admin section of your Lytics account: **Account** -> **Manage Accounts**.
+2. Once you're recording data enable Lytics on your destination page using your Customer ID number, which can be found in the admin section of your Lytics account: **Account** -> **Manage Accounts**.
 
 ![cid](https://lyticspublic.s3.amazonaws.com/images/Segment.io/segment_cid.png)
 

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

@@ -134,7 +134,7 @@ Again, this will **NOT** work for new users. New users will always have their su
 Mailchimp doesn't support arrays as traits values. This can cause calls to not show up.
 
 #### Why am I seeing a `400 Bad Request` error?
-A **400 Bad Request** error can occur if the email address contains a misspelled domain name. For example, Mailchimp might reject`"joe@gmil.com"` because "gmail" is misspelled.
+A **400 Bad Request** error can occur if the email address contains a misspelled domain name. For example, Mailchimp might reject `"joe@gmil.com"` because "gmail" is misspelled.
 
 #### Why am I seeing frequent `404 Bad Request` errors from Identify events with no error message?