- ⚠️ WARNING: This page contains outdated information. Please refer to the Rust docs for the most up-to-date documentation on this topic.
+ Please refer to the Rust docs for the most up-to-date documentation on this topic.
@@ -19,7 +19,7 @@ As you learned in [Chain specification](/build/chain-spec/), the chain specifica
However, the chain specification doesn't create the storage items that get initialized when you start a node.
Instead, the storage items are defined in the pallets included in the runtime as described in [Runtime storage](/build/runtime-storage/).
-After you create storage items for the runtime, you can choose whether they should be set to some initial value as part of the genesis configuration and included in the genesis block.
+After you create storage items for the runtime, you can choose whether they should be set to some initial value as part of the genesis configuration and included in the genesis block.
To specify the storage items that you want to set an initial state for, Substrate provides two specialized FRAME attribute macros.
The macros you can use to initialize storage items as part of the genesis configuration for a chain are:
@@ -120,12 +120,17 @@ All of the `GenesisConfig` types for the pallets that included in the constructi
The aggregated `RuntimeGenesisConfig` implements the [`BuildStorage`](https://paritytech.github.io/substrate/master/sp_runtime/trait.BuildStorage.html) trait to build all of the initial storage items for the runtime.
For example, the node template runtime builds storage items for the following pallets that have a `RuntimeGenesisConfig` specified by default:
-- [System pallet](#system-pallet)
-- [Aura pallet](#aura-pallet)
-- [Grandpa pallet](#grandpa-pallet)
-- [Balances pallet](#balances-pallet)
-- [TransactionPayment pallet](#transactionpayment-pallet)
-- [Sudo pallet](#sudo-pallet)
+- [Configure a simple storage value](#configure-a-simple-storage-value)
+ - [Configure macros in the pallet](#configure-macros-in-the-pallet)
+ - [Configure the chain specification](#configure-the-chain-specification)
+- [Adding genesis configuration to the runtime](#adding-genesis-configuration-to-the-runtime)
+ - [System pallet](#system-pallet)
+ - [Aura pallet](#aura-pallet)
+ - [Grandpa pallet](#grandpa-pallet)
+ - [Balances pallet](#balances-pallet)
+ - [TransactionPayment pallet](#transactionpayment-pallet)
+ - [Sudo pallet](#sudo-pallet)
+- [Initialize storage items within a pallet](#initialize-storage-items-within-a-pallet)
### System pallet
diff --git a/content/md/en/docs/build/origins.md b/content/md/en/docs/build/origins.md
index c0b9874c4..428755e91 100644
--- a/content/md/en/docs/build/origins.md
+++ b/content/md/en/docs/build/origins.md
@@ -5,6 +5,10 @@ keywords:
- origins
---
+
+ Please refer to the Rust docs for the most up-to-date documentation on this topic.
+
+
The runtime origin is used by dispatchable functions to check where a call has come from.
## Raw origins
diff --git a/content/md/en/docs/build/pallet-coupling.md b/content/md/en/docs/build/pallet-coupling.md
index 4a1db10c1..7e0d17672 100644
--- a/content/md/en/docs/build/pallet-coupling.md
+++ b/content/md/en/docs/build/pallet-coupling.md
@@ -6,6 +6,10 @@ keywords:
- pallet design
---
+
+ Please refer to the Rust Docs for the most up-to-date documentation on this topic.
+
+
The term **coupling** is often used to describe the degree to which two software modules depend on each other.
For example, in object-oriented programming tight coupling and loose coupling are used to describe the relationship between objects classes:
diff --git a/content/md/en/docs/build/randomness.md b/content/md/en/docs/build/randomness.md
index c5250357c..78669809d 100644
--- a/content/md/en/docs/build/randomness.md
+++ b/content/md/en/docs/build/randomness.md
@@ -41,7 +41,7 @@ Substrate includes two examples of how to implement the `Randomness` trait in pa
You should only use this pallet in applications with low security requirements or when testing randomness-consuming applications.
You shouldn't use this pallet in a production environment.
-= The [BABE pallet](https://paritytech.github.io/substrate/master/pallet_babe/index.html) provides randomness by using verifiable random functions.
+- The [BABE pallet](https://paritytech.github.io/substrate/master/pallet_babe/index.html) provides randomness by using verifiable random functions.
This pallet provides production-grade randomness, and is used in Polkadot.
If you select this pallet as the source of randomness your blockchain must use the blind assignment of blockchain extension ([BABE](/reference/glossary/#blind-assignment-of-blockchain-extension-babe)) slot-based consensus for producing blocks.
diff --git a/content/md/en/docs/build/remote-procedure-calls.md b/content/md/en/docs/build/remote-procedure-calls.md
index 32027e13e..896c954ae 100644
--- a/content/md/en/docs/build/remote-procedure-calls.md
+++ b/content/md/en/docs/build/remote-procedure-calls.md
@@ -6,6 +6,10 @@ keywords:
- frontend
---
+
+ Please refer to the Rust docs for the most up-to-date documentation on this topic.
+
+
Remote procedure calls, or RPC methods, are a way for an external program—for example, a browser or front-end application—to communicate with a Substrate node.
In general, these methods enable an RPC client to connect to an RPC server endpoint to request some type of service.
For example, you might use an RPC method to read a stored value, submit a transaction, or request information about the chain a node is connected to.
diff --git a/content/md/en/docs/build/tx-weights-fees.md b/content/md/en/docs/build/tx-weights-fees.md
index 7baf13cd2..1a41272e7 100644
--- a/content/md/en/docs/build/tx-weights-fees.md
+++ b/content/md/en/docs/build/tx-weights-fees.md
@@ -237,12 +237,12 @@ use frame_support:: {
Pays::Yes,
},
weights::Weight,
+};
#[pallet::weight(FunctionOf(
|args: (&Vec,)| args.0.len().saturating_mul(10_000),
)
]
-
fn handle_users(origin, calls: Vec) {
// Do something per user
}
diff --git a/content/md/en/docs/deploy/keys-and-network-operations.md b/content/md/en/docs/deploy/keys-and-network-operations.md
index 900b333ed..5f3968051 100644
--- a/content/md/en/docs/deploy/keys-and-network-operations.md
+++ b/content/md/en/docs/deploy/keys-and-network-operations.md
@@ -36,12 +36,12 @@ Session keys are private online keys that are used by validators to sign consens
Session keys must be available online to enable the validator to perform certain network operations.
These keys aren't used to control funds and they should only be used for their intended purpose.
-They can be changed regularly
-To create session keys, a validator node operator must use a controller account too generate a certificate signed with the session's public key.
+They can be changed regularly.
+To create session keys, a validator node operator must use a controller account to generate a certificate signed with the session's public key.
The certificate attests that the key acts on behalf of the validator's staking account and nominators.
After creating the session key, the validator node operator informs the chain that this key represents the controller key by
publishing the session certificate in a transaction on the chain.
-In most cases, node operators use the [Session](https://paritytech.github.io/substrate/master/pallet_session/index.html)) pallet to manage their session keys.
+In most cases, node operators use the [Session](https://paritytech.github.io/substrate/master/pallet_session/index.html) pallet to manage their session keys.
The [`SessionKeys`](https://paritytech.github.io/substrate/master/sp_session/index.html)
trait is a generic, indexable type and you can declare any number of session keys in the runtime.
diff --git a/content/md/en/docs/examples/quickstart/index.html b/content/md/en/docs/examples/quickstart/index.html
index 26839f0df..013743a9c 100644
--- a/content/md/en/docs/examples/quickstart/index.html
+++ b/content/md/en/docs/examples/quickstart/index.html
@@ -20,36 +20,36 @@
}
-
+
Display an account balance
Enter a development account address, then click Get Balance.