docs: fix spelling issues

packages/hebao_v1/addresses/README.md

@@ -2,7 +2,7 @@
 
 ## How to find pretty addresses
 
-Simply run `node findaddr.js find [chunk]` to find the best address in that chunk. Currenlty 12 chunks are being explored.
+Simply run `node findaddr.js find [chunk]` to find the best address in that chunk. Currently 12 chunks are being explored.
 
 ## How to use found addresses
 

packages/hebao_v1/test/testGuardians.ts

@@ -98,7 +98,7 @@ contract("GuardiansModule-Guardian", (accounts: string[]) => {
         const owner = ctx.owners[0];
         const { wallet } = await createWallet(ctx, owner);
 
-        // The first two guardian is added WA (so cannot be cancelled)
+        // The first two guardian is added WA (so cannot be canceled)
         await addGuardianChecked(owner, wallet, ctx.guardians[0]);
         await addGuardianChecked(owner, wallet, ctx.guardians[1]);
 
@@ -143,7 +143,7 @@ contract("GuardiansModule-Guardian", (accounts: string[]) => {
         // Skip forward `guardianPendingPeriod` seconds
         await advanceTimeAndBlockAsync(guardianPendingPeriod);
 
-        // Make sure the cancelled guardian isn't a guardian
+        // Make sure the canceled guardian isn't a guardian
         assert(
           !(await ctx.securityStore.isGuardian(
             wallet,
@@ -205,7 +205,7 @@ contract("GuardiansModule-Guardian", (accounts: string[]) => {
         // Skip forward `guardianPendingPeriod` seconds
         await advanceTimeAndBlockAsync(guardianPendingPeriod);
 
-        // Make sure the cancelled guardian is still a guardian
+        // Make sure the canceled guardian is still a guardian
         assert(
           await ctx.securityStore.isGuardian(wallet, ctx.guardians[0], false),
           "should be guardian"

packages/hebao_v1/util/Events.ts

@@ -7,7 +7,7 @@ export async function getEventsFromContract(contract: any, blockIdx: number) {
 }
 
 // This works differently from truffleAssert.eventEmitted in that it also is able to
-// get events emmitted in `deep contracts` (i.e. events not emmitted in the contract
+// get events emitted in `deep contracts` (i.e. events not emitted in the contract
 // the function got called in).
 export async function assertEventsEmitted(
   contract: any,

packages/loopring_v3/DESIGN.md

@@ -319,7 +319,7 @@ Nevertheless, if the operator pays the protocol fee, why have different protocol
 
 ### AMM
 
-It is possible to enable Automated Market-Maker (AMM) functionality on an account. This is done by setting the AMM virtual balances of at least two tokens to non-zero (using [AMM Update](#AMM-Update) transactions). Once that is the done, the operator can create any orders between those tokens, without any signature or other explicit approval of the account owner, as long as the price for the order is equal or better (from the AMM's point of view) than the price required by the AMM price curve. From the protocol's point of view, AMM swaps are the same as trades between different orders, but instead of approved with a signature from the account owner, it is approved by the curve set by the account owner. The fee paid by the AMM account for the trade to the operator is enforced to be 0. The virtual balances will be updated with the same fill amounts as the actual balances.
+It is possible to enable Automated Market-Maker (AMM) functionality on an account. This is done by setting the AMM virtual balances of at least two tokens to non-zero (using [AMM Update](#AMM-Update) transactions). Once that is done, the operator can create any orders between those tokens, without any signature or other explicit approval of the account owner, as long as the price for the order is equal or better (from the AMM's point of view) than the price required by the AMM price curve. From the protocol's point of view, AMM swaps are the same as trades between different orders, but instead of approved with a signature from the account owner, it is approved by the curve set by the account owner. The fee paid by the AMM account for the trade to the operator is enforced to be 0. The virtual balances will be updated with the same fill amounts as the actual balances.
 
 The curve enforced in the protocol is the uniswap curve `x*y = k` and is defined as follows in the protocol:
 
@@ -455,7 +455,7 @@ If the operator does not process the deposit after `MAX_AGE_DEPOSIT_UNTIL_WITHDR
 Depending on the specific token, the gas cost to the user is around 60,000 gas/deposit. There are several ways not to let users pay this gas cost:
 
 - We only require users to approve the ERC20 token for the exchange (this method does not work for ETH). We can then use an agent that uses an on-chain signature of the user to make the actual deposit.
-- A simple forwarder contract is used that can only deposit funds available inside the contract for a specific user. This contract can be deployed using `CREATE2` with a deterministic address. Once the user receives this address, the user can then do a simple transfer to this smart contract's address as usual. Anyone willing to pay the gas cost (in exchange for a fee paid by the user) can create the contract and deposit the funds (remember that how and to who is hardcoded inside the generated smart contract so this is always safe and trustless). Afterward, the smart contract can directly be destroyed to recoup the deployment gas cost partly.
+- A simple forwarder contract is used that can only deposit funds available inside the contract for a specific user. This contract can be deployed using `CREATE2` with a deterministic address. Once the user receives this address, the user can then do a simple transfer to this smart contract's address as usual. Anyone willing to pay the gas cost (in exchange for a fee paid by the user) can create the contract and deposit the funds (remember how and to who is hardcoded inside the generated smart contract so this is always safe and trustless). Afterward, the smart contract can directly be destroyed to recoup the deployment gas cost partly.
 
 Both methods allow the user to pay for the deposit in any token (on layer 1 or layer 2).