Merge pull request #8145 from lopenchi/develop

Fix some links

Author: forstisabella

src/connections/destinations/catalog/actions-braze-cloud/index.md

@@ -16,7 +16,7 @@ versions:
 [Braze](https://www.braze.com/){:target="_blank"}, formerly Appboy, is an engagement platform that empowers growth by helping marketing teams to build customer loyalty through mobile, omni-channel customer experiences.
 
 > success ""
-> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Braze Segment destination. There's also a page about the [non-Actions Braze destination](/docs/connections/destinations/catalog/braze/). Both of these destinations receives data _from_ Segment. There's also the [Braze source](/docs/connections/sources/catalog/cloud-apps/braze//), which sends data _to_ Segment!
+> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) Braze Segment destination. There's also a page about the [non-Actions Braze destination](/docs/connections/destinations/catalog/braze/). Both of these destinations receives data _from_ Segment. There's also the [Braze source](/docs/connections/sources/catalog/cloud-apps/braze/), which sends data _to_ Segment!
 
 ## Benefits of Braze Cloud-Mode (Actions) vs Braze (Classic)
 
@@ -77,4 +77,4 @@ Braze requires one of either `external_id`, `user_alias`, or `braze_id` to be pr
 #### Missing events
 When an event is sent under an alias, it might appear to be missing if the alias cannot be found in Braze. This might be due to an incorrect search for the alias in Braze. 
 
-To search for an alias in Braze, use the format `Alias Label:Alias Name`. For example, if the "Alias Label" field is set as email and "Alias Name" field is set as email address, for example: "test@email.com", you should search for the alias using "email:test@email.com".
+To search for an alias in Braze, use the format `Alias Label:Alias Name`. For example, if the "Alias Label" field is set as email and "Alias Name" field is set as email address, for example: "test@email.com", you should search for the alias using "email:test@email.com".

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

@@ -75,6 +75,6 @@ To more details how Wishpond's identify works  visit [Wishpond API Docs: #track]
 
 Make sure you have copied the right keys from Wishpond's ["API Keys" dialog](https://www.wishpond.com/central/welcome?api_keys=true){:target="_blank"}, this destination will need `Merchant ID` and `Tracking Key`.
 
-[Analytics.js]: https://segment.com//docs/connections/sources/catalog/libraries/website/javascript/
+[Analytics.js]: https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/
 [ci-link]: https://circleci.com/gh/segment-integrations/analytics.js-integration-wishpond
 [ci-badge]: https://circleci.com/gh/segment-integrations/analytics.js-integration-wishpond.svg?style=svg

src/connections/sources/catalog/libraries/mobile/react-native/destination-plugins/index.md

@@ -51,13 +51,13 @@ plugins:
     mark:
       url: https://cdn.filepicker.io/api/file/k1fi9InSu6eint2IHilP
   - name: Firebase
-    url: connections/sources/catalog/libraries/mobile/react-native//destination-plugins/firebase-react-native/
+    url: connections/sources/catalog/libraries/mobile/react-native/destination-plugins/firebase-react-native/
     logo:
       url: https://cdn.filepicker.io/api/file/W6teayYkRmKgb8SMqxIn
     mark:
       url: https://cdn.filepicker.io/api/file/ztKtaLBUT7GUZKius5sa
   - name: FullStory
-    url: connections/sources/catalog/libraries/mobile/react-native//destination-plugins/fullstory-react-native/
+    url: connections/sources/catalog/libraries/mobile/react-native/destination-plugins/fullstory-react-native/
     logo:
       url: https://cdn.filepicker.io/api/file/0ET4vgkqTGNMRtZcFWCA
     mark:

src/connections/sources/catalog/libraries/server/net/quickstart.md

@@ -106,6 +106,6 @@ Congratulations! You can now track any event from the browser and the backend. H
 
 ## What's Next?
 
-We just walked through the quickest way to get started with Segment using Analytics.js and the .NET library. You might also want to check out our full [Analytics.js reference](//docs/connections/sources/catalog/libraries/website/javascript/) to see what else is possible, or read about the [Tracking API methods](/docs/connections/spec/) to get a sense for the bigger picture.
+We just walked through the quickest way to get started with Segment using Analytics.js and the .NET library. You might also want to check out our full [Analytics.js reference](/docs/connections/sources/catalog/libraries/website/javascript/) to see what else is possible, or read about the [Tracking API methods](/docs/connections/spec/) to get a sense for the bigger picture.
 
 If you're running an **Ecommerce** site or app you should also check out our [Ecommerce API reference](/docs/connections/spec/ecommerce/v2/) to make sure your products and checkout experience is instrumented properly!

src/connections/sources/catalog/libraries/server/node/migration.md

@@ -60,7 +60,7 @@ If you're using the [classic version of Analytics Node.js](/docs/connections/sou
 
 #### Removals
 The updated Analytics Node.js removed these configuration options:
-- `errorHandler` (see the docs on [error handling](/docs/connections/sources/catalog/libraries/server/node//#error-handling) for more information)
+- `errorHandler` (see the docs on [error handling](/docs/connections/sources/catalog/libraries/server/node/#error-handling) for more information)
 
 The updated Analytics Node.js library removed undocumented behavior around `track` properties 
 

src/guides/how-to-guides/forecast-with-sql.md

@@ -190,7 +190,7 @@ At Toastmates, most of the highest forward-looking expected LTV customers share
 
 With that in mind, you can define a behavioral cohort in our email tool, Customer.io, as well as create a trigger workflow so we can send an email offer to these customers.
 
-[Learn how to use email tools to target this cohort of high value customers.](https://segment.com/docs/guides/how-to-guides/forecast-with-sql//)
+[Learn how to use email tools to target this cohort of high value customers.](https://segment.com/docs/guides/how-to-guides/forecast-with-sql/)
 
 ## Reward your best customers
 

src/guides/what-is-replay.md

@@ -68,7 +68,7 @@ There are two types of replays with Engage.
 #### Nuances to Consider for Engage Replays
 
 **1. Replay a Profile Source's data into Engage Space**
-- When a new Profile Source is connected to an Engage Space, the default option to replay the source's data seen over the past 30 days can be selected. To request a source's additional historical data be replayed to the Engage Space, contact Segment Support at friends@segment.com or [create a ticket](https://segment.com/docs/engage/[url](https://app.segment.com/goto-my-workspace/home?period=last-24-hours&v2=enabled&help=create-ticket)). Please see [this documentation](https://segment.com/docs/engage/quickstart/#step-3-connect-production-sources:~:text=Step%203%3A%20Connect,production%20sources.) on further details of this process and what to include in your support request.
+- When a new Profile Source is connected to an Engage Space, the default option to replay the source's data seen over the past 30 days can be selected. To request a source's additional historical data be replayed to the Engage Space, contact Segment Support at friends@segment.com or [create a ticket](https://app.segment.com/goto-my-workspace/home?period=last-24-hours&v2=enabled&help=create-ticket). Please see [this documentation](https://segment.com/docs/engage/quickstart/#step-3-connect-production-sources:~:text=Step%203%3A%20Connect,production%20sources.) on further details of this process and what to include in your support request.
 
 **2. Replay from an Engage Space to its connected destination**
 - Since each instance of a destination is connected to its own Engage "Output" source, that source contains events for all of the computations that destination is connected to received data from, _the list of output sources can be found under Unify > Unify Settings > Debugger_. Because of this, it's not possible to replay only a specific computation's data to the destination, you should instead consider reaching out to [Segment support](https://segment.com/help/contact/) to request a resync of that computation to its destination instead. However, if you would like to replay all failed events seen by that destination, which will encompass all connected computations, that can be achieved with a replay.