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/primitives/tracing/src/lib.rs

@@ -17,7 +17,7 @@
 
 //! Substrate tracing primitives and macros.
 //!
-//! To trace functions or invidual code in Substrate, this crate provides [`within_span`]
+//! To trace functions or individual code in Substrate, this crate provides [`within_span`]
 //! and [`enter_span`]. See the individual docs for how to use these macros.
 //!
 //! Note that to allow traces from wasm execution environment there are
@@ -70,7 +70,7 @@ pub use crate::types::{WASM_NAME_KEY, WASM_TARGET_KEY, WASM_TRACE_IDENTIFIER};
 /// directly as they yield nothing without the feature present. Instead you should use
 /// `enter_span!` and `within_span!` – which would strip away even any parameter conversion
 /// you do within the span-definition (and thus optimise your performance). For your
-/// convineience you directly specify the `Level` and name of the span or use the full
+/// convenience you directly specify the `Level` and name of the span or use the full
 /// feature set of `span!`/`span_*!` on it:
 ///
 /// # Example
@@ -98,7 +98,7 @@ pub use crate::types::{WASM_NAME_KEY, WASM_TARGET_KEY, WASM_TRACE_IDENTIFIER};
 /// This project only provides the macros and facilities to manage tracing
 /// it doesn't implement the tracing subscriber or backend directly – that is
 /// up to the developer integrating it into a specific environment. In native
-/// this can and must be done through the regular `tracing`-facitilies, please
+/// this can and must be done through the regular `tracing`-facilities, please
 /// see their documentation for details.
 ///
 /// On the wasm-side we've adopted a similar approach of having a global
@@ -139,7 +139,7 @@ pub fn init_for_tests() {
 /// Runs given code within a tracing span, measuring it's execution time.
 ///
 /// If tracing is not enabled, the code is still executed. Pass in level and name or
-/// use any valid `sp_tracing::Span`followe by `;` and the code to execute,
+/// use any valid `sp_tracing::Span`followed by `;` and the code to execute,
 ///
 /// # Example
 ///

substrate/primitives/tracing/src/types.rs

@@ -17,7 +17,7 @@
 
 use alloc::{vec, vec::Vec};
 use codec::{Decode, Encode};
-/// Types for wasm based tracing. Loosly inspired by `tracing-core` but
+/// Types for wasm based tracing. Loosely inspired by `tracing-core` but
 /// optimised for the specific use case.
 use core::{fmt::Debug, format_args};
 
@@ -54,7 +54,7 @@ impl core::default::Default for WasmLevel {
 	}
 }
 
-/// A paramter value provided to the span/event
+/// A parameter value provided to the span/event
 #[derive(Encode, Decode, Clone)]
 pub enum WasmValue {
 	U8(u8),
@@ -180,9 +180,9 @@ impl From<i64> for WasmValue {
 	}
 }
 
-/// The name of a field provided as the argument name when contstructing an
+/// The name of a field provided as the argument name when constructing an
 /// `event!` or `span!`.
-/// Generally generated automaticaly via `stringify` from an `'static &str`.
+/// Generally generated automatically via `stringify` from an `'static &str`.
 /// Likely print-able.
 #[derive(Encode, Decode, Clone)]
 pub struct WasmFieldName(Vec<u8>);
@@ -320,7 +320,7 @@ impl tracing_core::field::Visit for WasmValuesSet {
 		self.0.push((field.name().into(), Some(WasmValue::from(value))))
 	}
 }
-/// Metadata provides generic information about the specifc location of the
+/// Metadata provides generic information about the specific location of the
 /// `span!` or `event!` call on the wasm-side.
 #[derive(Encode, Decode, Clone)]
 pub struct WasmMetadata {