diff --git a/docs/build/build-index.md b/docs/build/build-index.md
index b64c1cc6cc8..dd9c2fecfa9 100644
--- a/docs/build/build-index.md
+++ b/docs/build/build-index.md
@@ -28,7 +28,7 @@ This section of the wiki is divided into the following parts:
 ## Tools & Resources
 
 - [Tools](build-tools-index.md) - Maintained list of tools.
-- [Subkey](https://docs.substrate.io/v3/tools/subkey/) - Command line utility for
+- [Subkey](https://docs.substrate.io/reference/command-line-tools/subkey/) - Command line utility for
   generating and inspecting key pairs.
 - [JS tools](https://github.com/polkadot-js/tools) - TypeScript tools for offline signing of
   transactions, RPC calls, and more.
diff --git a/docs/build/build-node-interaction.md b/docs/build/build-node-interaction.md
index b892ce172ae..eb2e8df6652 100644
--- a/docs/build/build-node-interaction.md
+++ b/docs/build/build-node-interaction.md
@@ -11,7 +11,7 @@ This page will guide you through some basic interactions with your node. This gu
 seen as canonical reference. Always refer to the proper
 documentation for the tool you are using:
 
-- [Substrate RPC API](https://docs.substrate.io/rustdocs/latest/sc_rpc_api/index.html)
+- [Substrate RPC API](https://paritytech.github.io/substrate/master/sc_rpc_api/index.html)
 - [Polkadot-JS RPC](https://polkadot.js.org/docs/substrate/rpc)
 - [Substrate API Sidecar](https://github.com/paritytech/substrate-api-sidecar)
 
@@ -46,9 +46,9 @@ $ curl -H "Content-Type: application/json" -d '{"id":1, "jsonrpc":"2.0", "method
 ```
 
 Some return values may not appear meaningful at first glance. Polkadot uses
-[SCALE encoding](https://docs.substrate.io/v3/advanced/scale-codec/) as a format that is
+[SCALE encoding](https://docs.substrate.io/reference/scale-codec/) as a format that is
 suitable for resource-constrained execution environments. You will need to decode the information
-and use the chain [metadata](https://docs.substrate.io/v3/runtime/metadata/)
+and use the chain [metadata](https://docs.substrate.io/reference/command-line-tools/subxt/#metadata)
 (`state_getMetadata`) to obtain human-readable information.
 
 ### Tracking the Chain Head
diff --git a/docs/build/build-node-management.md b/docs/build/build-node-management.md
index 29e53fc432a..eaaaffd177f 100644
--- a/docs/build/build-node-management.md
+++ b/docs/build/build-node-management.md
@@ -89,7 +89,7 @@ can set a custom path with `--base-path <path>`.
 The keystore stores session keys, which are important for validator operations.
 
 - [Polkadot documentation](../learn/learn-keys.md/#session-keys)
-- [Substrate documentation](https://docs.substrate.io/v3/concepts/session-keys/)
+- [Substrate documentation](https://docs.substrate.io/main-docs/fundamentals/accounts-addresses-keys/#specialized-accounts)
 
 **`db`**
 
@@ -170,5 +170,5 @@ puts your node at higher risk of attack. You can run your own, private
 
 The node also exposes a Prometheus endpoint by default (disable with `--no-prometheus`). Substrate
 has a
-[vizualizing node metrics tutorial](https://docs.substrate.io/tutorials/v3/node-metrics/)
+[monitor node metrics tutorial](https://docs.substrate.io/tutorials/get-started/node-metrics/)
 which uses this endpoint.
diff --git a/docs/build/build-parachains.md b/docs/build/build-parachains.md
index 6f09f70938c..1ade55c9b5f 100644
--- a/docs/build/build-parachains.md
+++ b/docs/build/build-parachains.md
@@ -241,7 +241,7 @@ finalize, and treat as correct.
 
 See the [Cumulus overview](https://github.com/paritytech/cumulus/blob/master/docs/overview.md) for a
 more detailed description of Cumulus, and for those with experience in Substrate, give the
-[Cumulus tutorial](https://docs.substrate.io/tutorials/v3/cumulus/start-relay/) a try.
+[parachain tutorials](https://docs.substrate.io/tutorials/connect-other-chains/relay-chain/) a try.
 
 Cumulus is still in development, but the idea is that it should be simple
 to take a Substrate chain and add the parachain code by importing the crates and adding a single line
@@ -366,7 +366,7 @@ Once the executable is built, launch collators for your parachain:
 ```
 
 If you are interested in running and launching your own parathread or parachain, Parity Technologies
-has created a [Cumulus tutorial](https://docs.substrate.io/tutorials/v3/cumulus/start-relay/) to show you how.
+has created [parachain tutorials](https://docs.substrate.io/tutorials/connect-other-chains/relay-chain/) to show you how.
 Get stuck or need support along the way? Join the
 [Parachain Technical matrix chat channel](https://matrix.to/#/#parachain-technical:matrix.parity.io)
 and connect with other builders there.
@@ -444,7 +444,7 @@ selecting any parachain of choice.
 
 For the purpose of these following examples, we will be using the
 Rococo testnet "Custom Node" underneath "Development", following the
-[Cumulus tutorial](https://docs.substrate.io/tutorials/v3/cumulus/start-relay/).
+[parachain tutorials](https://docs.substrate.io/tutorials/connect-other-chains/relay-chain/).
 
 ### Parachain Playground
 
@@ -492,7 +492,7 @@ For more information on how parathread per-block auctions work, see the more det
 
 ## Resources 
 
-- [Parachains Guide Overview](https://docs.substrate.io/how-to-guides/v3/parachains/connect/)
+- [Parachain tutorials](https://docs.substrate.io/tutorials/connect-other-chains/relay-chain/)
 - [Common Good Parachains](https://polkadot.network/blog/common-good-parachains-an-introduction-to-governance-allocated-parachain-slots/)
 - [The Launch of Parachains](https://polkadot.network/blog/the-launch-of-parachains/)
 - [Parathreads: Pay-as-you-go Parachains](https://medium.com/polkadot-network/parathreads-pay-as-you-go-parachains-7440d23dde06)
diff --git a/docs/build/build-protocol-info.md b/docs/build/build-protocol-info.md
index b40a23f49ff..f2cdd888bd9 100644
--- a/docs/build/build-protocol-info.md
+++ b/docs/build/build-protocol-info.md
@@ -41,7 +41,7 @@ Polkadot (and Substrate) use the SS58 address format. This is a broad "meta-form
 handle many different cryptographic schemes and chains. It has much in common with Bitcoin's
 Base58Check format such as a version prefix, a hash-based checksum suffix, and base-58 encoding.
 
-See the [SS58 page](https://docs.substrate.io/v3/advanced/ss58/) in the Substrate documentation for
+See the [SS58 page](https://docs.substrate.io/main-docs/fundamentals/accounts-addresses-keys/#address-encoding-and-chain-specific-addresses) in the Substrate documentation for
 encoding information and a more comprehensive list of network prefixes.
 
 :::warning Do not use regular expressions (regex) to validate addresses
@@ -49,8 +49,7 @@ encoding information and a more comprehensive list of network prefixes.
 Always verify using the
 prefix and checksum of the address. Substrate API Sidecar provides an
 `accounts/{accountId}/validate` path that returns a boolean `isValid` response for a provided
-address. If you want to validate addresses in another way, see the
-[validation documentation](https://docs.substrate.io/v3/advanced/ss58/#validating-addresses).
+address.
 
 :::
 
@@ -109,7 +108,7 @@ transfers on Statemint. Statemint integration is discussed in the next page of t
 ## Free vs. Reserved vs. Locked vs. Vesting Balance
 
 Account balance information is stored in
-[`AccountData`](https://docs.substrate.io/rustdocs/latest/pallet_balances/struct.AccountData.html).
+[`AccountData`](https://paritytech.github.io/substrate/master/pallet_balances/struct.AccountData.html).
 Polkadot primarily deals with two types of balances: free and reserved.
 
 For most operations, free balance is what you are interested in. It is the "power" of an account in
@@ -131,9 +130,9 @@ over time until all the funds are transferable.
 
 More info:
 
-- [Lockable Currency](https://docs.substrate.io/rustdocs/latest/frame_support/traits/trait.LockableCurrency.html)
-- [Lock Withdraw Reasons](https://docs.substrate.io/rustdocs/latest/frame_support/traits/enum.WithdrawReason.html)
-- [Vesting](https://docs.substrate.io/rustdocs/latest/pallet_vesting/struct.Vesting.html)
+- [Lockable Currency](https://paritytech.github.io/substrate/master/frame_support/traits/trait.LockableCurrency.html)
+- [Lock Withdraw Reasons](https://paritytech.github.io/substrate/master/frame_support/traits/struct.WithdrawReasons.html)
+- [Vesting Info](https://paritytech.github.io/substrate/master/pallet_vesting/struct.VestingInfo.html)
 
 ## Extrinsics and Events
 
@@ -147,7 +146,7 @@ Extrinsics constitute information from the outside world and take on three forms
 
 As an infrastructure provider, you will deal almost exclusively with signed transactions. You will,
 however, see other extrinsics within the blocks that you decode. Find more information in the
-[Substrate documentation](https://docs.substrate.io/v3/concepts/extrinsics/).
+[Substrate documentation](https://docs.substrate.io/main-docs/build/tx-weights-fees/).
 
 Inherents contain information that is not provably true, but validators agree on based on some
 measure of reasonability. For example, a timestamp cannot be proved, but validators can agree that
@@ -223,7 +222,7 @@ The correct way to uniquely identify an extrinsic on a Substrate-based chain is
 (height or hash) and the extrinsic's index. Substrate defines a block as a header and an array of
 extrinsics; therefore, an index in the array at a canonical height will always uniquely identify a
 transaction. This methodology is reflected in the Substrate codebase itself, for example to
-[reference a previous transaction](https://docs.substrate.io/rustdocs/latest/pallet_multisig/struct.Timepoint.html)
+[reference a previous transaction](https://paritytech.github.io/substrate/master/pallet_multisig/struct.Timepoint.html)
 from the Multisig pallet.
 
 ### Events
@@ -248,7 +247,7 @@ Polkadot uses weight-based fees that, unlike gas, are charged _pre-dispatch._ Us
 
 Parity's integration tools should allow you to deal with decoded data. If you'd like to bypass them
 and interact directly with the chain data or implement your own codec, Polkadot encodes block and
-transaction data using the [SCALE codec](https://docs.substrate.io/v3/advanced/scale-codec/).
+transaction data using the [SCALE codec](https://docs.substrate.io/reference/scale-codec/).
 
 ## Runtime Upgrades
 
diff --git a/docs/build/build-smart-contracts.md b/docs/build/build-smart-contracts.md
index c7426e3d104..45f90953c14 100644
--- a/docs/build/build-smart-contracts.md
+++ b/docs/build/build-smart-contracts.md
@@ -70,10 +70,10 @@ can also be mapped directly to and from Substrate's SS58 scheme from existing ac
 ### Substrate Contracts
 
 Substrate offers a built-in
-[contract pallet](https://docs.substrate.io/rustdocs/latest/pallet_contracts/index.html);
+[contract pallet](https://paritytech.github.io/substrate/master/pallet_contracts/index.html);
 as time goes on, more parachains will support [WebAssembly](../learn/learn-wasm.md) smart contracts.
 Additionally, there is the
-[EVM Pallet](https://docs.substrate.io/v3/runtime/smart-contracts/#evm-pallet), which allows
+[EVM Pallet](https://github.com/paritytech/frontier/tree/master/frame/evm#evm-module), which allows
 a parachain to implement the Ethereum Virtual Machine, thereby supporting almost direct ports of
 Ethereum contracts.
 
@@ -90,7 +90,7 @@ Here is the list of current resources available to developers who want to get st
 contracts to deploy on parachains based on Substrate.
 
 - [ink!](https://github.com/paritytech/ink) - Parity's ink to write smart contracts.
-- [Substrate ink! Workshop](https://docs.substrate.io/tutorials/v3/ink-workshop/pt1/) - Walks you
+- [Substrate ink! Workshop](https://docs.substrate.io/tutorials/smart-contracts/develop-contract/) - Walks you
   through the basics of writing and deploying an ERC-20 token using `ink!`.
 
 ### Contracts Pallet
diff --git a/docs/build/build-ss58-registry.md b/docs/build/build-ss58-registry.md
index b66a2e44b47..d62a229cf9f 100644
--- a/docs/build/build-ss58-registry.md
+++ b/docs/build/build-ss58-registry.md
@@ -6,7 +6,7 @@ description: Information about SS58 encoding.
 slug: ../build-ss58-registry
 ---
 
-:::note Substrate-based chains use an [SS58 encoding](https://docs.substrate.io/v3/advanced/ss58/) for their address formats.
+:::note Substrate-based chains use an SS58 encoding for their address formats.
 
 Please see the 
 [SS58 registry](https://github.com/paritytech/ss58-registry/) to see which 
diff --git a/docs/build/build-storage.md b/docs/build/build-storage.md
index 79bb3d4866d..629e21f99ca 100644
--- a/docs/build/build-storage.md
+++ b/docs/build/build-storage.md
@@ -57,7 +57,7 @@ experimental [Parity database](https://github.com/paritytech/parity-db).
 The database is used for components that require persistent storage
 These are components like Substrate clients, Substrate light-clients & off-chain workers. 
 For more information, check out
-Substrate Developer Hub's [Storage Page](https://docs.substrate.io/v3/advanced/storage/).
+Substrate documentation [Storage Page](https://docs.substrate.io/main-docs/build/runtime-storage/).
 
 :::
 
@@ -66,23 +66,23 @@ which gives access to Substrate's storage APIs. These storage items support valu
 Parity's `SCALE (Simple Concatenated Aggregate Little-Endian) Codec`.
 
 There is a
-[`Storage Value`](https://docs.substrate.io/rustdocs/latest/frame_support/storage/trait.StorageValue.html) API
+[`Storage Value`](https://paritytech.github.io/substrate/master/frame_support/storage/trait.StorageValue.html) API
 that is used to store single values,
-a [`Storage Map`](https://docs.substrate.io/rustdocs/latest/frame_support/storage/trait.StorageMap.html) API
+a [`Storage Map`](https://paritytech.github.io/substrate/master/frame_support/storage/trait.StorageMap.html) API
 that is used to a key-value hash map,
-a [`Storage Double Map`](https://docs.substrate.io/rustdocs/latest/frame_support/storage/trait.StorageDoubleMap.html) API
+a [`Storage Double Map`](https://paritytech.github.io/substrate/master/frame_support/storage/trait.StorageDoubleMap.html) API
 that creates a `storage map` with two keys to provide the ability to efficiently remove all entries that have 
-a common first key, and a [`Storage N Map`](https://crates.parity.io/frame_support/storage/trait.StorageNMap.html) 
+a common first key, and a [`Storage N Map`](https://paritytech.github.io/substrate/master/frame_support/storage/trait.StorageNMap.html) 
 API that can be used to store a hash map with any arbitrary number of keys.
 
 These layered APIs act as runtime storage that allows you to store data in your blockchain. More information can 
-be found at the [`Runtime Storage Page`](https://docs.substrate.io/v3/runtime/storage/) on Substrate Developer Hub.
+be found at the [`Runtime Storage Page`](https://docs.substrate.io/main-docs/build/runtime-storage/) on Substrate Developer Hub.
 
 ### Crust Storage
 
 [Crust Network](https://crust.network) provides a Web3.0 decentralized storage network for the Metaverse. It is designed to realize core values of decentralization, privacy, and assurance. Crust supports multiple storage-layer protocols such as [IPFS](#ipfs-interplanetary-file-system), and exposes instant accessible on-chain storage functions to users. Crustʼs technical stack is also capable of supporting data manipulating and computing.
 
-Crust provides a native cross-chain communnication communication pallet based on [XCMP](https://wiki.polkadot.network/docs/learn-crosschain), called [xStorage](https://github.com/crustio/crust/tree/parachain/shadow/crust-collator/pallets/xstorage).
+Crust provides a native cross-chain communication communication pallet based on [XCMP](https://wiki.polkadot.network/docs/learn-crosschain), called [xStorage](https://github.com/crustio/crust/tree/parachain/shadow/crust-collator/pallets/xstorage).
 
 The protocol also supports most smart contract platforms, including Ethereum, with its [cross-chain dStorage solution](https://wiki.crust.network/docs/en/buildCrossChainSolution).
 
diff --git a/docs/build/build-substrate.md b/docs/build/build-substrate.md
index 0c665366002..4dbb1eeee8e 100644
--- a/docs/build/build-substrate.md
+++ b/docs/build/build-substrate.md
@@ -21,7 +21,7 @@ this is done through two main approaches:
      and insecure.
 
 There is now a new paradigm: instead of specifying a centralized RPC node, developers just need to 
-define the blockchain's [chain specification](https://docs.substrate.io/v3/runtime/chain-specs/) for 
+define the blockchain's [chain specification](https://docs.substrate.io/main-docs/build/chain-spec/) for 
 their application to synchronize with the chain. This is possible with Substrate connect.
 
 ## What is Substrate Connect? 
@@ -93,5 +93,4 @@ will be created in-page for them.
 - [What is a light client and why you should care?](https://www.parity.io/blog/what-is-a-light-client/)
 - [Introducing Substrate Connect: Browser-Based Light Clients for Connecting to Substrate Chains](https://www.parity.io/blog/introducing-substrate-connect)
 - [Substrate connect GitHub Repo](https://github.com/paritytech/substrate-connect/tree/master/projects/extension)
-- [Substrate connect Docs](https://docs.substrate.io/v3/integration/substrate-connect/)
   
\ No newline at end of file
diff --git a/docs/build/build-tools-index.md b/docs/build/build-tools-index.md
index da8369df8b3..cc4e640a62b 100644
--- a/docs/build/build-tools-index.md
+++ b/docs/build/build-tools-index.md
@@ -120,7 +120,7 @@ usage instructions are provided at
   Tool to construct, sign, and broadcast transactions. Signing can be done offline.
 - [Polkadot API Cpp](https://github.com/usetech-llc/polkadot_api_cpp) - A С++ API for Polkadot, can
   build `clip`, a command line tool.
-- [Subkey](https://docs.substrate.io/v3/tools/subkey/) - Command line utility for
+- [Subkey](https://docs.substrate.io/reference/command-line-tools/subkey/) - Command line utility for
   generating and inspecting key pairs.
 
 ### WASM
@@ -159,7 +159,7 @@ WebAssembly related tools and projects.
 
 ### SCALE Codec
 
-The [SCALE](https://docs.substrate.io/v3/advanced/scale-codec/) (Simple Concatenated
+The SCALE (Simple Concatenated
 Aggregate Little-Endian) Codec is a lightweight, efficient, binary serialization and deserialization
 codec.
 
@@ -170,15 +170,7 @@ the decoding context has all type knowledge about the encoded data.
 It is used in almost all communication to/from Substrate nodes, so implementations in different
 languages exist:
 
-- [Ruby](https://github.com/itering/scale.rb)
-- [Rust](https://github.com/paritytech/parity-scale-codec)
-- [Go](https://github.com/itering/scale.go)
-- [C++](https://github.com/soramitsu/kagome/tree/master/core/scale)
-- [TypeScript](https://github.com/polkadot-js/api)
-- [AssemblyScript](https://github.com/LimeChain/as-scale-codec)
-- [Haskell](https://github.com/airalab/hs-web3/tree/master/src/Codec)
-- [Java](https://github.com/emeraldpay/polkaj)
-- [Python](https://github.com/polkascan/py-scale-codec)
+- [Substrate Awesome](https://github.com/substrate-developer-hub/awesome-substrate#scale-codec) maintains a list of SCALE codex implementations.
 
 ## Data Crawling and Conversion
 
diff --git a/docs/build/build-transaction-construction.md b/docs/build/build-transaction-construction.md
index be78a20e8fc..bd0e17b37dc 100644
--- a/docs/build/build-transaction-construction.md
+++ b/docs/build/build-transaction-construction.md
@@ -73,7 +73,7 @@ in general the serialization format can be described as follows:
 
 The metadata provides you with all of the information required to know how to construct the serialized call data 
 specific to your transaction. You can read more about the metadata, its format and how to get it in the 
-[Substrate documentation](https://docs.substrate.io/v3/runtime/metadata/).
+[Substrate documentation](https://docs.substrate.io/reference/command-line-tools/subxt/#metadata).
 
 \* Polkadot supports sr25519, ed25519, and ECDSA as signing schemes.
 
@@ -245,7 +245,7 @@ There are several ways to submit a signed payload:
 ## Notes
 
 Some addresses to use in the examples. See
-[Subkey documentation](https://docs.substrate.io/v3/tools/subkey/).
+[Subkey documentation](https://docs.substrate.io/reference/command-line-tools/subkey/).
 
 ```bash
 $ subkey --network polkadot generate
diff --git a/docs/general/faq.md b/docs/general/faq.md
index 1436fa4ceea..8e08c51105e 100644
--- a/docs/general/faq.md
+++ b/docs/general/faq.md
@@ -277,7 +277,7 @@ Of the protocols that are custom to Substrate, there are the legacy Substrate st
 request-response for getting information on blocks (sync), a light client protocol, a notification
 protocol for transactions, and block announcement. For detailed information on how Substrate uses
 libp2p and the standard and custom protocols, please see the
-[networking documentation](https://docs.substrate.io/rustdocs/latest/sc_network/index.html).
+[networking documentation](https://paritytech.github.io/substrate/master/sc_network/index.html).
 
 ### How does libp2p differ from IPFS?
 
@@ -305,7 +305,7 @@ follows the following formula:
 base_fee + (tx_length * length_fee) + WeightToFee(weight)
 ```
 
-Please see the [fee calculation](https://docs.substrate.io/v3/runtime/weights-and-fees/) page in
+Please see the [fee calculation](https://docs.substrate.io/reference/how-to-guides/weights/calculate-fees/) page in
 the Substrate documentation for more detailed information.
 
 ## Answered by Gav series
diff --git a/docs/general/glossary.md b/docs/general/glossary.md
index d0c3a32305b..c92947f37a1 100644
--- a/docs/general/glossary.md
+++ b/docs/general/glossary.md
@@ -486,7 +486,7 @@ The [testnet](#testnet) set aside for testing parachains, cumulus, and related t
 
 A system-level origin in [Substrate](#Substrate). This is the highest privilege level and can be 
 thought of as the superuser of the runtime origin. To learn about more raw origins in Substrate, 
-visit [Substrate Docs](https://docs.substrate.io/v3/runtime/origins/)
+visit [Substrate Docs](https://docs.substrate.io/main-docs/build/origins/)
 
 ## Runtime
 
diff --git a/docs/general/kusama/kusama-claims.md b/docs/general/kusama/kusama-claims.md
index b0e7d45e883..a24d9afe7a3 100644
--- a/docs/general/kusama/kusama-claims.md
+++ b/docs/general/kusama/kusama-claims.md
@@ -26,7 +26,7 @@ In terms of hardware wallet support, you can use the [Kusama Ledger application]
 or [Parity Signer](../../learn/learn-account-generation.md#parity-signer).
 
 Another option you may consider using is the 
-[Subkey](https://docs.substrate.io/v3/tools/subkey/#:~:text=Subkey%20is%20a%20public%20key,signatures%20on%20the%20Ristretto%20group) 
+[Subkey](https://docs.substrate.io/reference/command-line-tools/subkey/) 
 command-line utility, which will allow you to
 take extra steps to protect the security of your key.
 
@@ -89,7 +89,7 @@ cargo install --git https://github.com/alexcrichton/wasm-gc
 Alternatively, you can build Subkey from the source code.
 
 1. Follow the build instructions for
-   [Substrate](https://docs.substrate.io/v3/getting-started/installation/).
+   [Substrate](https://docs.substrate.io/quick-start/).
 2. When building, only build Subkey by typing `cargo build -p subkey`.
 3. The executable is `./target/debug/subkey`.
 
@@ -115,7 +115,7 @@ NOTE: Previous versions of Subkey only generated Substrate addresses. If you do
 a new seed, you can convert the Substrate address to a Kusama address by following
 [this section](#kusama-from-substrate-address).
 
-See the [Subkey documentation](https://docs.substrate.io/v3/tools/subkey/) or
+See the [Subkey documentation](https://docs.substrate.io/reference/command-line-tools/subkey/) or
 enter `subkey --help` for more usage examples.
 
 ### Using Polkadot-JS UI
diff --git a/docs/learn/learn-accounts.md b/docs/learn/learn-accounts.md
index 50bbdb1ef6c..dc8f44f3246 100644
--- a/docs/learn/learn-accounts.md
+++ b/docs/learn/learn-accounts.md
@@ -23,8 +23,8 @@ For example:
 - Kusama addresses always start with a capital letter, such as **C D, F, G, H, J**.
 - Generic Substrate addresses **always start with** the number **5**.
 
-These prefixes, including how to validate addresses, are broken down on the
-[Substrate SS58 documentation](https://docs.substrate.io/v3/advanced/ss58/). Never use regular
+These prefixes, including how to validate addresses, are embedded in the 
+Substrate SS58 format. Never use regular
 expressions for address validation.
 
 It's important to understand that different network formats are **merely other representations of
@@ -63,7 +63,7 @@ Most wallets generate a mnemonic phrase for users to back up their wallets and g
 key from the mnemonic. Not all wallets use the same algorithm to convert from mnemonic phrase to
 private key.
 
-A typical mnemonic phrase generated by [the Subkey tool](https://docs.substrate.io/v3/tools/subkey/)
+A typical mnemonic phrase generated by [the Subkey tool](https://docs.substrate.io/reference/command-line-tools/subkey/)
 is shown below.
 
 ```
@@ -130,7 +130,7 @@ with the second. These derivation methods have their use cases, given that the p
 the derived accounts are fully secure. Unless you have a specific need for a soft derivation, it is
 recommended to generate the account using a hard derivation path.
 
-See the [Subkey documentation](https://docs.substrate.io/v3/tools/subkey/) for details and examples
+See the [Subkey documentation](https://docs.substrate.io/reference/command-line-tools/subkey/) for details and examples
 of derivation path formats. The Polkadot-JS Apps and Extension and Parity Signer support custom
 derivation paths using the same syntax as Subkey.
 
@@ -238,7 +238,7 @@ Besides the extension and the default UI, Polkadot and Kusama addresses can also
 [Subkey tool](https://github.com/paritytech/substrate/tree/master/bin/utils/subkey). Subkey is
 intended for users comfortable with using the command line and can seem intimidating but is quite
 approachable. Follow the instructions in the
-[Subkey documentation](https://docs.substrate.io/v3/tools/subkey/). When used properly, Subkey is
+[Subkey documentation](https://docs.substrate.io/reference/command-line-tools/subkey/). When used properly, Subkey is
 the **most secure** available method of creating an account.
 
 There is also the very secure [Parity Signer](https://www.parity.io/signer/). This keeps your keys
@@ -661,7 +661,7 @@ key is a base-16 (hexadecimal) address.
 
 This is to showcase that the **SS58 address is based on the public key (aka "Account ID")**
 
-The Subkey Tool's The [Inspecting Keys](https://docs.substrate.io/v3/tools/subkey/#inspecting-keys)
+The Subkey Tool's The [Inspecting Keys](https://docs.substrate.io/reference/command-line-tools/subkey/#inspecting-keys)
 section explains how to use the `inspect` command to recalculate your key pair's public key and
 address.
 
diff --git a/docs/learn/learn-collator.md b/docs/learn/learn-collator.md
index 60b64ef6f9c..59618b24594 100644
--- a/docs/learn/learn-collator.md
+++ b/docs/learn/learn-collator.md
@@ -60,7 +60,7 @@ the build parachain page.
 
 ## Guides and Tools
 
-- [Workshop covering Cumulus and Collators](https://docs.substrate.io/tutorials/v3/cumulus/start-relay/)
-- [Rococo tesnet guide](../build/build-parachains.md##testing-a-parachains:-rococo-testnet)
+- [Tutorial covering Cumulus and Collators](https://docs.substrate.io/tutorials/connect-other-chains/)
+- [Rococo testnet guide](../build/build-parachains.md##testing-a-parachains:-rococo-testnet)
 - [polkadot-launch](https://github.com/shawntabrizi/polkadot-launch) - a tool to quickly spin up a
   local Polkadot testnet based on some parameters like number of parachains, collator setup, etc.
diff --git a/docs/learn/learn-parachains.md b/docs/learn/learn-parachains.md
index 91875f67548..b6c47f94b12 100644
--- a/docs/learn/learn-parachains.md
+++ b/docs/learn/learn-parachains.md
@@ -171,7 +171,7 @@ that {{ polkadot: Polkadot :polkadot }}
 #### How about parachains that are not Substrate-based?
 
 Substrate provides 
-[FRAME Pallets](https://docs.substrate.io/v3/runtime/frame/) as
+[FRAME Pallets](https://docs.substrate.io/main-docs/fundamentals/runtime-intro/) as
 part of its framework to seamlessly build a rustic-based blockchain. Part of FRAME are pallets
 that can be used for consensus. {{ polkadot: Polkadot :polkadot }} 
 {{ kusama: Kusama :kusama }} being a Substrate-based chain relies on BABE as the block
diff --git a/docs/learn/learn-phragmen.md b/docs/learn/learn-phragmen.md
index 8361871c63c..19a5546c641 100644
--- a/docs/learn/learn-phragmen.md
+++ b/docs/learn/learn-phragmen.md
@@ -551,7 +551,7 @@ possible. It then runs an edge-reducing algorithm to minimize the number of vali
 nominator, ideally giving every nominator a single validator to nominate per era.
 
 To minimize block computation time, the staking process is run as an
-[off-chain worker](https://docs.substrate.io/v3/concepts/off-chain-workers).
+[off-chain worker](https://docs.substrate.io/reference/how-to-guides/offchain-workers/).
 In order to give time for this off-chain worker to run, staking commands (bond, nominate, etc.) are
 not allowed in the last quarter of each era.
 
diff --git a/docs/learn/learn-polkadotjs.md b/docs/learn/learn-polkadotjs.md
index d96fd09e133..a672e6498f1 100644
--- a/docs/learn/learn-polkadotjs.md
+++ b/docs/learn/learn-polkadotjs.md
@@ -103,4 +103,4 @@ For more user-friendly wallets, check out the supported and treasury-funded wall
 ### Documentation
 
 - [Official polkadot{.js} docs](https://polkadot.js.org/docs/)
-- [Substrate docs on Polkadot-JS](https://docs.substrate.io/v3/integration/polkadot-js/)
+- [Substrate docs on Polkadot-JS](https://docs.substrate.io/reference/command-line-tools/polkadot-apps/)
diff --git a/docs/learn/learn-transaction-fees.md b/docs/learn/learn-transaction-fees.md
index 14d46ec50a0..8691c1b0adf 100644
--- a/docs/learn/learn-transaction-fees.md
+++ b/docs/learn/learn-transaction-fees.md
@@ -38,7 +38,7 @@ accounts for the time to execute the transaction. All weights, even the base wei
 are a measure of time to execute on some standard hardware.
 
 The runtime 
-[converts weight units to balance units](https://docs.substrate.io/how-to-guides/v3/weights/calculate-fees/) 
+[converts weight units to balance units](https://docs.substrate.io/reference/how-to-guides/weights/calculate-fees/) 
 as part of the fee calculation.
 
 The weight fee is the sum of the base weight and the sum of the total weight consumed by 
@@ -52,7 +52,7 @@ and the weight would be one base weight and then the sum of the weights for `bon
 :::
 
 To learn more about the motivation of a weight fee, check out this 
-[Substrate doc](https://docs.substrate.io/v3/concepts/weight/) on weights.
+[Substrate doc](https://docs.substrate.io/main-docs/build/tx-weights-fees/) on weights.
 
 The length fee is a per-byte fee multiplier for the size of the transaction in bytes.
 
@@ -167,6 +167,4 @@ within some acceptable range of their own system clocks.
 ## Learn More
 
 - [Web3 Foundation Research](https://research.web3.foundation/en/latest/polkadot/overview/2-token-economics.html)
-- [Substrate Weights](https://docs.substrate.io/v3/concepts/weight/)
-- [Substrate Fees](https://docs.substrate.io/v3/runtime/weights-and-fees/)
-- [Extrinsics](https://docs.substrate.io/v3/concepts/extrinsics/)
+- [Substrate Extrinsics, Weights & Fees](https://docs.substrate.io/main-docs/build/tx-weights-fees/)
\ No newline at end of file
diff --git a/docs/learn/learn-treasury.md b/docs/learn/learn-treasury.md
index 8cf618f4ff9..8cbc37e9e97 100644
--- a/docs/learn/learn-treasury.md
+++ b/docs/learn/learn-treasury.md
@@ -330,4 +330,4 @@ migration to a minority fork. However, the possibility of this scenario is quite
 
 - [Substrate's Treasury Pallet](https://github.com/paritytech/substrate/blob/master/frame/treasury/src/lib.rs) -
   The Rust implementation of the Treasury.
-  ([Docs](https://docs.substrate.io/rustdocs/latest/pallet_treasury/index.html))
+  ([Docs](https://paritytech.github.io/substrate/master/pallet_treasury/index.html))
diff --git a/docs/maintain/maintain-errors.md b/docs/maintain/maintain-errors.md
index c2ff7afb7e4..1f339ea80ff 100644
--- a/docs/maintain/maintain-errors.md
+++ b/docs/maintain/maintain-errors.md
@@ -77,7 +77,7 @@ The table below lists the most commonly encountered errors and ways to resolve t
 
 :::note Future Error
 
-This error will not cause the TX to be discarded immediately. Instead, it will be sent to the [futures queue](https://docs.substrate.io/v3/concepts/tx-pool/#sorting), where it will wait to be executed at the correct place in the nonce sequence OR it will get discarded due to some other error (ex. the validity period expires).*
+This error will not cause the TX to be discarded immediately. Instead, it will be sent to the [futures queue](https://docs.substrate.io/main-docs/fundamentals/transaction-lifecycle/), where it will wait to be executed at the correct place in the nonce sequence OR it will get discarded due to some other error (ex. the validity period expires).*
 
 :::
 
diff --git a/docs/maintain/maintain-guides-how-to-chill.md b/docs/maintain/maintain-guides-how-to-chill.md
index 68111de7819..7a12cdd79ac 100644
--- a/docs/maintain/maintain-guides-how-to-chill.md
+++ b/docs/maintain/maintain-guides-how-to-chill.md
@@ -70,5 +70,5 @@ An unbounded and unlimited number of nominators and validators in Polkadot's NPo
 
 For instance, let us consider a scenario where the minimum staking requirement for nominators is changed from 80 DOTs to 120 DOTs. An account that was actively nominating with 80 DOTs before this update would still keep receiving staking rewards. To handle this corner case, the `chill_other` extrinsic was incorporated which also helps to keep things backwards compatible and safe. The `chill_other` extrinsic is permissionless and any third party user can target it on an account where the minimum active bond is not satisfied, and chill that account. The list of addresses of all the active validators and their nominators can be viewed by running [validator stats](https://github.com/w3f/validator-stats) script.
 
-[chill extrinsic]: https://docs.substrate.io/rustdocs/latest/pallet_staking/pallet/enum.Call.html#variant.chill
+[chill extrinsic]: https://paritytech.github.io/substrate/master/pallet_staking/pallet/enum.Call.html#variant.chill
 [accounts]: ../learn/learn-staking.md#accounts
diff --git a/docs/maintain/maintain-sync.md b/docs/maintain/maintain-sync.md
index 3b184f60bf0..35f4b87d8da 100644
--- a/docs/maintain/maintain-sync.md
+++ b/docs/maintain/maintain-sync.md
@@ -190,7 +190,7 @@ values={[
 ## Get Substrate
 
 Follow instructions as outlined
-[here](https://docs.substrate.io/v3/getting-started/overview/) - note that Windows users will
+[here](https://docs.substrate.io/quick-start/) - note that Windows users will
 have their work cut out for them. It's better to use a virtual machine instead.
 
 Test if the installation was successful by running `cargo --version`.