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.~~

polkadot/node/network/statement-distribution/src/legacy_v1/responder.rs

@@ -64,7 +64,7 @@ pub async fn respond(
 		//    late, as each requester having the data will help distributing it.
 		// 2. If we take too long, the requests timing out will not yet have had any data sent, thus
 		//    we wasted no bandwidth.
-		// 3. If the queue is full, requestes will get an immediate error instead of running in a
+		// 3. If the queue is full, requests will get an immediate error instead of running in a
 		//    timeout, thus requesters can immediately try another peer and be faster.
 		//
 		// From this perspective we would not want parallel response sending at all, but we don't

polkadot/node/network/statement-distribution/src/legacy_v1/tests.rs

@@ -1494,7 +1494,7 @@ fn receiving_large_statement_from_one_sends_to_another_and_to_candidate_backing(
 			Err(()) => {}
 		);
 
-		// And now the succeding request from peer_b:
+		// And now the succeeding request from peer_b:
 		let (pending_response, response_rx) = oneshot::channel();
 		let inner_req = StatementFetchingRequest {
 			relay_parent: metadata.relay_parent,

polkadot/node/network/statement-distribution/src/v2/cluster.rs

@@ -430,8 +430,8 @@ impl ClusterTracker {
 	///
 	/// Normally we should not have pending statements to validators in our cluster,
 	/// but if we do for all validators in our cluster, then we don't participate
-	/// in backing. Ocasional pending statements are expected if two authorities
-	/// can't detect each otehr or after restart, where it takes a while to discover
+	/// in backing. Occasional pending statements are expected if two authorities
+	/// can't detect each other or after restart, where it takes a while to discover
 	/// the whole network.
 
 	pub fn warn_if_too_many_pending_statements(&self, parent_hash: Hash) {

polkadot/node/network/statement-distribution/src/v2/mod.rs

@@ -112,7 +112,7 @@ const COST_EXCESSIVE_SECONDED: Rep = Rep::CostMinor("Sent Excessive `Seconded` S
 const COST_DISABLED_VALIDATOR: Rep = Rep::CostMinor("Sent a statement from a disabled validator");
 
 const COST_UNEXPECTED_MANIFEST_MISSING_KNOWLEDGE: Rep =
-	Rep::CostMinor("Unexpected Manifest, missing knowlege for relay parent");
+	Rep::CostMinor("Unexpected Manifest, missing knowledge for relay parent");
 const COST_UNEXPECTED_MANIFEST_DISALLOWED: Rep =
 	Rep::CostMinor("Unexpected Manifest, Peer Disallowed");
 const COST_UNEXPECTED_MANIFEST_PEER_UNKNOWN: Rep =
@@ -628,8 +628,8 @@ pub(crate) async fn handle_active_leaves_update<Context>(
 				request_min_backing_votes(new_relay_parent, session_index, ctx.sender()).await?;
 			let mut per_session_state =
 				PerSessionState::new(session_info, &state.keystore, minimum_backing_votes);
-			if let Some(toplogy) = state.unused_topologies.remove(&session_index) {
-				per_session_state.supply_topology(&toplogy.topology, toplogy.local_index);
+			if let Some(topology) = state.unused_topologies.remove(&session_index) {
+				per_session_state.supply_topology(&topology.topology, topology.local_index);
 			}
 			state.per_session.insert(session_index, per_session_state);
 		}

polkadot/node/network/statement-distribution/src/v2/requests.rs

@@ -320,7 +320,7 @@ impl RequestManager {
 		// need for the current node to limit itself to the same amount the
 		// requests, because the requests are going to different nodes anyways.
 		// While looking at https://github.com/paritytech/polkadot-sdk/issues/3314,
-		// found out that this requests take around 100ms to fullfill, so it
+		// found out that this requests take around 100ms to fulfill, so it
 		// would make sense to try to request things as early as we can, given
 		// we would need to request it for each candidate, around 25 right now
 		// on kusama.