Apply suggestions from code review

Co-authored-by: Alexandra Carrillo <[email protected]>

Author: AyushBherwani1998

delegation-toolkit/concepts/smart-accounts.md

@@ -56,12 +56,12 @@ The signatory must have at least as many signers include as the threshold is con
 
 This type is referenced in the toolkit as `Implementation.Multisig`.
 
-### Statless 7702 smart account
+### Stateless 7702 smart account
 
-The Stateless 7702 smart account implementation represents an Externally Owned Account (EOA) upgraded to
-support smart account functionality as defined by the [EIP-7702 standard](https://eips.ethereum.org/EIPS/eip-7715). This implementation enables EOAs to perform smart account operations, including the creation and management of delegations.
+The Stateless 7702 smart account implementation represents an externally owned account (EOA) upgraded to
+support smart account functionality as defined by [EIP-7702](https://eips.ethereum.org/EIPS/eip-7702). This implementation enables EOAs to perform smart account operations, including the creation and management of delegations.
 
-This type is reference in the toolkit as `Implementation.Stateless7702`.
+This type is referenced in the toolkit as `Implementation.Stateless7702`.
 
 ## Smart account flow
 

delegation-toolkit/get-started/eip7702-quickstart.md

@@ -1,13 +1,13 @@
 ---
-description: Upgrade an externally owned account(EOA) to smart account
+description: Upgrade an externally owned account (EOA) to a smart account
 sidebar_position: 3
-sidebar_label: EIP-7702 Quickstart
+sidebar_label: EIP-7702 quickstart
 ---
 
-# EIP-7702 Quickstart
+# EIP-7702 quickstart
 
-This page demonstrates how to upgrade your Externally Owned Account (EOA) to support MetaMask smart account 
-functionality using an EIP-7702 transaction. This enables your EOA to leverage the benefits of account 
+This page demonstrates how to upgrade your externally owned account (EOA) to support MetaMask smart account 
+functionality using an [EIP-7702](https://eips.ethereum.org/EIPS/eip-7702) transaction. This enables your EOA to leverage the benefits of account 
 abstraction, such as batch transactions, gas sponsorship, and [ERC-7710 delegation capabilities](./../concepts/delegation.md).
 
 ## Prerequisites
@@ -64,13 +64,13 @@ export const walletClient = createWalletClient({
 })
 ```
 
-### 4. Authorize 7702 delegation
+### 4. Authorize a 7702 delegation
 
-Create an authorization to map the contract code to EOA, and sign it 
-using `signAuthorization` action. Please note, the `signAuthorization` action 
+Create an authorization to map the contract code to an EOA, and sign it 
+using Viem's [`signAuthorization`](https://viem.sh/docs/eip7702/signAuthorization) action. The `signAuthorization` action 
 does not support JSON-RPC accounts.
 
-In this quickstart, we use [`EIP7702StatelessDeleGator`](https://github.com/MetaMask/delegation-framework/blob/main/src/EIP7702/EIP7702StatelessDeleGator.sol) as the EIP-7702 delegator contract. 
+This example uses [`EIP7702StatelessDeleGator`](https://github.com/MetaMask/delegation-framework/blob/main/src/EIP7702/EIP7702StatelessDeleGator.sol) as the EIP-7702 delegator contract. 
 It follows a stateless design, as it does not store signer data in the contract's state. This approach
 provides a lightweight and secure way to upgrade an EOA to a smart account.
 
@@ -94,8 +94,8 @@ const authorization = await walletClient.signAuthorization({
 
 ### 5. Submit the authorization
 
-Once you have signed an authroization, you can send an EIP-7702 transaction to set the EOA code.
-Since the authorization cannot be sent as standlone, you can include it alongside a dummy transaction.
+Once you have signed an authorization, you can send an EIP-7702 transaction to set the EOA code.
+Since the authorization cannot be sent by itself, you can include it alongside a dummy transaction.
 
 ```ts
 import { zeroAddress } from "viem";
@@ -107,9 +107,9 @@ const hash = await walletClient.sendTransaction({
 });
 ```
 
-### 6. Create MetaMask smart account
+### 6. Create a MetaMask smart account
 
-After successfully setting the EOA code, you can create a smart account instance for the EOA and start 
+Create a smart account instance for the EOA and start 
 leveraging the benefits of account abstraction.
 
 ```ts
@@ -131,7 +131,7 @@ const smartAccount = await toMetaMaskSmartAccount({
 
 ### 7. Send a user operation
 
-To send a user operation through the upgraded EOA, use the Viem's [`sendUserOperation`](https://viem.sh/account-abstraction/actions/bundler/sendUserOperation) method.
+Send a user operation through the upgraded EOA, using Viem's [`sendUserOperation`](https://viem.sh/account-abstraction/actions/bundler/sendUserOperation) method.
 
 ```ts
 import { parseEther } from "viem";

delegation-toolkit/how-to/create-smart-account/configure-accounts-signers.md

@@ -318,16 +318,15 @@ The number of signers in the signatories must be at least equal to the threshold
 
 ## Configure a Stateless 7702 smart account
 
-The Stateless 7702 smart account represents an EOA that has been upgraded to support smart account 
-functionality as defined by the [EIP-7702 standard](https://eips.ethereum.org/EIPS/eip-7715). This implementation does not handle the upgrade process 
-itself, see [7702 Quickstart](./../../get-started/7702-quickstart.md) to learn how to ugrade.
+The [Stateless 7702 smart account](../../concepts/smart-accounts.md#stateless-7702-smart-account) represents an EOA that has been upgraded to support smart account 
+functionality as defined by [EIP-7702](https://eips.ethereum.org/EIPS/eip-7702). This implementation does not handle the upgrade process; see the [EIP-7702 quickstart](./../../get-started/7702-quickstart.md) to learn how to upgrade.
 
 To configure a Stateless 7702 smart account, provide the following parameters:
 
 - `address`: The address of the EOA that has been upgraded to a smart account.
 - `signatory`: A signer that will sign on behalf of the smart account.
 
-For a Statless 7702 smart account, you can configure the following types of signatories:
+For a Stateless 7702 smart account, you can configure the following types of signatories:
 
 ### Configure an account signatory
 
@@ -346,7 +345,7 @@ import {
 
 const smartAccount = await toMetaMaskSmartAccount({
   client: publicClient,
-  implementation: Implementation.Statless7702,
+  implementation: Implementation.Stateless7702,
   address: account.address
   signatory: { account },
 });

delegation-toolkit/reference/api/delegation.md

@@ -92,7 +92,7 @@ Creates a delegation with specific delegate.
 | `from` | `Hex` | Yes | The address that is granting the delegation. |
 | `to` | `Hex` | Yes | The address to which the delegation is being granted. |
 | `caveats` | `Caveats` | Yes | Caveats to restrict the authority being granted. |
-| `parentDelegation` | `Delegation \| Hex` | No | The parent delegation or it's corresponding hex to create a delegation chain. |
+| `parentDelegation` | `Delegation \| Hex` | No | The parent delegation or its corresponding hex to create a delegation chain. |
 | `salt` | `Hex` | No | The salt for generating the delegation hash. This helps prevent hash collisions when creating identical delegations. |
 
 ### Example
@@ -120,7 +120,7 @@ Creates an open delegation that can be redeemed by any delegate.
 | ---- | ---- | -------- | ----------- |
 | `from` | `Hex` | Yes | The address that is granting the delegation. |
 | `caveats` | `Caveats` | Yes | Caveats to restrict the authority being granted. |
-| `parentDelegation` | `Delegation \| Hex` | No | The parent delegation or it's corresponding hex to create a delegation chain. |
+| `parentDelegation` | `Delegation \| Hex` | No | The parent delegation or its corresponding hex to create a delegation chain. |
 | `salt` | `Hex` | No | The salt for generating the delegation hash. This helps prevent hash collisions when creating identical delegations. |