Fixes

Author: lopenchi

src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adobe-swift.md

@@ -44,7 +44,7 @@ You then have the option to pin to a version or specific branch and select which
 
 Open your Package.swift file and add the following to the `dependencies` section:
 
-```
+```swift
 .package(
             name: "Segment",
             url: "https://github.com/segment-integrations/analytics-swift-adobe-analytics.git",
@@ -56,14 +56,14 @@ Open your Package.swift file and add the following to the `dependencies` section
 
 Open the file where you set up and configured the Analytics-Swift library.  Add this plugin to the list of imports.
 
-```
+```swift
 import Segment
 import SegmentAdobe // <-- Add this line
 ```
 
 Just under your Analytics-Swift library setup, call `analytics.add(plugin: ...)` to add an instance of the plugin to the Analytics timeline.
 
-```
+```swift
 let analytics = Analytics(configuration: Configuration(writeKey: "<YOUR WRITE KEY>")
                     .flushAt(3)
                     .trackApplicationLifecycleEvents(true))

src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/mixpanel-swift.md

@@ -82,9 +82,15 @@ The first thing you'll want to do is to identify your users so Mixpanel knows wh
 
 As soon as you have a `userId` for a visitor that was previously anonymous you'll need to [`alias`](/docs/connections/spec/alias/) their old anonymous `id` to the new `userId`. In Mixpanel only **one** anonymous user history can be merged to **one** identified user. For that reason you should only call `alias` once, right after a user registered, but before the first `identify`.
 
- When you call the Identify method from the client in either a browser using Analytics.js or one a mobile SDKs, several things occur: Segment recognizes and translates the [special traits](/docs/connections/spec/identify/#traits) so that they fit the expectations of Mixpanel's API. The table below shows the mappings. Pass the key on the left and Segment transforms it to the key on the right before sending to Mixpanel.
+ When you call the Identify method from the client in either a browser using Analytics.js or one a mobile SDKs, several things occur: 
+ Segment recognizes and translates the [special traits](/docs/connections/spec/identify/#traits) so that they fit the expectations of Mixpanel's API. 
+ The table below shows the mappings. Pass the key on the left and Segment transforms it to the key on the right before sending to Mixpanel.
 
 <table>
+  <tr>
+    <td>Key</td>
+    <td>Segment transformation</td>
+  </tr>
   <tr>
     <td>`created`</td>
     <td>`$created`</td>