Merge pull request #1140 from segmentio/broken-nav-link-fix

[DOC-12] Broken link cleanup and image border fix

Author: markzegarelli

src/_data/glossary.yml

@@ -51,7 +51,7 @@ Destination: |
   A destination is a target for Segment to forward data to, and represents a tool or storage destination.
 
 Device mode: |
-  *Device mode*, (or [client-side](#client-side)) libraries are loaded on the on the user's client (for example their web browser, or mobile device), which means they can collect contextual data about the user. The three main libraries that are considered "device mode" are [Analytics.js](/docs/connections/sources/catalog/libraries/javascript/), which is used on websites, our [iOS SDK](/docs/connections/sources/catalog/libraries/ios/), and our [Android SDK](/docs/connections/sources/catalog/libraries/android/). Device mode libraries can maintain a cache of information about each user on the device so we know that device belongs to a consistent `anonymousId` or `userId`, and has a consistent list of traits like name, email, etc.
+  *Device mode*, (or [client-side](#client-side)) libraries are loaded on the on the user's client (for example their web browser, or mobile device), which means they can collect contextual data about the user. The three main libraries that are considered "device mode" are [Analytics.js](/docs/connections/sources/catalog/libraries/website/javascript/), which is used on websites, our [iOS SDK](/docs/connections/sources/catalog/libraries/mobile/ios/), and our [Android SDK](/docs/connections/sources/catalog/libraries/mobile/android/). Device mode libraries can maintain a cache of information about each user on the device so we know that device belongs to a consistent `anonymousId` or `userId`, and has a consistent list of traits like name, email, etc.
 
 
 DMP: |
@@ -113,7 +113,7 @@ Schema: |
   In Segment, you can send data to a Warehouse which has a schema based on the types of data you collect and route through Segment, and which updates as the data you collect changes.
 
 Server Side: |
-  Refers to a group of libraries that can send data to Segment, in [Cloud mode](#cloud-mode), meaning through the Segment cloud. "Server side" can could refer to people sending data directly to [our HTTP API](/docs/connections/sources/catalog/libraries/http/) without using a "library". Usually used in contrast to [Client Side](#client-side).
+  Refers to a group of libraries that can send data to Segment, in [Cloud mode](#cloud-mode), meaning through the Segment cloud. "Server side" can could refer to people sending data directly to [our HTTP API](/docs/connections/sources/catalog/libraries/server/http-api/) without using a "library". Usually used in contrast to [Client Side](#client-side).
 
 
 SDK: |

src/_data/privacy.yml

@@ -16,7 +16,7 @@ sections:
   section:
   - name: Understand and Comply with regulations
     description: "Segment is committed to making it easier for you to comply with the GDPR."
-    path: /privacy/preparing-for-the-gdpr/
+    path: /privacy/complying-with-for-the-gdpr/
     icon: icon-comply.svg
   - name: Delete and suppress data about end-users
     description: "Easily remove your company's end-users from Segment and supported connections."

src/_data/sidenav/main.yml

@@ -203,7 +203,7 @@ sections:
         title: Warehouse FAQs
       - path: /connections/storage/warehouses/add-warehouse-users
         title: How do you add users?
-      - path: /connections/storage/warehouses/warehouse-errorsx
+      - path: /connections/storage/warehouses/warehouse-errors
         title: What does my warehouse error mean?
       - path: /connections/storage/warehouses/redshift-faq
         title: Redshift cluster and Redshift connector limitations

src/_sass/components/_thumbnail-integration.scss

@@ -42,10 +42,12 @@
     img {
       max-width: 50px;
       max-height: 50px;
+      border: none!important;
 
       @include breakpoint(medium up) {
         max-width: 70px;
         max-height: 70px;
+        border: none!important;
       }
     }
   }

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

@@ -159,7 +159,7 @@ In-App Messaging are custom views which you can send to a segment of users to sh
 The MoEngage SDK is GDPR compliant, follow the doc in this [link](https://docs.moengage.com/docs/gdpr-compliance-1) to know how to use opt-outs for different features. 
 
 ### Segment Docs
-For more info on using **Segment for iOS** refer to [**Developer Docs**](/docs/sources/mobile/ios/) provided by Segment.
+For more info on using **Segment for iOS** refer to [**Developer Docs**](/docs/connections/sources/catalog/libraries/mobile/ios/) provided by Segment.
 
 
 ## Android
@@ -362,10 +362,10 @@ You are now all set up to receive push notifications from MoEngage. For more inf
  
 
 ### Identify
-Use [Identify](/docs/sources/mobile/android/#identify) to track user-specific attributes. This is the same as tracking [user attributes](http://docs.moengage.com/docs/identifying-user) on MoEngage. MoEngage supports traits supported by Segment as well as custom traits. If you set traits.id, MoEngage sets that as the Unique ID for that user.
+Use [Identify](/docs/connections/sources/catalog/libraries/mobil/android/#identify) to track user-specific attributes. This is the same as tracking [user attributes](http://docs.moengage.com/docs/identifying-user) on MoEngage. MoEngage supports traits supported by Segment as well as custom traits. If you set traits.id, MoEngage sets that as the Unique ID for that user.
 
 ### Track
-Use [track](/docs/sources/mobile/android/#track) to track events and user behavior in your app.
+Use [track](/docs/connections/sources/catalog/libraries/mobil/android/#track) to track events and user behavior in your app.
 This will send the event to MoEngage with the associated properties. Tracking events is essential and will help you create segments for engaging users.
 
 ### Reset

src/connections/integration_error_codes.md

@@ -13,4 +13,4 @@ id: integrationerrors
 | errors.awaiting-retry.429          | Rate limit exceeded. contact the partner to raise your limit or avoid sending events in burst.                                                                                                                                                                                                                                      |
 | errors.awaiting-retry.5xx          | The partner's API report an internal error. Consider disabling this integration or contact the integration partner to address this issue.                                                                                                                                                                                           |
 | errors.awaiting-retry.ENOTFOUND<br>errors.awaiting-retry.ECONNREFUSED <br>errors.awaiting-retry.ECONNRESET<br>errors.awaiting-retry.ECONNABORTED<br>errors.awaiting-retry.EHOSTUNREACH<br>errors.awaiting-retry.EAI_AGAIN | Segment is unable to establish a connection with the partner's server. This could mean your Segment configurations contain some invalid settings or that the integration is no longer operational.  If your configurations are valid, consider disabling this integration or contact the integration partner to address this issue. |
-| Others                             | Refer to the error message you receive for more information. Refer to our <a href="/docs/connections/how-do-I-test-my-connections/"> How do I test my connections guide</a> for more debugging help.
+| Others                             | Refer to the error message you receive for more information. Refer to our <a href="/docs/connections/test-connections/"> How do I test my connections guide</a> for more debugging help.

src/connections/sources/visual-tagger.md

@@ -95,7 +95,7 @@ When you click on an element on your website, a window appears where you can ent
    Segment recommends that you use an "Object Action" format (for example, `Blog Post Clicked`, and use Title Case (capitalize the first letter of each word ) when naming events.
 
 2. **Properties**. Add properties to the event to add contextual information about the action that the user took. Properties are optional, but they are very helpful when you analyze events data later.
-   - Use `snake_case` for property names (all lowercase, with spaces between words represented as an underscore “_”). For a guide on event naming best practices, check out our Docs [here](docs/protocols/tracking-plan/best-practices/#formalize-your-naming-and-collection-standards).
+   - Use `snake_case` for property names (all lowercase, with spaces between words represented as an underscore “_”). For a guide on event naming best practices, check out the Docs [here](/docs/protocols/tracking-plan/best-practices/#formalize-your-naming-and-collection-standards).
    - Check the [list of properties that are collected by default](/docs/connections/spec/common/) before you add a property.
 
 3. **Advanced**. You can also click the `</>` button to manually edit the CSS selector. If you didn't select the right element, you can choose the element on the page again by clicking on the finger button.

src/guides/how-to-guides/measure-marketing-roi.md

@@ -12,7 +12,7 @@ This guide provides you with the tools to answer these questions with SQL so tha
 
 The goal of marketing campaigns is to drive engagement and conversions. Most commonly performed by attracting traffic to the site, these campaigns use UTM parameters for attribution. In our analysis, we'll be heavily relying on UTM parameters to analyze not only campaign, but also channel performance.
 
-[Learn how to effectively use UTM parameters in your marketing campaign strategies.](/docs/guides/sources/how-to-track-customers-across-channels-devices)
+[Learn how to effectively use UTM parameters in your marketing campaign strategies.](/docs/guides/how-to-guides/cross-channel-tracking/)
 
 For our analysis walkthrough, we'll use fictitious e-commerce and marketing data from on-demand artisanal toast company, Toastmates.
 

src/partners/conceptual-model.md

@@ -70,7 +70,7 @@ Streams are the basis for sending events to Segment directly as an [Event Source
 
 Subscriptions are the basis for [Cloud-mode Destinations](/docs/connections/destinations/#connection-modes), and are the starting point for our partnership. Subscriptions can be created, configured, and managed in the Segment Developer Center.
 
-Subscriptions give you complete control over how you want to store, transform and process your customers' data. It means that our customers can immediately start sending you data from any one of our [sources](/docs/connections/sources/)—from the browser, from their mobile apps, or from their servers—with no added work. Segment [Business Plan](https://segment.com/pricing/) customers can also [**replay**](/docs/guides/destinations/what-are-my-data-export-options/) historical data from our archives, which means you can demonstrate the full value of your tool immediately upon enablement.
+Subscriptions give you complete control over how you want to store, transform and process your customers' data. It means that our customers can immediately start sending you data from any one of our [sources](/docs/connections/sources/)—from the browser, from their mobile apps, or from their servers—with no added work. Segment [Business Plan](https://segment.com/pricing/) customers can also [**replay**](/docs/connections/data-export-options/) historical data from our archives, which means you can demonstrate the full value of your tool immediately upon enablement.
 
 Note that Object data collected from Cloud Object Sources (such as Stripe, Zendesk, and Salesforce) currently only targets customer Warehouse Destinations and is not not made available to Destinations through Subscriptions.
 

src/personas/identity-resolution/externalids.md

@@ -3,7 +3,7 @@ title: Identity Resolution ExternalIDs
 ---
 
 > note ""
-> **NOTE:** The steps in this guide pertain to spaces created before September 27th, 2020. For spaces created after September 27th, 2020, please refer to the onboarding guide [here](/docs/personas/identity-resolution/identity-onboarding/).
+> **NOTE:** The steps in this guide pertain to spaces created before September 27th, 2020. For spaces created after September 27th, 2020, please refer to the onboarding guide [here](/docs/personas/identity-resolution/identity-resolution-onboarding/).
 
 ## Default ExternalIDs