From cbd9c22a5589f02a1e14217a736f1fe43181d049 Mon Sep 17 00:00:00 2001 From: Sacha Lansky Date: Thu, 5 Oct 2023 13:40:44 +0200 Subject: [PATCH] fix broken links --- .../en/docs/learn/light-clients-in-substrate-connect.md | 2 +- content/md/en/docs/reference/frame-macros.md | 6 +++--- .../consensus-models/create-a-hybrid-node.md | 2 +- .../pallet-design/implement-lockable-currency.md | 8 ++++---- .../how-to-guides/parachains/connect-to-a-relay-chain.md | 4 ++-- .../use-macros-in-a-custom-pallet.md | 2 +- .../en/docs/tutorials/collectibles-workshop/01-prepare.md | 2 +- .../integrate-with-tools/integrate-a-light-client-node.md | 2 +- 8 files changed, 14 insertions(+), 14 deletions(-) diff --git a/content/md/en/docs/learn/light-clients-in-substrate-connect.md b/content/md/en/docs/learn/light-clients-in-substrate-connect.md index db4a718ec..45b6cff20 100644 --- a/content/md/en/docs/learn/light-clients-in-substrate-connect.md +++ b/content/md/en/docs/learn/light-clients-in-substrate-connect.md @@ -43,7 +43,7 @@ A few of the key benefits include: You can use Substrate Connect to connect to any Substrate-based blockchain. However, you must specify the correct name of the chain that you want to connect to. -There are a few well-known chain names that are defined for the [`WellKnownChain`](https://paritytech.github.io/substrate-connect/api/enums/connect_src.WellKnownChain.html) enumeration type. +There are a few well-known chain names that are defined for the [`WellKnownChain`](https://paritytech.github.io/substrate-connect/api/enums/_substrate_connect.WellKnownChain.html) enumeration type. You can connect to the following public blockchain networks using the name listed: diff --git a/content/md/en/docs/reference/frame-macros.md b/content/md/en/docs/reference/frame-macros.md index 008a69d72..929110ea4 100644 --- a/content/md/en/docs/reference/frame-macros.md +++ b/content/md/en/docs/reference/frame-macros.md @@ -405,9 +405,9 @@ $vis type $StorageName<$some_generic> $optional_where_clause For more information, see the Rust documentation for [pallet::storage](https://paritytech.github.io/substrate/master/frame_support/attr.pallet.html#storage-palletstorage-optional) and the following storage data structures: -- [StorageDoubleMap](https://paritytech.github.io/substrate/master/frame_support/pallet_prelude/struct.StorageDoubleMap.html) -- [StorageMap](https://paritytech.github.io/substrate/master/frame_support/pallet_prelude/struct.StorageMap.html#implementations) -- [StorageValue](https://paritytech.github.io/substrate/master/frame_support/pallet_prelude/struct.StorageValue.html) +- [StorageDoubleMap](https://paritytech.github.io/polkadot-sdk/master/frame_support/storage/types/struct.StorageDoubleMap.html) +- [StorageMap](https://paritytech.github.io/polkadot-sdk/master/frame_support/storage/types/struct.StorageMap.html) +- [StorageValue](https://paritytech.github.io/polkadot-sdk/master/frame_support/storage/types/struct.StorageValue.html) ### #[pallet::type_value] diff --git a/content/md/en/docs/reference/how-to-guides/consensus-models/create-a-hybrid-node.md b/content/md/en/docs/reference/how-to-guides/consensus-models/create-a-hybrid-node.md index 0fedff806..2873c0fb8 100644 --- a/content/md/en/docs/reference/how-to-guides/consensus-models/create-a-hybrid-node.md +++ b/content/md/en/docs/reference/how-to-guides/consensus-models/create-a-hybrid-node.md @@ -29,7 +29,7 @@ Customize the consensus mechanisms of a Substrate chain. We begin by creating the block import for Grandpa. In addition to the block import itself, we get back a `grandpa_link`. This link is a channel over which the block import can communicate with the background task that actually casts Grandpa votes. -The [details of the Grandpa protocol](https://research.web3.foundation/en/latest/polkadot/finality.html) are beyond the scope of this guide. +The [details of the Grandpa protocol](https://research.web3.foundation/Polkadot/protocols/finality) are beyond the scope of this guide. In `node/src/service.rs`, create the Grandpa block import: diff --git a/content/md/en/docs/reference/how-to-guides/pallet-design/implement-lockable-currency.md b/content/md/en/docs/reference/how-to-guides/pallet-design/implement-lockable-currency.md index d6ffd24d6..5a552830d 100644 --- a/content/md/en/docs/reference/how-to-guides/pallet-design/implement-lockable-currency.md +++ b/content/md/en/docs/reference/how-to-guides/pallet-design/implement-lockable-currency.md @@ -9,7 +9,7 @@ keywords: --- This guide shows you how to write a pallet that allows users to lock funds for staking and voting. -The [`LockableCurrency`](https://paritytech.github.io/substrate/master/frame_support/traits/trait.LockableCurrency.html) trait is useful in the context of economic systems that enforce accountability by collateralizing fungible resources. +The [`LockableCurrency`](https://paritytech.github.io/polkadot-sdk/master/frame_support/traits/tokens/currency/trait.LockableCurrency.html) trait is useful in the context of economic systems that enforce accountability by collateralizing fungible resources. You can use the Substrate [staking pallet](https://paritytech.github.io/substrate/master/pallet_staking/index.html) to manage locked funds in time-based increments. In this guide, we will implement the `set_lock`, `extend_lock` and `remove_lock` methods in our own custom pallet. @@ -22,7 +22,7 @@ You can use the template pallet in the [node template](https://github.com/substr ## Declare the necessary dependencies -The methods from [`LockableCurrency`](https://paritytech.github.io/substrate/master/frame_support/traits/trait.LockableCurrency.html) require us to import a few traits from `frame_support`. +The methods from [`LockableCurrency`](https://paritytech.github.io/polkadot-sdk/master/frame_support/traits/tokens/currency/trait.LockableCurrency.html) require us to import a few traits from `frame_support`. 1. Ensure you have the following traits imported in the top section of your pallet: @@ -162,5 +162,5 @@ The required methods are: ## Related material - [Currency trait](https://paritytech.github.io/substrate/master/frame_support/traits/tokens/currency/trait.Currency.html) -- [LockableCurrency](https://paritytech.github.io/substrate/master/frame_support/traits/trait.LockableCurrency.html) -- [LockIdentifier](https://paritytech.github.io/substrate/master/frame_support/traits/type.LockIdentifier.html) +- [LockableCurrency](https://paritytech.github.io/polkadot-sdk/master/frame_support/traits/tokens/currency/trait.LockableCurrency.html) +- [LockIdentifier](https://paritytech.github.io/polkadot-sdk/master/frame_support/traits/tokens/currency/type.LockIdentifier.html) diff --git a/content/md/en/docs/reference/how-to-guides/parachains/connect-to-a-relay-chain.md b/content/md/en/docs/reference/how-to-guides/parachains/connect-to-a-relay-chain.md index e0fc92b73..dc8402838 100644 --- a/content/md/en/docs/reference/how-to-guides/parachains/connect-to-a-relay-chain.md +++ b/content/md/en/docs/reference/how-to-guides/parachains/connect-to-a-relay-chain.md @@ -180,8 +180,8 @@ pub const fn deposit(items: u32, bytes: u32) -> Balance {} You can find this function for each relay chain in the Polkadot repository. For example: -- [Kusama](https://github.com/paritytech/polkadot-sdk/blob/master/polkadot/runtime/kusama/constants/src/lib.rs) -- [Polkadot](https://github.com/paritytech/polkadot-sdk/blob/master/polkadot/runtime/polkadot/constants/src/lib.rs) +- [Kusama](https://github.com/polkadot-fellows/runtimes/blob/main/relay/kusama/constants/src/lib.rs) +- [Polkadot](https://github.com/polkadot-fellows/runtimes/blob/main/relay/polkadot/constants/src/lib.rs) - [Rococo](https://github.com/paritytech/polkadot-sdk/blob/master/polkadot/runtime/rococo/constants/src/lib.rs) - [Westend](https://github.com/paritytech/polkadot-sdk/blob/master/polkadot/runtime/westend/constants/src/lib.rs) diff --git a/content/md/en/docs/tutorials/build-application-logic/use-macros-in-a-custom-pallet.md b/content/md/en/docs/tutorials/build-application-logic/use-macros-in-a-custom-pallet.md index 7ace105f4..c6aa96a7a 100644 --- a/content/md/en/docs/tutorials/build-application-logic/use-macros-in-a-custom-pallet.md +++ b/content/md/en/docs/tutorials/build-application-logic/use-macros-in-a-custom-pallet.md @@ -228,7 +228,7 @@ To implement the errors for the proof-of-existence pallet: To add a new claim to the blockchain, the proof-of-existence pallet requires a storage mechanism. To address this requirement, you can create a key-value map, where each claim points to the owner and the block number when the claim was made. -To create this key-value map, you can use the FRAME [`StorageMap`](https://paritytech.github.io/substrate/master/frame_support/pallet_prelude/struct.StorageMap.html). +To create this key-value map, you can use the FRAME [`StorageMap`](https://paritytech.github.io/polkadot-sdk/master/frame_support/storage/types/struct.StorageMap.html). To implement storage for the proof-of-existence pallet: diff --git a/content/md/en/docs/tutorials/collectibles-workshop/01-prepare.md b/content/md/en/docs/tutorials/collectibles-workshop/01-prepare.md index 3f9b7b990..911b0d1d6 100644 --- a/content/md/en/docs/tutorials/collectibles-workshop/01-prepare.md +++ b/content/md/en/docs/tutorials/collectibles-workshop/01-prepare.md @@ -58,7 +58,7 @@ If you don't have a preferred IDE, Visual Studio Code is a good choice. To interact with the blockchain and test your work as you build the Substrate collectibles application, you'll need a browser-based application that can connect to the Substrate node. For the workshop, you can connect to the node from the [Polkadot/Substrate Portal](https://polkadot.js.org/apps/) if you have Chrome or a Chromium-based browser. -- [ ] [Google Chrome](https://www.google.com/chrome/) or a Chromium-based browser, such as [Brave](https://brave.com/download/), [Microsoft Edge](https://www.microsoft.com/en-us/edge?form=MA13FJ&exp=e00), [Opera](https://www.opera.com/download), or [Vivaldi](https://vivaldi.com/download/). +- [ ] [Google Chrome](https://www.google.com/chrome/) or a Chromium-based browser, such as [Brave](https://brave.com/download/), [Microsoft Edge](https://www.microsoft.com/en-us/edge?ep=79&form=MA13KE&es=23), [Opera](https://www.opera.com/download), or [Vivaldi](https://vivaldi.com/download/). If you use a more restrictive browser—such as Firefox—you might find that connections between the Polkadot/Substrate Portal and the node are blocked for security or privacy reasons. diff --git a/content/md/en/docs/tutorials/integrate-with-tools/integrate-a-light-client-node.md b/content/md/en/docs/tutorials/integrate-with-tools/integrate-a-light-client-node.md index 163d8e5b4..7e2c10de0 100644 --- a/content/md/en/docs/tutorials/integrate-with-tools/integrate-a-light-client-node.md +++ b/content/md/en/docs/tutorials/integrate-with-tools/integrate-a-light-client-node.md @@ -30,7 +30,7 @@ By completing this tutorial, you will accomplish the following objectives: Before the light client can connect to a network, you must have a web application that specifies the network the light client should connect to, the nodes for it to communicate with, and the consensus-critical state it must have at genesis. This information is available in the [chain specification](/build/chain-spec/) file for the network. -Substrate Connect is preconfigured to recognize several chains that are defined in the [WellKnownChain](https://paritytech.github.io/substrate-connect/api/enums/connect_src.WellKnownChain.html) enumeration list. +Substrate Connect is preconfigured to recognize several chains that are defined in the [WellKnownChain](https://paritytech.github.io/substrate-connect/api/enums/_substrate_connect.WellKnownChain.html) enumeration list. These well-known chains are: - Polkadot identified as `polkadot`