From 540ca2420fbd7958174587281cc60054a982c0c4 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Mon, 9 Dec 2024 10:18:43 +0100 Subject: [PATCH] applying prettier to entire repo (#6435) Co-authored-by: Polkadot-Kusama Bot --- docs/learn/learn-guides-identity.md | 4 ++-- docs/learn/learn-staking-advanced.md | 4 ++-- docs/learn/learn-validator.md | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/learn/learn-guides-identity.md b/docs/learn/learn-guides-identity.md index afeac7b2f05d..33dd225a3684 100644 --- a/docs/learn/learn-guides-identity.md +++ b/docs/learn/learn-guides-identity.md @@ -124,8 +124,8 @@ guidelines about clearing identities. **Clearing:** Users can clear their identity information and have their deposit returned. Clearing an identity also clears all sub accounts and returns their deposits. -**Killing:** It is possible to kill an identity that deems erroneous. This results in a slash of -the deposit. +**Killing:** It is possible to kill an identity that deems erroneous. This results in a slash of the +deposit. ## Setting Sub-Identities diff --git a/docs/learn/learn-staking-advanced.md b/docs/learn/learn-staking-advanced.md index acb148f29725..e84c63ca1c87 100644 --- a/docs/learn/learn-staking-advanced.md +++ b/docs/learn/learn-staking-advanced.md @@ -103,8 +103,8 @@ intents are submitted to the network, they are automatically put into each bag b of bonded tokens, but within each bag, those nodes are arranged based on the time they are inserted and not based on their stake (see figure below). When the nomination intent of 19 DOT is submitted, it gets placed at the last spot in the 2nd bag (shown in the green circle). The same scenario -applies for the node with 8 DOT (yellow circle) in the 3rd bag. Placing the node above all nodes with -a lesser stake requires an additional step (more on this later). +applies for the node with 8 DOT (yellow circle) in the 3rd bag. Placing the node above all nodes +with a lesser stake requires an additional step (more on this later). ![bags list example 1](../assets/bags-list-example-1.png) diff --git a/docs/learn/learn-validator.md b/docs/learn/learn-validator.md index f7cc1a7ddfb2..5377f01593b7 100644 --- a/docs/learn/learn-validator.md +++ b/docs/learn/learn-validator.md @@ -27,8 +27,8 @@ trust-free environment. Parachain validators (i.e. para-validators) participate to the [Parachain Phase of the AnV Protocol](./learn-parachains-protocol.md/#parachain-phase), and submit [candidate receipts](./learn-parachains-protocol.md/#candidate-receipts) to the relay chain -transaction queue so that a block author can include information on the parablock in a fork of -the relay chain. +transaction queue so that a block author can include information on the parablock in a fork of the +relay chain. Para-validators work in groups and are selected by the runtime in every epoch to validate parachain blocks for all parachains connected to the relay chain. The selected para-validators are part of the