From 4bf5da4e1e361941351054463e65bb08f1083883 Mon Sep 17 00:00:00 2001 From: divdeploy <166095818+divdeploy@users.noreply.github.com> Date: Sat, 6 Apr 2024 02:01:11 +0800 Subject: [PATCH] docs: fix some comments (#5762) Signed-off-by: divdeploy --- docs/learn/learn-guides-identity.md | 2 +- docs/learn/learn-runtime-upgrades.md | 2 +- docs/learn/xcm/journey/holding-modifiers.md | 2 +- docs/learn/xcm/journey/queries.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/learn/learn-guides-identity.md b/docs/learn/learn-guides-identity.md index a39ee6b3c6b6..8812d90363d1 100644 --- a/docs/learn/learn-guides-identity.md +++ b/docs/learn/learn-guides-identity.md @@ -133,7 +133,7 @@ Setting an Identity is not possible on Ledger app yet, but as a workaround, you [set the identity for an on-chain account ](../learn/learn-identity.md#setting-an-identity) and then use it to set a sub-identity to your Ledger account. -- Go to https://polkadot.js.org/apps/#/accounts. Click on the three vertical dots correponding to +- Go to https://polkadot.js.org/apps/#/accounts. Click on the three vertical dots corresponding to the account to which you already set identity. You should see an option to set onchain sub-identities. Click on it. diff --git a/docs/learn/learn-runtime-upgrades.md b/docs/learn/learn-runtime-upgrades.md index 1c29eb449ab5..85bb0f31e139 100644 --- a/docs/learn/learn-runtime-upgrades.md +++ b/docs/learn/learn-runtime-upgrades.md @@ -140,7 +140,7 @@ should monitor the Relay Chain as follows to know when the next runtime upgrade 2. Ongoing referenda will have an `enactment` field under `referenda.ReferendumInfoFor` storage. This is the block number that, if passed, the system will attempt to schedule the inner proposal's execution for. Note that there are some constraints like a minimum enactment period - that could result in the proposal's execution occuring later. It is not possible for the proposal + that could result in the proposal's execution occurring later. It is not possible for the proposal to enact _before_ this block number. 3. Check also for `referenda (DecisionDepositPlaced)` events where `index` matches the one previously found. This means that the required deposit has been placed. diff --git a/docs/learn/xcm/journey/holding-modifiers.md b/docs/learn/xcm/journey/holding-modifiers.md index 903689aa2df8..1d206221460f 100644 --- a/docs/learn/xcm/journey/holding-modifiers.md +++ b/docs/learn/xcm/journey/holding-modifiers.md @@ -69,7 +69,7 @@ The `give` field indicates the maximum number of assets that can be removed from register. The `want` field indicates the minimum amount of assets which `give` should be exchanged for. We -should at a mimimum get the assets in `want` for the execution of the instruction not to fail. +should at a minimum get the assets in `want` for the execution of the instruction not to fail. If the `maximal` field is `true`, then we prefer to give as much as possible up to the limit of `give` and receive accordingly more assets then stated in `want`. If the `maximal` field is `false`, diff --git a/docs/learn/xcm/journey/queries.md b/docs/learn/xcm/journey/queries.md index 89ffc00ed3f4..afd26dcdcdba 100644 --- a/docs/learn/xcm/journey/queries.md +++ b/docs/learn/xcm/journey/queries.md @@ -45,7 +45,7 @@ QueryResponse { querier: Option, } -// Reponse Struct +// Response Struct pub enum Response { /// No response. Serves as a neutral default. Null,