change all 301 moved permanently

Author: 0xlukem

develop/interoperability/send-messages.md

@@ -86,7 +86,7 @@ For further information about the `send` extrinsic, see the [`pallet-xcm` docume
 
 The [`XcmRouter`](https://paritytech.github.io/polkadot-sdk/master/pallet_xcm/pallet/trait.Config.html#associatedtype.XcmRouter){target=\_blank} is a critical component the XCM pallet requires to facilitate sending XCM messages. It defines where messages can be sent and determines the appropriate XCM transport protocol for the operation.
 
-For instance, the Kusama network employs the [`ChildParachainRouter`](https://paritytech.github.io/polkadot-sdk/master/polkadot_runtime_common/xcm_sender/struct.ChildParachainRouter.html){target=\_blank}, which restricts routing to [Downward Message Passing (DMP)](https://wiki.polkadot.network/docs/learn-xcm-transport#dmp-downward-message-passing){target=\_blank} from the relay chain to parachains, ensuring secure and controlled communication.
+For instance, the Kusama network employs the [`ChildParachainRouter`](https://paritytech.github.io/polkadot-sdk/master/polkadot_runtime_common/xcm_sender/struct.ChildParachainRouter.html){target=\_blank}, which restricts routing to [Downward Message Passing (DMP)](https://wiki.polkadot.network/learn/learn-xcm-transport/#dmp-downward-message-passing){target=\_blank} from the relay chain to parachains, ensuring secure and controlled communication.
 
 ```rust
 --8<-- 'https://raw.githubusercontent.com/polkadot-fellows/runtimes/refs/heads/main/relay/kusama/src/xcm_config.rs:122:125'

develop/interoperability/xcm-channels.md

@@ -7,7 +7,7 @@ description: Learn how Polkadot's cross-consensus messaging (XCM) channels conne
 
 ## Introduction
 
-Polkadot is designed to enable interoperability between its connected parachains. At the core of this interoperability is the [Cross-Consensus Message Format (XCM)](https://wiki.polkadot.network/docs/learn-xcm), a standard language that allows parachains to communicate and interact with each other.
+Polkadot is designed to enable interoperability between its connected parachains. At the core of this interoperability is the [Cross-Consensus Message Format (XCM)](https://docs.polkadot.com/develop/interoperability/intro-to-xcm/), a standard language that allows parachains to communicate and interact with each other.
 
 The network-layer protocol responsible for delivering XCM-formatted messages between parachains is the Cross-Chain Message Passing (XCMP) protocol. XCMP maintains messaging queues on the relay chain, serving as a bridge to facilitate cross-chain interactions.
 

develop/interoperability/xcm-config.md

@@ -37,7 +37,7 @@ Each configuration item is explained below, detailing the associated type’s pu
     - `Dispatchable` - indicates it can be executed in the runtime
     - `GetDispatchInfo` - provides weight details, determining how long execution takes
 
-- [**`XcmSender`**](https://paritytech.github.io/polkadot-sdk/master/staging_xcm_executor/trait.Config.html#associatedtype.XcmSender){target=\_blank} - implements the [`SendXcm`](https://paritytech.github.io/polkadot-sdk/master/staging_xcm/v4/trait.SendXcm.html){target=\_blank} trait, specifying how the executor sends XCMs using transport layers (e.g., UMP for relay chains or XCMP for sibling chains). If a runtime lacks certain transport layers, such as [HRMP](https://wiki.polkadot.network/docs/learn-xcm-transport#hrmp-xcmp-lite){target=\_blank} (or [XCMP](https://wiki.polkadot.network/docs/learn-xcm-transport#xcmp-cross-consensus-message-passing-design-summary){target=\_blank})
+- [**`XcmSender`**](https://paritytech.github.io/polkadot-sdk/master/staging_xcm_executor/trait.Config.html#associatedtype.XcmSender){target=\_blank} - implements the [`SendXcm`](https://paritytech.github.io/polkadot-sdk/master/staging_xcm/v4/trait.SendXcm.html){target=\_blank} trait, specifying how the executor sends XCMs using transport layers (e.g., UMP for relay chains or XCMP for sibling chains). If a runtime lacks certain transport layers, such as [HRMP](https://wiki.polkadot.network/learn/learn-xcm-transport/#hrmp-xcmp-lite){target=\_blank} (or [XCMP](https://wiki.polkadot.network/learn/learn-xcm-transport/#xcmp-cross-consensus-message-passing-design-summary){target=\_blank})
     ```rust
     type XcmSender: SendXcm;
     ```
@@ -126,7 +126,7 @@ Each configuration item is explained below, detailing the associated type’s pu
     type PalletInstancesInfo: PalletsInfoAccess;
     ```
  <!-- I think `Holding Register` should be linked to https://wiki.polkadot.network/docs/learn/xcm/reference-glossary#holding-register, but since we will have our own glossary, I’m putting this as a TODO -->
-- [**`MaxAssetsIntoHolding`**](https://paritytech.github.io/polkadot-sdk/master/staging_xcm_executor/trait.Config.html#associatedtype.MaxAssetsIntoHolding){target=\_blank} - limits the number of assets in the [Holding register](https://wiki.polkadot.network/docs/learn/xcm/reference-glossary#holding-register){target=\_blank}. At most, twice this limit can be held under worst-case conditions
+- [**`MaxAssetsIntoHolding`**](https://paritytech.github.io/polkadot-sdk/master/staging_xcm_executor/trait.Config.html#associatedtype.MaxAssetsIntoHolding){target=\_blank} - limits the number of assets in the [Holding register](https://wiki.polkadot.network/learn/learn-xcm/#holding-register){target=\_blank}. At most, twice this limit can be held under worst-case conditions
     ```rust
     type MaxAssetsIntoHolding: Get<u32>;
     ```

develop/networks.md

@@ -271,4 +271,4 @@ Paseo is a decentralised, community run, stable testnet for parachain and dapp d
 
 ## Additional Resources
 
-- [**Polkadot Fellowship runtimes repository**](https://github.com/polkadot-fellows/runtimes){target=\_blank} - find a collection of runtimes for Polkadot, Kusama, and their system-parachains as maintained by the community via the [Polkadot Technical Fellowship](https://wiki.polkadot.network/docs/learn-polkadot-technical-fellowship){target=\_blank}
+- [**Polkadot Fellowship runtimes repository**](https://github.com/polkadot-fellows/runtimes){target=\_blank} - find a collection of runtimes for Polkadot, Kusama, and their system-parachains as maintained by the community via the [Polkadot Technical Fellowship](https://wiki.polkadot.network/learn/learn-polkadot-technical-fellowship/){target=\_blank}

develop/parachains/deployment/index.md

@@ -55,7 +55,7 @@ flowchart TD
 
 - **Acquire coretime** - to build on top of the Polkadot network, users need to acquire coretime (either on-demand or in bulk) to access the computational resources of the relay chain. This allows for the secure validation of parachain blocks through a randomized selection of relay chain validators
 
-If you’re building a standalone blockchain (solochain) that won’t connect to Polkadot as a parachain, you can skip the preceding step, as there’s no need to acquire coretime or implement [Cumulus](https://wiki.polkadot.network/docs/build-pdk#cumulus){target=\_blank}.
+If you’re building a standalone blockchain (solochain) that won’t connect to Polkadot as a parachain, you can skip the preceding step, as there’s no need to acquire coretime or implement [Cumulus](https://docs.polkadot.com/develop/parachains/#cumulus){target=\_blank}.
 
 - **Launch and monitor** - once everything is configured, you can launch the blockchain, initiating the network with your chain spec and Wasm runtime. Validators or collators will begin producing blocks, and the network will go live. Post-launch, monitoring is vital to ensuring network health—tracking block production, node performance, and overall security
 

develop/parachains/deployment/obtain-coretime.md

@@ -52,7 +52,7 @@ Before obtaining coretime, ensure you have:
 Bulk coretime provides several advantages:
 
 - Monthly allocation of resources
-- Guaranteed block production slots (every 12 seconds, or 6 seconds with [Asynchronous Backing](https://wiki.polkadot.network/docs/learn-async-backing#asynchronous-backing){target=\_blank})
+- Guaranteed block production slots (every 12 seconds, or 6 seconds with [Asynchronous Backing](https://wiki.polkadot.network/learn/learn-async-backing/#asynchronous-backing){target=\_blank})
 - Priority renewal rights
 - Protection against price fluctuations
 - Ability to split and resell unused coretime
@@ -66,7 +66,7 @@ To purchase bulk coretime:
 
 After successfully obtaining coretime, your parachain will automatically start producing blocks at regular intervals.
 
-For current marketplaces and pricing, consult the [Coretime Marketplaces](https://wiki.polkadot.network/docs/learn-guides-coretime-marketplaces){target=\_blank} page on the Polkadot Wiki.
+For current marketplaces and pricing, consult the [Coretime Marketplaces](https://wiki.polkadot.network/learn/learn-guides-coretime-marketplaces/){target=\_blank} page on the Polkadot Wiki.
 
 ### On-demand Coretime
 

develop/parachains/install-polkadot-sdk.md

@@ -237,7 +237,7 @@ To prepare a development environment using WSL:
 
     If you have Microsoft Windows 10, version 2004 (Build 19041 and higher), or Microsoft Windows 11, WSL is available by default and you can continue to the next step.
 
-    If you have an older version of Microsoft Windows installed, see the [WSL manual installation steps for older versions](https://docs.microsoft.com/en-us/windows/wsl/install-manual){target=\_blank}. If you are installing on an older version of Microsoft Windows, you can download and install WLS 2 if your computer has Windows 10, version 1903 or higher
+    If you have an older version of Microsoft Windows installed, see the [WSL manual installation steps for older versions](https://learn.microsoft.com/en-us/windows/wsl/install-manual){target=\_blank}. If you are installing on an older version of Microsoft Windows, you can download and install WLS 2 if your computer has Windows 10, version 1903 or higher
 
 2. Select **Windows PowerShell** or **Command Prompt** from the **Start** menu, right-click, then **Run as administrator**
 
@@ -262,7 +262,7 @@ To prepare a development environment using WSL:
 
     Restarting the computer is required to start the installation of the Linux distribution. It can take a few minutes for the installation to complete after you restart.
 
-    For more information about setting up WSL as a development environment, see the [Set up a WSL development environment](https://docs.microsoft.com/en-us/windows/wsl/setup/environment){target=\_blank} docs
+    For more information about setting up WSL as a development environment, see the [Set up a WSL development environment](https://learn.microsoft.com/en-us/windows/wsl/setup/environment){target=\_blank} docs
 
 ### Install Required Packages and Rust {: #install-required-packages-and-rust-windows }
 

develop/smart-contracts/evm/index.md

@@ -12,7 +12,7 @@ The Polkadot ecosystem supports Ethereum-compatible smart contracts through both
 
 With EVM support, developers can build decentralized applications (dApps) using familiar tools, languages like Solidity, and established smart contract standards, all while taking advantage of Polkadot's unique features, such as scalability and cross-chain interoperability.
 
-Whether deploying existing Ethereum contracts on Polkadot or creating new applications, this section provides the resources you need to get started. Learn how to leverage popular EVM tools, such as [Remix](https://remix.ethereum.org/){target=\_blank} and [Ethers.js](https://docs.ethers.org/){target=\_blank}, to integrate Ethereum-compatible smart contract functionality into the Polkadot ecosystem.
+Whether deploying existing Ethereum contracts on Polkadot or creating new applications, this section provides the resources you need to get started. Learn how to leverage popular EVM tools, such as [Remix](https://remix.ethereum.org/){target=\_blank} and [Ethers.js](https://docs.ethers.org/v6/){target=\_blank}, to integrate Ethereum-compatible smart contract functionality into the Polkadot ecosystem.
 
 - Want to learn more? Jump to [In This Section](#in-this-section) to get started
 - Ready to start coding? Check out the [Deploy a Smart Contract](#deploy-a-smart-contract) section to get started

develop/smart-contracts/evm/parachain-contracts.md

@@ -76,7 +76,7 @@ The diagram illustrates the layered architecture of Astar Network: at the top, d
 |  EVM Chain ID   | 81                                                                                               |
 | Public RPC URLs | <pre>```https://evm.shibuya.astar.network```</pre>                                               |
 | Public WSS URLs | <pre>```wss://evm.shibuya.astar.network```</pre>                                                 |
-| Block Explorer  | [Shibuya Blockscout](https://blockscout.com/shibuya){target=\_blank}                             |
+| Block Explorer  | [Shibuya Blockscout](https://shibuya.blockscout.com/){target=\_blank}                             |
 |   Faucet Link   | [Faucet - Astar Docs](https://docs.astar.network/docs/build/environment/faucet/){target=\_blank} |
 
 ### Moonbeam
@@ -188,7 +188,7 @@ The diagram illustrates Acala's unique EVM+ architecture, which extends beyond s
 | Public RPC URLs | <pre>```https://eth-rpc-tc9.aca-staging.network```</pre>                             |
 | Public WSS URLs | <pre>```wss://tc7-eth.aca-dev.network```</pre>                                       |
 | Block Explorer  | [Mandala Blockscout](https://blockscout.mandala.aca-staging.network){target=\_blank} |
-|   Faucet Link   | [Mandala Faucet](https://discord.gg/5JJgXKSznc){target=\_blank}                      |
+|   Faucet Link   | [Mandala Faucet](https://discord.com/invite/5JJgXKSznc){target=\_blank}                      |
 
 ## EVM Developer Tools
 

develop/smart-contracts/overview.md

@@ -65,7 +65,7 @@ Polkadot's primary purpose is to provide security for parachains that connect to
 The Polkadot SDK supports multiple smart contract execution environments:
 
 - **EVM** - through [Frontier](https://github.com/polkadot-evm/frontier){target=\_blank}. It consists of a full Ethereum JSON RPC compatible client, an Ethereum emulation layer, and a [Rust-based EVM](https://github.com/rust-ethereum/evm){target=\_blank}. This is used by chains like [Acala](https://acala.network/){target=\_blank}, [Astar](https://astar.network/){target=\_blank}, [Moonbeam](https://moonbeam.network){target=\_blank} and more
-- **Wasm** - through the [Contracts pallet](https://github.com/paritytech/polkadot-sdk/blob/master/substrate/frame/contracts/){target=\_blank}. [ink!](https://use.ink/){target=\_blank} is a smart contract language that provides a compiler to Wasm. Wasm contracts can be used by chains like [Astar](https://astar.network/){target=\_blank}
+- **Wasm** - through the [Contracts pallet](https://github.com/paritytech/polkadot-sdk/tree/master/substrate/frame/contracts){target=\_blank}. [ink!](https://use.ink/){target=\_blank} is a smart contract language that provides a compiler to Wasm. Wasm contracts can be used by chains like [Astar](https://astar.network/){target=\_blank}
 <!-- This content is temporarily hidden and has been commented out to ensure it is preserved. -->
 <!-- - **PolkaVM** - a cutting-edge virtual machine tailored to optimize smart contract execution on Polkadot. Unlike traditional EVMs, PolkaVM is built with a [RISC-V-based register architecture](https://en.wikipedia.org/wiki/RISC-V){target=\_blank} for increased performance and scalability -->