Fix spelling and grammar

build-modules/erc4337-validation/overview.mdx

@@ -11,7 +11,7 @@ This library allows you to validate:
 - [x] Banned storage locations
 - [x] Disallowed `*CALLs`
 - [x] Disallowed use of `EXT*` opcodes
-- [x] Disallowed use `CREATE` opcode
+- [x] Disallowed use of `CREATE` opcode
 
 It also supports both `v0.6` and `v0.7` of ERC-4337.
 

build-modules/guides/testing/calculating-gas.mdx

@@ -59,6 +59,6 @@ Note that if you re-run gas calculations, then the newest number will be added a
 All numbers are in gas units. To calculate the cost in gwei, follow the instructions below:
 
 - On L1: multiply the total gas used by the gas price in gwei: `totalGasUsed * gasPrice`
-- On an L2: multiply the total gas used by the L2 gas price in gwei and then add it to to the result of the relevant L2-L1 gas cost muliplied by the L1 gas cost in gwei: `totalGasUsed * l2GasPrice + callDataGasUsed * l1GasPrice`
+- On an L2: multiply the total gas used by the L2 gas price in gwei and then add it to the result of the relevant L2-L1 gas cost multiplied by the L1 gas cost in gwei: `totalGasUsed * l2GasPrice + callDataGasUsed * l1GasPrice`
 
 Note: if you are calculating the dollar amount of the gas cost, make sure to use the relevant gwei to usd conversions if the L2 has a different gas token to L1.

build-modules/module-registry/integrations/wallet.mdx

@@ -5,13 +5,13 @@ sidebarTitle: "Wallet"
 
 If your smart wallet uses an ERC-7579 account with a native registry integration, such as Safe7579 or Biconomy Nexus, then all you need to do is to make sure that the registry is set up correctly. If your chosen account does not have a native registry integration, then you can add this to the accounts of your users by simply installing a module, the registry hook.
 
-### Create the users smart account
+### Create the user's smart account
 
 Using your preferred way, create a smart account for the user. Some smart accounts will allow you to provide initial modules to be installed on creation. However, if this is not the case, you can install the registry hook module after the smart account is created. In the following, we will show you how to install the registry hook module after account creation.
 
 ### Install the ModuleSDK
 
-To install a module on the users smart account, you will need to use the `installModule` function. This function will install the module on the smart account and execute the module's `onInstall` function. So, to be able to call this function, you will need to have the module's address, the module type id and the initData. This can be done most easily using the [ModuleSDK](/module-sdk).
+To install a module on the user's smart account, you will need to use the `installModule` function. This function will install the module on the smart account and execute the module's `onInstall` function. So, to be able to call this function, you will need to have the module's address, the module type id and the initData. This can be done most easily using the [ModuleSDK](/module-sdk).
 
 First, install the ModuleSDK:
 

build-modules/reference/building/hooks/onUninstallModule.mdx

@@ -2,7 +2,7 @@
 title: "onUninstallModule"
 ---
 
-A virtual function called when a module is uninstalled on the account. Overwrites from `ERC7579HookDestruct`.
+A virtual function called when a module is uninstalled on the account. Overrides from `ERC7579HookDestruct`.
 
 ## Usage
 

build-modules/reference/building/hooks/preCheck.mdx

@@ -2,7 +2,7 @@
 title: "_preCheck"
 ---
 
-A virtual function called before executions occured on the account. Overwrites from `ERC7579HookDestruct`.
+A virtual function called before executions occurred on the account. Overwrites from `ERC7579HookDestruct`.
 
 ## Usage
 

build-modules/reference/building/scheduling-module/executeOrder.mdx

@@ -1,7 +1,7 @@
 ---
 title: "executeOrder"
 ---
-A virtual function called when a scheduled execution should occur. Overwrites from `SchedulingBase`.
+A virtual function called when a scheduled execution should occur. Overrides from `SchedulingBase`.
 
 ## Usage
 

build-modules/reference/building/smart-sessions/checkAction.mdx

@@ -1,7 +1,7 @@
 ---
 title: "checkAction"
 ---
-A virtual function called when the session is being used to verify the individual calls of a UserOperation. Overwrites from `ERC7579ActionPolicy`.
+A virtual function called when the session is being used to verify the individual calls of a UserOperation. Overrides from `ERC7579ActionPolicy`.
 
 ## Usage
 

build-modules/reference/building/smart-sessions/checkUserOp.mdx

@@ -1,7 +1,7 @@
 ---
 title: "checkUserOp"
 ---
-A virtual function called when the session is being used to verify a UserOperation. Overwrites from `ERC7579UserOpPolicy`.
+A virtual function called when the session is being used to verify a UserOperation. Overrides from `ERC7579UserOpPolicy`.
 
 ## Usage
 

home/resources/fees.mdx

@@ -11,7 +11,7 @@ The transaction infrastructure has no API fee. The stakeholders in the transacti
 
 **Same chain intents are free**. 
 
-Solvers are incentivised to fill these transactions for two reasons:
+Solvers are incentivized to fill these transactions for two reasons:
 
 - The solver takes a small premium on gas (see below).