Merge pull request #1176 from segmentio/fix-procols

fix protocols overview buttons and ios 14 links

Author: markzegarelli

src/_includes/components/media-thumbnail.html

@@ -1,5 +1,5 @@
 <div class="media-thumbnail">
-  <a class="media-thumbnail__inner flex flex--stack flex--queue@xlarge waffle waffle--large" href="{{ include.href }}">
+  <a class="media-thumbnail__inner flex flex--stack flex--queue@xlarge waffle waffle--large" href="{{ site.baseurl }}{{ include.href }}">
     {% if include.icon %}
       <span class="flex__column flex__column--shrink">
         <span class="media-thumbnail__icon">

src/connections/sources/catalog/libraries/mobile/ios/ios14-guide.md

@@ -24,7 +24,7 @@ Due to this major change, **you should upgrade to the latest stable version of `
 ## You can manually pass the IDFA to the Segment SDK.
 
 
-If you need to collect the user’s IDFA to pass it to specific destinations, or for other uses, you can follow the steps for Ad Tracking and IDFA in the [iOS documentation](/docs/connections/sources/catalog/libraries/mobile/ios/#ad-tracking-and-idfa) to collect and pass IDFA as a configuration item to the Segment SDK.
+If you need to collect the user’s IDFA to pass it to specific destinations, or for other uses, you can follow the steps for Ad Tracking and IDFA in the [iOS documentation](/docs/connections/sources/catalog/libraries/mobile/ios#ad-tracking-and-idfa) to collect and pass IDFA as a configuration item to the Segment SDK.
 
 Remember, under iOS14, applications can only collect the IDFA from a user if they consent to make it available. The Segment example code, used along with Apple’s documentation, make it easy for developers to collect and pass the IDFA to the Segment SDK as a configuration item on app load.
 

src/connections/sources/catalog/libraries/mobile/ios/troubleshooting.md

@@ -22,11 +22,11 @@ This was due to an old [CocoaPods limitation](https://github.com/CocoaPods/Cocoa
 
 ## No events in my debugger
 
-1. Verify you have followed all [Getting Started](/docs/connections/sources/catalog/libraries/mobile/ios/#getting-started) steps
+1. Verify you have followed all [Getting Started](/docs/connections/sources/catalog/libraries/mobile/ios#getting-started) steps
 2. Verify you have entered the correct writeKey for your source
     - If the writeKey you have entered is something other than a string or an empty string your app may crash
     - If the writeKey you have entered is a valid form but not the correct writeKey for your specific source, you will not see an error response. Data will be accepted by Segment but not able to be correctly routed to your source (debugger).
-3. [Enable logging](/docs/connections/sources/catalog/libraries/mobile/ios/#logging) to confirm if call is being sent to Segment
+3. [Enable logging](/docs/connections/sources/catalog/libraries/mobile/ios#logging) to confirm if call is being sent to Segment
 
 
 ## No events in my destinations
@@ -43,7 +43,7 @@ This was due to an old [CocoaPods limitation](https://github.com/CocoaPods/Cocoa
 
 If you are using device-mode, you should see the value of that integration set to false in the `integrations` object. That means that the data is being sent from the device to the destination SDK, and not through Segment's servers. This is expected if you chose to use a device-mode destination's SDK with Segment's during installation.
 
-Enable verbose [logging](/docs/connections/sources/catalog/libraries/mobile/ios/#logging)  and trigger the call in question. You should see a call to Segment triggered as well as to the partner SDK. It will show you exactly which partner method was invoked and the arguments it was invoked with!
+Enable verbose [logging](/docs/connections/sources/catalog/libraries/mobile/ios#logging)  and trigger the call in question. You should see a call to Segment triggered as well as to the partner SDK. It will show you exactly which partner method was invoked and the arguments it was invoked with!
 
 
 ## Debugging cloud-mode destinations