docs: fix typos (#1101)

docs/website/pages/blog/from-web2.5-to-web3.en-US.mdx

@@ -117,15 +117,15 @@ The programming language for Web3 Apps should be optimized for describing assets
 
 [Move Language](https://github.com/move-language/move) is an object-oriented programming language. It is designed to address this balance issue.
 
-With Move, developers can use `struct` to define arbitrary types of assets. The assets can also be passed into functions as arguments, so that all the assets can be flexibly operated by different smart contracts. In the meantime, the creation, destruction, and ownership of the assets are explicity defined with language declarations, giving language level safety to all the assets defined by Move Language.
+With Move, developers can use `struct` to define arbitrary types of assets. The assets can also be passed into functions as arguments, so that all the assets can be flexibly operated by different smart contracts. In the meantime, the creation, destruction, and ownership of the assets are explicitly defined with language declarations, giving language level safety to all the assets defined by Move Language.
 
 As a new programming language, Move is promoted by more than just one communities and projects. (See [Awesome-Move](https://awesome-move.com/#move-powered-blockchains) for a list of Move powered blockchains) This gives it great potential to grow into a much popular choice of language in the future.
 
 Move Language also has built-in support for features such as contract upgradability and account abstraction, making it easier for App builders to eliminate pain points for their users.
 
 ## Conclusion
 
-In this article we have discussed 6 key questions regarding how we achieve true Web3, including a back-to-back comparsion between Web2.5 Apps and Web3 Apps in terms wether they could achieve these Web3 features.
+In this article we have discussed 6 key questions regarding how we achieve true Web3, including a back-to-back comparison between Web2.5 Apps and Web3 Apps in terms wether they could achieve these Web3 features.
 
 <Image
   src="/docs/web3-comparsion.png"

docs/website/pages/blog/triple-iron-curtains-before-da.en-US.mdx

@@ -105,7 +105,7 @@ Three iron curtains have opened up since then.
 ## The First Iron Curtain: Proof of Persistence
 
 Let's look at the first iron curtain of DV (Data Visibility), which is the equivalent of proving that the water coming out of a pipe came from its own reservoir or was pumped from somewhere else.
-This seemingly unsolvable problem is one that DV has to face, becasue water is H₂O in everywhere.
+This seemingly unsolvable problem is one that DV has to face, because water is H₂O in everywhere.
 This is because every piece of data in DV has open multi-node access redundancy, so as long as there is an honest node that holds that piece of data, every other node can forward a client read request.
 
 The most serious cost of this problem is not in terms of unjust enrichment, but in terms of the reliability risk faced. This risk manifests itself in different ways in different forms of DV data distribution:

docs/website/pages/blog/weekly-230711.en-US.mdx

@@ -44,7 +44,7 @@ Finally, the second phase of the Rooch milestone was successfully completed, and
 
 - **[MoveOS] Execute `pre_execute` function before transaction execute  (#322)** (2023-06-19) @jolestar
 - **[types] Unify the ObjectID and AccountAddress json output (#328)** (2023-06-21) @jolestar
-- **[MoveosStdlib] Public the `destory_empty` function in table,type_table,object_storage module (#344)** (2023-06-24) @jolestar
+- **[MoveosStdlib] Public the `destroy_empty` function in table,type_table,object_storage module (#344)** (2023-06-24) @jolestar
 - **Remove TxContext from the check in the entry function. (#360)** (2023-06-27) @steelgeek091
 - **Rename framework modules (#361)** (2023-06-27) @jolestar
 - **Remove the TxContext in the move test file. (#362)** (2023-06-27) @steelgeek091

docs/website/pages/blog/weekly-230711.zh-CN.mdx

@@ -44,7 +44,7 @@ import PostHeader from "/components/blog/postHeader";
 
 - **[MoveOS] Execute `pre_execute` function before transaction execute  (#322)** (2023-06-19) @jolestar
 - **[types] Unify the ObjectID and AccountAddress json output (#328)** (2023-06-21) @jolestar
-- **[MoveosStdlib] Public the `destory_empty` function in table,type_table,object_storage module (#344)** (2023-06-24) @jolestar
+- **[MoveosStdlib] Public the `destroy_empty` function in table,type_table,object_storage module (#344)** (2023-06-24) @jolestar
 - **Remove TxContext from the check in the entry function. (#360)** (2023-06-27) @steelgeek091
 - **Rename framework modules (#361)** (2023-06-27) @jolestar
 - **Remove the TxContext in the move test file. (#362)** (2023-06-27) @steelgeek091

docs/website/pages/blog/weekly-230814.en-US.mdx

@@ -37,7 +37,7 @@ import PostHeader from "/components/blog/postHeader";
 
 - **add weekly 2023-08-07 (#579)** (2023-08-07) @Joe Chen
 - **Modify the names in CODEOWNER. (#596)** (2023-08-09) @stevenlaw123
-- **Storage reload consistance testcase (#603)** (2023-08-10) @Bai Chuan
+- **Storage reload consistency testcase (#603)** (2023-08-10) @Bai Chuan
 - **[gh-574] add docs for the rooch account command. (#601)** (2023-08-10) @feliciss
 - **docs: update multi-chain settlement workflow (#606)** (2023-08-11) @y17b
 - **add doc comment and fix typo for the server command (#611)** (2023-08-11) @Joe Chen

docs/website/pages/blog/weekly-230814.zh-CN.mdx

@@ -37,7 +37,7 @@ import PostHeader from "/components/blog/postHeader";
 
 - **add weekly 2023-08-07 (#579)** (2023-08-07) @Joe Chen
 - **Modify the names in CODEOWNER. (#596)** (2023-08-09) @stevenlaw123
-- **Storage reload consistance testcase (#603)** (2023-08-10) @Bai Chuan
+- **Storage reload consistency testcase (#603)** (2023-08-10) @Bai Chuan
 - **[gh-574] add docs for the rooch account command. (#601)** (2023-08-10) @feliciss
 - **docs: update multi-chain settlement workflow (#606)** (2023-08-11) @y17b
 - **add doc comment and fix typo for the server command (#611)** (2023-08-11) @Joe Chen

docs/website/pages/blog/weekly-230925.en-US.mdx

@@ -30,7 +30,7 @@ import PostHeader from "/components/blog/postHeader";
 - **docs(miscellaneous): add the contributing guide (#832)** (2023-09-20) @Joe Chen
 - **[doc] Add more diagram for multi-chain settlement (#836)** (2023-09-20) @jolestar
 - **fix/transaction (#834)** (2023-09-20) @sven Tan
-- **docs: add the dashbaord intro document (#837)** (2023-09-21) @Joe Chen
+- **docs: add the dashboard intro document (#837)** (2023-09-21) @Joe Chen
 - **docs(data flow): refine tx & l1tol2 messaging & add l2tol1 messaging (#843)** (2023-09-21) @popcnt
 - **env add test net (#846)** (2023-09-21) @sven Tan
 - **docs(multi-chain): update multi-chain-settlement with content from the latest cross-layer communications article (#848)** (2023-09-21) @popcnt

docs/website/pages/blog/weekly-230925.zh-CN.mdx

@@ -30,7 +30,7 @@ import PostHeader from "/components/blog/postHeader";
 - **docs(miscellaneous): add the contributing guide (#832)** (2023-09-20) @Joe Chen
 - **[doc] Add more diagram for multi-chain settlement (#836)** (2023-09-20) @jolestar
 - **fix/transaction (#834)** (2023-09-20) @sven Tan
-- **docs: add the dashbaord intro document (#837)** (2023-09-21) @Joe Chen
+- **docs: add the dashboard intro document (#837)** (2023-09-21) @Joe Chen
 - **docs(data flow): refine tx & l1tol2 messaging & add l2tol1 messaging (#843)** (2023-09-21) @popcnt
 - **env add test net (#846)** (2023-09-21) @sven Tan
 - **docs(multi-chain): update multi-chain-settlement with content from the latest cross-layer communications article (#848)** (2023-09-21) @popcnt

docs/website/pages/docs/miscellaneous/faq.en-US.mdx

@@ -2,7 +2,7 @@
 
 In this document you can find answers to several questions we have frequently been asked.
 
-## What are the applications Rooch is targetting as an infrastructure? How does Rooch attract users and developers?
+## What are the applications Rooch is targeting as an infrastructure? How does Rooch attract users and developers?
 All the Modular blockchain infras, including us, we are trying to push the boundary of blockchain technology, so the blockchain applications can grow in an environment that has less limits and more features.
 The problem of what we can do with "less limits and more features", I believe, is a shared problem for all Layer2 or Modular Infras.  
 

docs/website/pages/docs/rooch.en-US.mdx

@@ -3,7 +3,7 @@
 Rooch is a smart contract execution runtime with the following features:
 
 - **MoveVM** - Rooch embeds a full MoveVM for developers to program the smart contracts with Move Language
-- **Scalable** - Rooch is a fast execution environment that can achieve 100k peak TPS when composed in a netwrok
+- **Scalable** - Rooch is a fast execution environment that can achieve 100k peak TPS when composed in a network
 - **Modular** - Rooch has abstracted interfaces which enables different DA Layer, Settlement Layer and Arbitration Layer to be integrated
 
 ## Architecture
@@ -19,7 +19,7 @@ import Image from "next/image";
 />
 
 - **RPC** - RPC component provides access endpoint for users and developers to upload Move modules as well as send transactions to call contracts and native functions
-  - **RPC Proxy** is a special componenet designed for interpreting differernt transaction structures to the native schema to allow users sending transactions directly from all kinds of wallets in the market. E.g. users can directly send transactions from MetaMask to call a Move contract on Rooch
+  - **RPC Proxy** is a special components designed for interpreting differernt transaction structures to the native schema to allow users sending transactions directly from all kinds of wallets in the market. E.g. users can directly send transactions from MetaMask to call a Move contract on Rooch
 - **MoveOS** - MoveOS is the component that does all the computational and storage work
   - **flexEmu** is a general purpose MIPS emulator that generates [Fraud Proof](/docs/tech-highlights/fraud-proof) for exeuction
   - **MoveVM** is a full function turing-complete VM that executes smart contracts written in [Move Language](/docs/tech-highlights/move-language)

docs/website/pages/docs/tech-highlights/fraud-proof.en-US.mdx

@@ -45,5 +45,5 @@ flexEmu is designed to be a general purpose bytecode emulator with per-step stat
 
 - **Compatibility with Arbitrary Layer1**
   Any Layer1 that supports MIPS operation code set will be able to arbitrate proofs generated by flexEmu. This enables Rooch to be Layer2 for arbitrary Layer1s.
-- **Easy for Maintainance, Debugging and Upgrades**
+- **Easy for Maintenance, Debugging and Upgrades**
   If there are any major upgrades to MoveVM in the future, flexEmu can quickly accommodate them.

docs/website/pages/docs/tech-highlights/hybrid-security.en-US.mdx

@@ -20,6 +20,6 @@ With only Fraud Proof, a user's withdraw transaction submitted at `BlockT` needs
 
 With ZK Proof generated by ZK Prover using zkMove, the challenge period can be optimized to a much lower amount of blocks. Here's how it works:
 
-- The proposer keeps commiting blocks of state to Layer1 at its maxmium speed
+- The proposer keeps committing blocks of state to Layer1 at its maxmium speed
 - ZK Prover generate ZK Proofs for the state blocks that have been committed to the Layer1, at a relatively slower pace, due to the considerably long proof generation time
 - For the withdraw transaction submitted at `BlockT`, it can be considered finalized when the ZK Proof of `BlockT` has been generated and verified on Layer1, instead of waiting to reach the end of the whole challenge period