Fix spelling mistakes across the whole repository (#3808)

**Update:** Pushed additional changes based on the review comments.

**This pull request fixes various spelling mistakes in this
repository.**

Most of the changes are contained in the first **3** commits:

- `Fix spelling mistakes in comments and docs`

- `Fix spelling mistakes in test names`

- `Fix spelling mistakes in error messages, panic messages, logs and
tracing`

Other source code spelling mistakes are separated into individual
commits for easier reviewing:

- `Fix the spelling of 'authority'`

- `Fix the spelling of 'REASONABLE_HEADERS_IN_JUSTIFICATION_ANCESTRY'`

- `Fix the spelling of 'prev_enqueud_messages'`

- `Fix the spelling of 'endpoint'`

- `Fix the spelling of 'children'`

- `Fix the spelling of 'PenpalSiblingSovereignAccount'`

- `Fix the spelling of 'PenpalSudoAccount'`

- `Fix the spelling of 'insufficient'`

- `Fix the spelling of 'PalletXcmExtrinsicsBenchmark'`

- `Fix the spelling of 'subtracted'`

- `Fix the spelling of 'CandidatePendingAvailability'`

- `Fix the spelling of 'exclusive'`

- `Fix the spelling of 'until'`

- `Fix the spelling of 'discriminator'`

- `Fix the spelling of 'nonexistent'`

- `Fix the spelling of 'subsystem'`

- `Fix the spelling of 'indices'`

- `Fix the spelling of 'committed'`

- `Fix the spelling of 'topology'`

- `Fix the spelling of 'response'`

- `Fix the spelling of 'beneficiary'`

- `Fix the spelling of 'formatted'`

- `Fix the spelling of 'UNKNOWN_PROOF_REQUEST'`

- `Fix the spelling of 'succeeded'`

- `Fix the spelling of 'reopened'`

- `Fix the spelling of 'proposer'`

- `Fix the spelling of 'InstantiationNonce'`

- `Fix the spelling of 'depositor'`

- `Fix the spelling of 'expiration'`

- `Fix the spelling of 'phantom'`

- `Fix the spelling of 'AggregatedKeyValue'`

- `Fix the spelling of 'randomness'`

- `Fix the spelling of 'defendant'`

- `Fix the spelling of 'AquaticMammal'`

- `Fix the spelling of 'transactions'`

- `Fix the spelling of 'PassingTracingSubscriber'`

- `Fix the spelling of 'TxSignaturePayload'`

- `Fix the spelling of 'versioning'`

- `Fix the spelling of 'descendant'`

- `Fix the spelling of 'overridden'`

- `Fix the spelling of 'network'`

Let me know if this structure is adequate.

**Note:** The usage of the words `Merkle`, `Merkelize`, `Merklization`,
`Merkelization`, `Merkleization`, is somewhat inconsistent but I left it
as it is.

~~**Note:** In some places the term `Receival` is used to refer to
message reception, IMO `Reception` is the correct word here, but I left
it as it is.~~

~~**Note:** In some places the term `Overlayed` is used instead of the
more acceptable version `Overlaid` but I also left it as it is.~~

~~**Note:** In some places the term `Applyable` is used instead of the
correct version `Applicable` but I also left it as it is.~~

**Note:** Some usage of British vs American english e.g. `judgement` vs
`judgment`, `initialise` vs `initialize`, `optimise` vs `optimize` etc.
are both present in different places, but I suppose that's
understandable given the number of contributors.

~~**Note:** There is a spelling mistake in `.github/CODEOWNERS` but it
triggers errors in CI when I make changes to it, so I left it as it
is.~~

substrate/bin/node/cli/benches/block_production.rs

@@ -145,7 +145,7 @@ fn prepare_benchmark(client: &FullClient) -> (usize, Vec<OpaqueExtrinsic>) {
 	let src = Sr25519Keyring::Alice.pair();
 	let dst: MultiAddress<AccountId32, u32> = Sr25519Keyring::Bob.to_account_id().into();
 
-	// Add as many tranfer extrinsics as possible into a single block.
+	// Add as many transfer extrinsics as possible into a single block.
 	for nonce in 0.. {
 		let extrinsic: OpaqueExtrinsic = create_extrinsic(
 			client,
@@ -179,7 +179,7 @@ fn block_production(c: &mut Criterion) {
 	let node = new_node(tokio_handle.clone());
 	let client = &*node.client;
 
-	// Buliding the very first block is around ~30x slower than any subsequent one,
+	// Building the very first block is around ~30x slower than any subsequent one,
 	// so let's make sure it's built and imported before we benchmark anything.
 	let mut block_builder = BlockBuilderBuilder::new(client)
 		.on_parent_block(client.chain_info().best_hash)

substrate/bin/node/cli/src/cli.rs

@@ -49,7 +49,7 @@ pub struct Cli {
 /// Possible subcommands of the main binary.
 #[derive(Debug, clap::Subcommand)]
 pub enum Subcommand {
-	/// The custom inspect subcommmand for decoding blocks and extrinsics.
+	/// The custom inspect subcommand for decoding blocks and extrinsics.
 	#[command(
 		name = "inspect",
 		about = "Decode given block or extrinsic using current native runtime."

substrate/bin/node/cli/src/service.rs

@@ -53,7 +53,7 @@ pub type HostFunctions = (
 	frame_benchmarking::benchmarking::HostFunctions,
 );
 
-/// A specialized `WasmExecutor` intended to use accross substrate node. It provides all required
+/// A specialized `WasmExecutor` intended to use across substrate node. It provides all required
 /// HostFunctions.
 pub type RuntimeExecutor = sc_executor::WasmExecutor<HostFunctions>;
 

substrate/bin/node/cli/tests/fees.rs

@@ -135,7 +135,7 @@ fn transaction_fee_is_correct() {
 	// if weight of the cheapest weight would be 10^7, this would be 10^9, which is:
 	//   - 1 MILLICENTS in substrate node.
 	//   - 1 milli-dot based on current polkadot runtime.
-	// (this baed on assigning 0.1 CENT to the cheapest tx with `weight = 100`)
+	// (this based on assigning 0.1 CENT to the cheapest tx with `weight = 100`)
 	let mut t = new_test_ext(compact_code_unwrap());
 	t.insert(<frame_system::Account<Runtime>>::hashed_key_for(alice()), new_account_info(100));
 	t.insert(<frame_system::Account<Runtime>>::hashed_key_for(bob()), new_account_info(10));

substrate/bin/node/testing/src/bench.rs

@@ -84,7 +84,7 @@ impl BenchPair {
 
 /// Drop system cache.
 ///
-/// Will panic if cache drop is impossbile.
+/// Will panic if cache drop is impossible.
 pub fn drop_system_cache() {
 	#[cfg(target_os = "windows")]
 	{
@@ -173,7 +173,7 @@ impl Clone for BenchDb {
 
 		// We clear system cache after db clone but before any warmups.
 		// This populates system cache with some data unrelated to actual
-		// data we will be quering further under benchmark (like what
+		// data we will be querying further under benchmark (like what
 		// would have happened in real system that queries random entries
 		// from database).
 		drop_system_cache();
@@ -443,7 +443,7 @@ impl BenchDb {
 		BlockContentIterator::new(content, &self.keyring, client)
 	}
 
-	/// Get cliet for this database operations.
+	/// Get client for this database operations.
 	pub fn client(&mut self) -> Client {
 		let (client, _backend, _task_executor) =
 			Self::bench_client(self.database_type, self.directory_guard.path(), &self.keyring);

substrate/bin/utils/chain-spec-builder/src/lib.rs

@@ -185,7 +185,7 @@ pub struct ConvertToRawCmd {
 /// Verifies the provided input chain spec.
 ///
 /// Silently checks if given input chain spec can be converted to raw. It allows to check if all
-/// RuntimeGenesisConfig fiels are properly initialized and if the json does not contain invalid
+/// RuntimeGenesisConfig fields are properly initialized and if the json does not contain invalid
 /// fields.
 #[derive(Parser, Debug, Clone)]
 pub struct VerifyCmd {

substrate/bin/utils/subkey/README.md

@@ -77,7 +77,7 @@ below can be derived from those secrets.
 The output above also show the **public key** and the **Account ID**. Those are the independent from the network where
 you will use the key.
 
-The **SS58 address** (or **Public Address**) of a new account is a reprensentation of the public keys of an account for
+The **SS58 address** (or **Public Address**) of a new account is a representation of the public keys of an account for
 a given network (for instance Kusama or Polkadot).
 
 You can read more about the [SS58 format in the Substrate Docs](https://docs.substrate.io/reference/address-formats/)
@@ -143,7 +143,7 @@ Secret phrase `soup lyrics media market way crouch elevator put moon useful ques
   SS58 Address:     5He5pZpc7AJ8evPuab37vJF6KkFDqq9uDq2WXh877Qw6iaVC
 ```
 
-Using the `inspect` command (see more details below), we see that knowning only the **secret seed** is no longer
+Using the `inspect` command (see more details below), we see that knowing only the **secret seed** is no longer
 sufficient to recover the account:
 
 ```bash

substrate/bin/utils/subkey/src/lib.rs

@@ -94,10 +94,10 @@
 //! seed** (also called **Private Key**). Those 2 secrets are the pieces of information you MUST
 //! keep safe and secret. All the other information below can be derived from those secrets.
 //!
-//! The output above also show the **public key** and the **Account ID**. Those are the independant
+//! The output above also show the **public key** and the **Account ID**. Those are the independent
 //! from the network where you will use the key.
 //!
-//! The **SS58 address** (or **Public Address**) of a new account is a reprensentation of the public
+//! The **SS58 address** (or **Public Address**) of a new account is a representation of the public
 //! keys of an account for a given network (for instance Kusama or Polkadot).
 //!
 //! You can read more about the [SS58 format in the Substrate Docs](https://docs.substrate.io/reference/address-formats/) and see the list of reserved prefixes in the [SS58 Registry](https://github.com/paritytech/ss58-registry).
@@ -110,7 +110,7 @@
 //!
 //! ### Json output
 //!
-//! `subkey` can calso generate the output as *json*. This is useful for automation.
+//! `subkey` can also generate the output as *json*. This is useful for automation.
 //!
 //! command:
 //!
@@ -163,7 +163,7 @@
 //!   SS58 Address:     5He5pZpc7AJ8evPuab37vJF6KkFDqq9uDq2WXh877Qw6iaVC
 //! ```
 //!
-//! Using the `inspect` command (see more details below), we see that knowning only the **secret
+//! Using the `inspect` command (see more details below), we see that knowing only the **secret
 //! seed** is no longer sufficient to recover the account:
 //!
 //! ```bash
@@ -184,7 +184,7 @@
 //!
 //! ### Inspecting a key
 //!
-//! If you have *some data* about a key, `subkey inpsect` will help you discover more information
+//! If you have *some data* about a key, `subkey inspect` will help you discover more information
 //! about it.
 //!
 //! If you have **secrets** that you would like to verify for instance, you can use: