chore: fix typos (paritytech#4590)

chore: fix typos

Author: omahs

bridges/docs/running-relayer.md

@@ -139,7 +139,7 @@ your transactions that are **validated** on top of block, where it is active get
 becomes expired when the block with the number you have specified during registration is "mined". It is the
 `validTill` parameter of the `register` call (see below). After that `validTill` block, you may unregister and get
 your reserved funds back. There's also an intermediate point between those blocks - it is the `validTill - LEASE`,
-where `LEASE` is the the chain constant, controlled by the governance. Initially it is set to `300` blocks.
+where `LEASE` is the chain constant, controlled by the governance. Initially it is set to `300` blocks.
 All your transactions, **validated** between the `validTill - LEASE` and `validTill` blocks do not get the
 priority boost. Also, it is forbidden to specify `validTill` such that the `validTill - currentBlock` is less
 than the `LEASE`.
@@ -156,7 +156,7 @@ than the `LEASE`.
 | 700               | Inactive           | Your message delivery transactions are not boosted     |
 | 701               | Inactive           | Your message delivery transactions are not boosted     |
 | ...               | Inactive           | Your message delivery transactions are not boosted     |
-| 1000              | Expired            | Your may submit a tx with the `deregister` call        |
+| 1000              | Expired            | You may submit a tx with the `deregister` call         |
 
 </details>
 
@@ -230,7 +230,7 @@ your relayer account. Then:
 
 - set the `bridgedChainId` to `bhpd`;
 
-- check the both variants of the `owner` field: `ThisChain` is used to pay for message delivery transactions
+- check both variants of the `owner` field: `ThisChain` is used to pay for message delivery transactions
   and `BridgedChain` is used to pay for message confirmation transactions.
 
 If check shows that you have some rewards, you can craft the claim transaction, with similar parameters.

docs/RELEASE.md

@@ -45,7 +45,7 @@ variable.
 
 ## Westend & Rococo
 
-For the these networks, in addition to incrementing the `Cargo.toml` version we also increment the `spec_version` and
+For these networks, in addition to incrementing the `Cargo.toml` version we also increment the `spec_version` and
 sometimes the `transaction_version`. The spec version is also following the node version. Its schema is: `M_mmm_ppp` and
 for example `1_002_000` is the node release `1.2.0`. This versioning has no further meaning, and is only done to map
 from an on chain `spec_version` easily to the release in this repository.  

polkadot/roadmap/implementers-guide/src/runtime/scheduler.md

@@ -1,7 +1,7 @@
 # Scheduler Pallet
 
 > TODO: this section is still heavily under construction. key questions about availability cores and validator
-> assignment are still open and the flow of the the section may be contradictory or inconsistent
+> assignment are still open and the flow of the section may be contradictory or inconsistent
 
 The Scheduler module is responsible for two main tasks:
 

prdoc/schema_user.json

@@ -218,7 +218,7 @@
       },
       "doc": {
         "type": "object",
-        "description": "You have the the option to provide different description of your PR for different audiences.",
+        "description": "You have the option to provide different description of your PR for different audiences.",
         "additionalProperties": false,
         "properties": {
           "audience": {

substrate/bin/utils/subkey/README.md

@@ -74,7 +74,7 @@ The output above shows a **secret phrase** (also called **mnemonic phrase**) and
 **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 independent from the network where
+The output above also shows 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 representation of the public keys of an account for
@@ -152,7 +152,7 @@ subkey inspect "soup lyrics media market way crouch elevator put moon useful que
 
 which recovers the account `5Fe4sqj2K4fRuzEGvToi4KATqZfiDU7TqynjXG6PZE2dxwyh` and not
 `5He5pZpc7AJ8evPuab37vJF6KkFDqq9uDq2WXh877Qw6iaVC` as we expected. The additional user-defined **password**
-(`extra_secret` in our example) is now required to fully recover the account. Let's inspect the the previous mnemonic,
+(`extra_secret` in our example) is now required to fully recover the account. Let's inspect the previous mnemonic,
 this time passing also the required `password` as shown below:
 
 ```bash

substrate/client/transaction-pool/README.md

@@ -49,7 +49,7 @@ pool, it's broadcasting status, block inclusion, finality, etc.
 
 ## Transaction Validity details
 
-Information retrieved from the the runtime are encapsulated in the `TransactionValidity`
+Information retrieved from the runtime are encapsulated in the `TransactionValidity`
 type.
 
 ```rust

substrate/frame/contracts/README.md

@@ -112,7 +112,7 @@ Contracts can emit messages to the client when called as RPC through the
 API. This is exposed in [ink!](https://use.ink) via
 [`ink_env::debug_message()`](https://paritytech.github.io/ink/ink_env/fn.debug_message.html).
 
-Those messages are gathered into an internal buffer and sent to the RPC client. It is up the the individual client if
+Those messages are gathered into an internal buffer and sent to the RPC client. It is up to the individual client if
 and how those messages are presented to the user.
 
 This buffer is also printed as a debug message. In order to see these messages on the node console the log level for the

substrate/utils/frame/benchmarking-cli/src/overhead/README.md

@@ -108,7 +108,7 @@ The complete command for Polkadot looks like this:
 cargo run --profile=production -- benchmark overhead --chain=polkadot-dev --wasm-execution=compiled --weight-path=runtime/polkadot/constants/src/weights/
 ```
 
-This will overwrite the the
+This will overwrite the
 [block_weights.rs](https://github.com/paritytech/polkadot/blob/c254e5975711a6497af256f6831e9a6c752d28f5/runtime/polkadot/constants/src/weights/block_weights.rs)
 and
 [extrinsic_weights.rs](https://github.com/paritytech/polkadot/blob/c254e5975711a6497af256f6831e9a6c752d28f5/runtime/polkadot/constants/src/weights/extrinsic_weights.rs)