docs: update Skip doc links (#244)

pages/infrastructure_providers-validators/running_a_validator.md

@@ -22,7 +22,7 @@ Note: example endpoints will work out of the box, but will be quickly rate limit
 
 ## Slinky Sidecar
 
-Starting in `v5.0.0`, running a validating full node requires a Skip Protocol's Slinky Sidecar to be run in order to fetch Oracle prices. The sidecar should be started before upgrading from `v4` to `v5`. Instructions to start Slinky Sidecar can be found [here](https://docs.skip.money/slinky/integrations/dydx).
+Starting in `v5.0.0`, running a validating full node requires a Skip Protocol's Slinky Sidecar to be run in order to fetch Oracle prices. The sidecar should be started before upgrading from `v4` to `v5`. Instructions to start Slinky Sidecar can be found [here](https://docs.skip.build/connect/validators/quickstart).
 
 Support issues with Skip's Sidecar should be directed [here](https://discord.gg/7hxEThEaRQ).
 

pages/infrastructure_providers-validators/upgrades/upgrading_sidecar.md

@@ -1,3 +1,3 @@
 Starting in `v5.0.0`, all validating full nodes should be running the [Sidecar](../running_full_node.md#slinky-sidecar). Non validating full nodes do not need to run the sidecar.
 
-Follow instructions [here](https://docs.skip.money/slinky/integrations/dydx/#q-how-do-i-upgrade-the-sidecar-binary) to upgrade the sidecar.
+Follow instructions [here](https://docs.skip.build/connect/validators/faq#how-do-i-upgrade-the-connect-binary) to upgrade the sidecar.

pages/introduction-onboarding_faqs.mdx

@@ -331,7 +331,7 @@
 <summary>1. How is the oracle price computed?</summary>
 
 - The oracle price has five parts:
-  - Skip Protocol Sidecar: side car that pulls price data from external sources and caches them for the validator to use [link](https://docs.skip.money/slinky/integrations/dydx).
+  - Skip Protocol Sidecar: side car that pulls price data from external sources and caches them for the validator to use [link](https://docs.skip.build/connect/validators/quickstart).
   - Vote Extensions: Every block during the Precommit stage, all validators will submit vote extensions for what they believe the oracle price of all tracked assets should be.
   - Consensus: The block after VE are submitted, Slinky deterministically aggregates all VE from the previous block and proposes a new updated price which is voted into consensus.
   - `x/prices` Module: updates the state based on the new price, also has logic for validation and etc. [link](https://github.com/dydxprotocol/v4-chain/tree/main/protocol/x/prices).