Fix typos (#327)

README.md

@@ -104,7 +104,7 @@ git checkout ${LATEST_TAG}
 
 ### Install WebAssembly target
 
-Hyperbridge's blockchain runtime compiles to wasm which allows it's code to be forklessly upgraded. In order to build hyperbridge we need the wasm toolchain installed.
+Hyperbridge's blockchain runtime compiles to wasm which allows its code to be forklessly upgraded. In order to build hyperbridge we need the wasm toolchain installed.
 
 ```bash
 rustup update nightly

docs/pages/developers/evm/getting-started.mdx

@@ -1,12 +1,12 @@
 ---
 title: Getting Started
-description: ISMP Solidity is the implementation of the Interoperable State Machine Protocol for EVM execution environments. It provides EVM smart contracts with the neccessary interfaces to send and receive messages securely through the Hyperbridge Nexus.
+description: ISMP Solidity is the implementation of the Interoperable State Machine Protocol for EVM execution environments. It provides EVM smart contracts with the necessary interfaces to send and receive messages securely through the Hyperbridge Nexus.
 ---
 
 
 # ISMP Solidity
 
-ISMP Solidity is the implementation of the [Interoperable State Machine Protocol](/protocol/ismp) for EVM execution environments. It provides EVM smart contracts with the neccessary interfaces to send and receive messages securely through the Hyperbridge Nexus. Let's dive into it's different components:
+ISMP Solidity is the implementation of the [Interoperable State Machine Protocol](/protocol/ismp) for EVM execution environments. It provides EVM smart contracts with the necessary interfaces to send and receive messages securely through the Hyperbridge Nexus. Let's dive into it's different components:
 
 ## `EvmHost`
 

docs/pages/developers/explore/modules/fishermen.mdx

@@ -1,11 +1,11 @@
 ---
 title: Pallet Fishermen
-description: The Fishermen module is responsible for tracking a permissioned set of accounts who are given the priviledge to veto any misrepresentative state commitments which are submitted to the Hyperbridge blockchain.
+description: The Fishermen module is responsible for tracking a permissioned set of accounts who are given the privilege to veto any misrepresentative state commitments which are submitted to the Hyperbridge blockchain.
 ---
 
 # Pallet Fishermen
 
-The Fishermen module is responsible for tracking a permissioned set of accounts who are given the priviledge to veto any misrepresentative state commitments which are submitted to the Hyperbridge blockchain. They are able to do this without providing any cryptographic proofs. Recall that state commitments are the outputs of consensus proof verification by the relevant consensus client on the Hyperbridge blockchain. In a scenario where the source chain's validators become byzantine, the fishermen keep the applications that rely on the Hyperbridge blockchain safe from any byzantine attacks.
+The Fishermen module is responsible for tracking a permissioned set of accounts who are given the privilege to veto any misrepresentative state commitments which are submitted to the Hyperbridge blockchain. They are able to do this without providing any cryptographic proofs. Recall that state commitments are the outputs of consensus proof verification by the relevant consensus client on the Hyperbridge blockchain. In a scenario where the source chain's validators become byzantine, the fishermen keep the applications that rely on the Hyperbridge blockchain safe from any byzantine attacks.
 
 This of course has some drawbacks, as the fishermen themselves could become malicious and begin to veto **valid state commitments**. However this can only constitute a griefing attack that temporarily prevents Hyperbridge from processing new cross-chain messages. Fishermen **cannot censor specific cross-chain messages**, this is because the state commitment of a blockchain is an **accumulator**. Even if they veto the state commitment for a specific height, later state commitments will still include the messages from the censored height. If any fishermen are found to be malicious, they can be removed from the fishermen set by the Hyperbridge governance.
 

docs/pages/developers/explore/modules/host-executive.mdx

@@ -7,7 +7,7 @@ description: The Hyperbridge protocol encompasses more than just the Hyperbridge
 
 The Hyperbridge protocol encompasses more than just the Hyperbridge nexus blockchain, it also includes contracts or modules on its connected chains. These modules, which are governed by the Hyperbridge protocol, are responsible for collecting relayer and protocol revenue for cross-chain operations. They are managed from Hyperbridge through the `HostManager` interface. This interface allows the Hyperbridge protocol to dispatch cross-chain governance actions which may either withdraw any accrued protocol or relayer revenue or modify its fee structure or other protocol parameters.
 
-The `HostExecutive` module on Hyperbridge is the module responsible for managing the `HostManager` across all connected chains. It tracks any relevant protocol parameters for each chain and allows the Hyperbridge governance dispatch any protocol paramater changes to the connected chains. It is named after the corporate structure of a multi-~chain~national company, where the "Executive" is responsible for managing the "Regional Manager".
+The `HostExecutive` module on Hyperbridge is the module responsible for managing the `HostManager` across all connected chains. It tracks any relevant protocol parameters for each chain and allows the Hyperbridge governance to dispatch any protocol parameter changes to the connected chains. It is named after the corporate structure of a multi-~chain~national company, where the "Executive" is responsible for managing the "Regional Manager".
 
 
 ## Implementation

docs/pages/developers/explore/modules/ismp.mdx

@@ -7,13 +7,13 @@ description: The ISMP module is the central module of the Hyperbridge blockchain
 
 The `pallet-ismp` is the central module of the Hyperbridge blockchain. It is the core innovation that makes the Hyperbridge protocol possible. It is responsible for:
 
- - Verifying the consensus proofs and managing the state commitments of it's connected chains through the use of "consensus clients".
+ - Verifying the consensus proofs and managing the state commitments of its connected chains through the use of "consensus clients".
  - Verifying and aggregating the cross-chain messages that are relayed from its connected chains.
- - Managing various consensus clients on behalf of it's connected chains.
+ - Managing various consensus clients on behalf of its connected chains.
 
  ## Consensus Clients
 
- The Hyperbridge blockchain uses "consensus clients" to verify the consensus proofs of it's connected chains. A consensus client is a module that is responsible for verifying the consensus proofs which attest to the finality of some state commitment of a specific blockchain. Any blockchain that produces consensus proofs can be connected to the Hyperbridge blockchain through a consensus client. The `pallet-ismp` module manages the consensus clients on behalf of the connected chains. The consensus clients currently supported by the Hyperbridge protocol are:
+ The Hyperbridge blockchain uses "consensus clients" to verify the consensus proofs of its connected chains. A consensus client is a module that is responsible for verifying the consensus proofs which attest to the finality of some state commitment of a specific blockchain. Any blockchain that produces consensus proofs can be connected to the Hyperbridge blockchain through a consensus client. The `pallet-ismp` module manages the consensus clients on behalf of the connected chains. The consensus clients currently supported by the Hyperbridge protocol are:
 
   - [Parachain Consensus Client](https://github.com/polytope-labs/hyperbridge/tree/main/modules/ismp/clients/parachain/client)
   - [Sync Committee Consensus Client](https://github.com/polytope-labs/hyperbridge/tree/main/modules/ismp/clients/sync-committee)

docs/pages/developers/explore/modules/relayer.mdx

@@ -18,7 +18,7 @@ Once a relayer successfully completes a delivery, after winning the "relay race"
   - **State proofs of initial request/response**:
     Recall that users or applications can opt to provide a fee to incentivize the delivery of their cross-chain message. The relayer must provide state proofs of the initial request/response that was dispatched on the source chain. The state proof must reveal the associated fees that was provided by the user or application.
   - **State proofs of the request/response delivery**:
-     Successful deliveries are stored in the [`IsmpHost`](/protocol/ismp/host) alongside the account of the responsible relayer. This allows the `pallet-ismp-relayer` module to verify the delivery of the message and it's associated relayer.
+     Successful deliveries are stored in the [`IsmpHost`](/protocol/ismp/host) alongside the account of the responsible relayer. This allows the `pallet-ismp-relayer` module to verify the delivery of the message and its associated relayer.
 
      Once the `pallet-ismp-relayer` module verifies these proofs and confirms them to be valid, the module will "accumulate" the fees associated with the delivery. Storing the fees in the relayer's account. The relayer can then withdraw these fees at any time.
 

docs/pages/developers/explore/nexus.mdx

@@ -1,15 +1,15 @@
 ---
 title: Hyperbridge Nexus
-description: Hyperbridge is at it's fundamental level, a coprocessor for expensive cryptographic operations needed to confirm the validity of cross-chain messages.
+description: Hyperbridge is at its fundamental level, a coprocessor for expensive cryptographic operations needed to confirm the validity of cross-chain messages.
 ---
 
 # Hyperbridge Nexus
 
-The Hyperbridge blockchain is designed to be the Nexus of secure cross-chain interoperability. Hence the name. Hyperbridge is at it's fundamental level, a coprocessor for expensive cryptographic operations needed to confirm the validity of cross-chain messages.
+The Hyperbridge blockchain is designed to be the Nexus of secure cross-chain interoperability. Hence the name. Hyperbridge is at its fundamental level, a coprocessor for expensive cryptographic operations needed to confirm the validity of cross-chain messages.
 
 ## Crypto-Economic Coprocessor
 
-The Hyperbridge blockchain performs all the neccessary computation needed to certify the validity of cross-chain messages and presents a single proof to any chain to prove the finality of the aggregated messages. This architecture pioneered by Hyperbridge, introduces a new class of coprocessors called **crypto-economic coprocessors** that leverage their consensus proofs to attest to the correctness of the computations performed onchain (ie within it's state transition function).
+The Hyperbridge blockchain performs all the necessary computation needed to certify the validity of cross-chain messages and presents a single proof to any chain to prove the finality of the aggregated messages. This architecture pioneered by Hyperbridge, introduces a new class of coprocessors called **crypto-economic coprocessors** that leverage their consensus proofs to attest to the correctness of the computations performed onchain (ie within its state transition function).
 
 This crypto-economic coprocessor model is what enables Hyperbridge to scale trust-free interoperability to all blockchains. But it also places some requirements that must be met by the Hyperbridge blockchain to be scalable, fast and fully-secure. We've chosen the Polkadot relay chain as the base layer because it fully meets these requirements in a way that no other blockchain can.
 
@@ -20,7 +20,7 @@ The Nexus blockchain inherits the fast finality of the Polkadot relay chain. Thi
 
 ### Economic Security
 
-The Nexus blockchain is secured by the Polkadot relay chain. This economic security is **fully attributable**. Unlike restaked security models where economic security and validators are rehypothecated across multiple chains, the Polkadot relay chain provides a direct and fully attributable security model. In this model, it's validators are not overloaded across parachains for (obvious) security reasons. It means faults are isolated, attributable and therefore accountable. The offending validators can be slashed, permissionlessly (no committee approvals needed), without issue.
+The Nexus blockchain is secured by the Polkadot relay chain. This economic security is **fully attributable**. Unlike restaked security models where economic security and validators are rehypothecated across multiple chains, the Polkadot relay chain provides a direct and fully attributable security model. In this model, its validators are not overloaded across parachains for (obvious) security reasons. It means faults are isolated, attributable and therefore accountable. The offending validators can be slashed, permissionlessly (no committee approvals needed), without issue.
 
 
 ### Execution Sharding
@@ -34,7 +34,7 @@ Polkadot provides a sharded design that allows for the execution of multiple par
 
 ### Cheap Consensus Proofs
 
-Polkadot introduces [BEEFY](/protocol/consensus/beefy), a secondary consensus protocol that produces the cheapest consensus proofs of any blockchain. Since Hyperbridge uses Polkadot as it's consensus layer, this means that Polkadot's consensus proofs are what attest to the finality of Hyperbridge blocks. This consensus proof must be sent to the destination chain to prove the finality of the cross-chain messages that have been aggregated on the Hyperbridge blockchain. This is critical to it's crypto-economic coprocessor architecture, as it leverages the cheap consensus proofs of the Polkadot relay chain to attest to the correctness of the work done by the Hyperbridge blockchain.
+Polkadot introduces [BEEFY](/protocol/consensus/beefy), a secondary consensus protocol that produces the cheapest consensus proofs of any blockchain. Since Hyperbridge uses Polkadot as its consensus layer, this means that Polkadot's consensus proofs are what attest to the finality of Hyperbridge blocks. This consensus proof must be sent to the destination chain to prove the finality of the cross-chain messages that have been aggregated on the Hyperbridge blockchain. This is critical to its crypto-economic coprocessor architecture, as it leverages the cheap consensus proofs of the Polkadot relay chain to attest to the correctness of the work done by the Hyperbridge blockchain.
 
 
  ## Runtime Modules