Fix typos (#5207)

* fix typo * fix typo * fix typos * fix typos * fix typo * fix typo * fix typos * fix typos * Update docs/learn/learn-comparison-ethereum-2.md --------- Co-authored-by: Radha <[email protected]>
w3f · Sep 20, 2023 · 71730c8 · 71730c8
1 parent e0947ef
commit 71730c8
Show file tree

Hide file tree

Showing 8 changed files with 17 additions and 14 deletions.
diff --git a/docs/learn/learn-account-advanced.md b/docs/learn/learn-account-advanced.md
@@ -244,7 +244,7 @@ This is to showcase that the **SS58 address is based on the public key (aka "Acc
 
 The Subkey Tool's The
 [Inspecting Keys](https://docs.substrate.io/reference/command-line-tools/subkey/#inspecting-keys)
-the section explains how to use the `inspect` command to recalculate your key pair's public key and
+section explains how to use the `inspect` command to recalculate your key pair's public key and
 address.
 
 Start by inspecting your account's Polkadot address by running the inspect command against your

diff --git a/docs/learn/learn-account-generation.md b/docs/learn/learn-account-generation.md
@@ -242,7 +242,7 @@ password for an account created on the Polkadot-JS UI (i.e. a non-injected accou
 If you create an account first using Polkadot-JS Apps UI and then add it to the browser extension,
 you need to follow the
 [guidelines for the browser extension](#reset-password-using-the-browser-extension) to change the
-the password of such an account.
+password of such an account.
 
 :::
 

diff --git a/docs/learn/learn-account-multisig.md b/docs/learn/learn-account-multisig.md
@@ -52,7 +52,7 @@ threshold, they will immediately have access to these tokens.
 
 ### Multisig Transactions with Accounts Tab
 
-:::info Waltkthrough Video Tutorial
+:::info Walkthrough Video Tutorial
 
 See [this video tutorial](https://www.youtube.com/watch?v=-cPiKMslZqI) to learn how to transact with
 a multisig account using the Accounts Tab in the

diff --git a/docs/learn/learn-accounts.md b/docs/learn/learn-accounts.md
@@ -155,7 +155,7 @@ More in-depth information about the above data can be found in the
 The `AccountData` structure defines the balance types in Substrate. The three types of balances
 include `free`, `reserved`, and `frozen`. The **usable** balance of the account is the amount that
 is `free` minus any funds considered `frozen`, while the **total** balance of the account is the sum
-of `free` and`reserved` funds. The `flags` describe extra information about the account.
+of `free` and `reserved` funds. The `flags` describe extra information about the account.
 
 More in-depth information about the above data can be found in the
 [balances pallet in the Substrate code base](https://github.com/paritytech/substrate/blob/2e7fde832b77b242269b136f1c3b6fffef86f9b6/frame/balances/src/types.rs#LL95-L114).

diff --git a/docs/learn/learn-auction.md b/docs/learn/learn-auction.md
@@ -13,7 +13,7 @@ import AuctionSchedule from "./../../components/Auction-Schedule";
 
 For a [parachain](learn-parachains.md) to be added to
 {{ polkadot: Polkadot :polkadot }}{{ kusama: Kusama :kusama }} it must inhabit one of the available
-parachain slots. The number of parachain slots is are not unbounded on
+parachain slots. The number of parachain slots is not unbounded on
 {{ polkadot: Polkadot :polkadot }}{{ kusama: Kusama :kusama }}, as only a limited number are
 available. A limited number of slots are unlocked every few months through on-chain governance. If a
 parachain wants to have guaranteed block inclusion at every Relay Chain block, it must acquire a

diff --git a/docs/learn/learn-collator.md b/docs/learn/learn-collator.md
@@ -38,13 +38,13 @@ The validator must successfully verify the following conditions in the following
 3. Validate the candidate by executing the parachain Runtime.
 
 Once a candidate meets a specified criteria for inclusion, the selected relay chain block author
-then choses any of the backable candidates for each parachain and includes those into the relay
+then chooses any of the backable candidates for each parachain and includes those into the relay
 chain block. We say the candidate blocks are _backed_.
 
 The assumption that having more collators is better or more secure is not correct. On the contrary,
 too many collators may slow down the network. The only nefarious power collators have is transaction
 censorship. To prevent censorship, a parachain only needs to ensure that there are some neutral
-collators - but not necessarily a majority. Theoretically, the censorship problem is solved with
+collators - but not necessarily a majority. Theoretically, the censorship problem is solved by
 having just one honest collator.
 
 ## XCM

diff --git a/docs/learn/learn-comparison-ethereum-2.md b/docs/learn/learn-comparison-ethereum-2.md
@@ -51,7 +51,7 @@ architecture:
   relay chain.
 
 Polkadot can't and does not directly run something like a virtual machine for smart contracts.
-However, several of its parachains can (and does). Parachains on Polkadot can even run an EVM for
+However, several of its parachains can (and do). Parachains on Polkadot can even run an EVM for
 executing smart contracts written in Solidity, Ethereum's native smart contract language.
 
 In the context of blockchain, "sharding" refers to the parallelization of state transition
@@ -99,8 +99,8 @@ execute it within a Wasm environment.
 ## Architectural Differences: Polkadot and Ethereum
 
 As previously mentioned, Ethereum is a **general-purpose** virtual machine that can run sandboxed
-programs are written in Solidity, whereas Polkadot is a meta-protocol for other parachains to
-connect and interact with each other.
+programs written in Solidity, whereas Polkadot is a meta-protocol for other parachains to connect 
+and interact with each other.
 
 Ethereum operates as a single, homogeneous chain. Each Ethereum node is divided into two layers: the
 **consensus** and **execution** layers. Each layer handles the block validation information, peer
@@ -167,9 +167,12 @@ expected time to finality is 12-60 seconds.
     achieves this by making validators distribute an
     [erasure coding](./learn-parachains-protocol.md#erasure-codes) to all validators in the system,
     such that anyone - not only the shard's validators - can reconstruct a parachain's block and
-    test its validity. The random parachain-validator assignments and secondary checks were
-    performed randomly selected validators make it less likely for the small set of validators on
-    each parachain to collude.
+    test its validity. The random parachain-validator assignments and secondary checks are
+
+
+
+    performed by randomly selected validators making it less likely for the small set of validators 
+    on each parachain to collude.
 
 ### Staking Mechanics
 

diff --git a/docs/learn/learn-guides-polkadot-opengov.md b/docs/learn/learn-guides-polkadot-opengov.md
@@ -24,7 +24,7 @@ attain
 :::
 
 To cancel a referendum, you need first to submit a preimage. Go to the
-[Polkadot-JS UI > Governace > Referenda](https://polkadot.js.org/apps/#/referenda) and click on the
+[Polkadot-JS UI > Governance > Referenda](https://polkadot.js.org/apps/#/referenda) and click on the
 "Add Preimage" button. You must specify the specific call enacted if the proposal passes. To cancel
 a referendum, you must specify the `referenda.cancel` extrinsic of referendum `249`.