Fix typo (#36)

docs/build/networks.md

@@ -2,13 +2,13 @@
 
 The [Msgport Protocol](./../index.md) is a robust and reliable cross-chain messaging protocol that has been deployed on many mainstream Ethereum blockchains, This protocol has undergone careful revisions to enhance its developer and user-friendliness.
 
-## Canonical Cross-Chain Contract
+## Canonical Cross-chain Contract
 
 The Msgport protocol is a set of contracts that defines the [core interfaces](./interfaces.md) for sending and receiving cross-chain messages. You can think of it as an abstract class in programming, with `Msgport` as its name.
 This abstract class can have multiple subclasses, known as messaging protocols, which extend its functionality. Each of these subclasses must adhere to the interfaces defined in the Msgport protocol. To be user-friendly, each messaging protocol has 
 its unique contract address across all the networks it supports. The table below shows the canonical cross-chain contract address for each supported network.
 
-|   Name     |  Canonical Cross-Chain Contract Address  |
+|   Name     |  Canonical Cross-chain Contract Address  |
 |------------|--------------------------------------------|
 |   [ORMP](../learn/messaging-protocols/ormp.md)     | 0x0000000005d961F950adA391C1511c92bbc64D9F |
 

docs/community/ringdao.md

@@ -2,7 +2,7 @@
 
 RingDAO is a upcoming DAO based using [Tally](https://www.tally.xyz/) on Darwinia Chain, intended for governing the Darwinia Chain in its next version. It is currently under development and implementation. [**RING**](https://coinmarketcap.com/currencies/darwinia-network/) will be the govenance token of RingDAO. 
 
-## Cross-Chain Governance
+## Cross-chain Governance
 
 [XAcount](https://xaccount.box/) will be adopted by RingDAO for cross-chain govenance, it is also seamlessly integrated with the Safe Modules, with which we can customized a recovery address to challenge and gain the XAccount permission if it lost connection from original chain.
 

docs/learn/architecture.md

@@ -11,7 +11,7 @@ At the heart of this system is the core interface, [IMessagePort](../build/inter
 Highlighting the three messaging protocols:
 
   - [ORMP](./messaging-protocols/ormp.md): Oracle Relayer Messaging Protocol leverages chain-independent components, such as oracles and DApp-preferred relayers, to verify cross-chain messages. This approach integrates diverse verification mechanisms, ensuring robust and flexible cross-chain communication.
-  - [LCMP](./messaging-protocols/lcmp.md): Light Client Cross-Chain Messaging Protocol employs blockchain consensus mechanisms and light clients as decentralized verifiers. This ensures the integrity and accuracy of message verification across different blockchains, fostering a secure and trustless environment for message passing.
+  - [LCMP](./messaging-protocols/lcmp.md): Light Client Cross-chain Messaging Protocol employs blockchain consensus mechanisms and light clients as decentralized verifiers. This ensures the integrity and accuracy of message verification across different blockchains, fostering a secure and trustless environment for message passing.
   - [XCMP](./messaging-protocols/xcmp.md): Developed by Polkadot, Cross-Consensus Message Passing facilitates seamless messaging between various parachains within the Polkadot network. Messages are exchanged directly by parachains, relayed and verified by the relay chain, exemplifying efficient inter-parachain communication and interoperability.
 
 These implementations underscore Msgport's commitment to fostering interoperability, ensuring that assets and information can navigate the complex landscape of blockchain technology smoothly.

docs/learn/messaging-protocols/lcmp.md

@@ -3,7 +3,7 @@
 !!! Warning
     LCMP protocol served as a foundational prototype and remains in a testing stage, not yet deployed in a live production environment.
 
-LCMP, short for Light Client Cross-Chain Messaging Protocol, is a protocol meticulously designed and developed by the Darwinia core team. It is currently being actively utilized within Darwinia's chains. This protocol enables seamless communication between different blockchains by establishing messaging channels between them.
+LCMP, short for Light Client Cross-chain Messaging Protocol, is a protocol meticulously designed and developed by the Darwinia core team. It is currently being actively utilized within Darwinia's chains. This protocol enables seamless communication between different blockchains by establishing messaging channels between them.
 
 ![msgport-lcmp-1](../../images/msgport-lcmp-1.png)
 

docs/learn/messaging-protocols/ormp.md

@@ -74,7 +74,7 @@ When the `relay` method of the target chain contract is invoked, it performs the
 
 If the validation is successful, the message is then sent to the corresponding user application. Unless an exception occurs, the user contract's method is invoked to complete the cross-chain task associated with the message. At this point, we can consider the cross-chain message to have reached its destination.
 
-##  Cross-Chain Fee Calculation
+##  Cross-chain Fee Calculation
 
 The fee for cross-chain messaging is paid in the native token of the source chain. The application can retrieve the cross-chain fee by calling the **`fee`** function in the **[IMessagePort](../../build/interfaces.md#imessageport)** interface.
 

docs/learn/messaging-protocols/overview.md

@@ -14,4 +14,4 @@ The cross-chain mcessage protocol serves as the underlying technology for cross-
 | :--------: | :----------- |
 | [ORMP](./ormp.md) | Oracle Relayer Messaging Protocol, based on the Oracle mechanism, as darwinia msgport's default messaging protocol. |
 | [XCMP](./xcmp.md) | XCMP, which is based on Polkadot XCM, is on our roadmap for support. |
-| [LCMP](./lcmp.md) | Light Client Cross-Chain Messaging Protocol, used for years in Darwinia, currently replaced by ORMP. |
+| [LCMP](./lcmp.md) | Light Client Cross-chain Messaging Protocol, used for years in Darwinia, currently replaced by ORMP. |

docs/learn/use-cases/overview.md

@@ -6,9 +6,9 @@ As we explore this area, we'll look into different scenarios that highlight the
 
 | Scenarios | Description |
 | --- | --- |
-| **[Cross-Chain Abstract Account](./xaccount.md)** | Exploring the concept of multi-chains abstract account and their significance in a decentralized environment. |
-| **[Cross-Chain DAOs](./xdao.md)** | An examination of decentralized autonomous organizations operating across multiple chains, fostering a new era of governance. |
-| **[Cross-Chain Tokens](./xtoken.md)** | Exploring the management of cross-chain tokens enhanced by the functionalities of Msgport.|
+| **[Cross-chain Abstract Account](./xaccount.md)** | Exploring the concept of multi-chains abstract account and their significance in a decentralized environment. |
+| **[Cross-chain DAOs](./xdao.md)** | An examination of decentralized autonomous organizations operating across multiple chains, fostering a new era of governance. |
+| **[Cross-chain Tokens](./xtoken.md)** | Exploring the management of cross-chain tokens enhanced by the functionalities of Msgport.|
 | **[Order Clearing](./order-xclearing.md)** | See how the Msgport enhances the cross-chain settlement features of [Helix Bridge](https://helixbridge.app/).|
 
 Each topic is designed to expand your knowledge and inspire innovation in the cross-chain space. We highly value your insights and contributions and warmly invite you to propose additional use cases for inclusion.

docs/learn/use-cases/xaccount.md

@@ -1,5 +1,5 @@
-# Cross-Chain Abstract Account
+# Cross-chain Abstract Account
 
-Cross-Chain Abstract Account, embodies a pioneering approach to account abstraction at the cross-chain level. This innovative concept introduces the creation of a counterpart account on the target chain for an existing account on the source chain, which remains under the exclusive control of the original address on the source chain.
+Cross-chain Abstract Account, embodies a pioneering approach to account abstraction at the cross-chain level. This innovative concept introduces the creation of a counterpart account on the target chain for an existing account on the source chain, which remains under the exclusive control of the original address on the source chain.
 
 The [XAccount Design](https://github.com/msgport/msgport/tree/main/src/xAccount) significantly simplifies and enhances the user experience by adopting this design of cross-chain abstract accounts. As a refined iteration of Msgport’s cross-chain functionalities, XAccount is meticulously crafted to streamline the process for users involved in cross-chain transactions, making it more accessible and user-friendly. The user interface for the XAccount DApp will be available shortly. In the meantime, you can get a preview of the XAccount design through its [protocol implementation and contracts](https://github.com/msgport/msgport/tree/main/src/xAccount). It is also seamlessly integrated with the [Safe Modules](https://docs.safe.global/advanced/smart-account-modules), developed on the most secure abstract account framework.

docs/learn/use-cases/xtoken.md

@@ -1,4 +1,4 @@
-# Cross-Chain Tokens Management
+# Cross-chain Tokens Management
 
 Msgport's cross-chain functionality opens up a multitude of token management possibilities for applications. It allows issuers on either the source or target chains to set up and establish cross-chain bridge mappings for their tokens. Moreover, it acts as a utility for custodian issuers to launch Custodian DApps, which permit users to transfer the supported mapped tokens across different chains.
 

mkdocs.yml

@@ -174,9 +174,9 @@ nav:
           - LCMP Protocol: "learn/messaging-protocols/lcmp.md"
       - Use Cases:
         - Overview: "learn/use-cases/overview.md"
-        - Cross-Chain Abstract Account: "learn/use-cases/xaccount.md"
-        - Cross-Chain DAOs: "learn/use-cases/xdao.md"
-        - Cross-Chain Tokens: "learn/use-cases/xtoken.md"
+        - Cross-chain Abstract Account: "learn/use-cases/xaccount.md"
+        - Cross-chain DAOs: "learn/use-cases/xdao.md"
+        - Cross-chain Tokens: "learn/use-cases/xtoken.md"
         - Order Clearing: "learn/use-cases/order-xclearing.md"
       - Glossary: "learn/glossary.md"
       - FAQ: "learn/faq.md"