fix: quick pass to fix typos

docs/README.md

@@ -12,7 +12,7 @@ aa-sdk/
 │   ├── docs.yml         # The main configuration file that defines the documentation structure and sidebar navigation
 │   ├── pages/           # Contains the documentation markdown files
 │   ├── images/          # Contains images used in the documentation
-│   ├── components/      # Contains the all custom React components used in markdown
+│   ├── components/      # Contains all the custom React components used in markdown
 |   ├── specs/           # Contains OpenRPC and OpenAPI spec definitions which are dereferenced during build
 |   └── api-generators/  # Contains generators.yaml files used by Fern to reference API specs
 └── docs-site/           # Git Submodule containing Fern and all non-wallet docs content

docs/pages/reference/account-kit/infra/functions/isAlchemyTransport.mdx

@@ -7,7 +7,7 @@ slug: wallets/reference/account-kit/infra/functions/isAlchemyTransport
 
 A type guard for the transport to determine if it is an Alchemy transport.
 Used in cases where we would like to do switching depending on the transport, where there used
-to be two clients for a alchemy and a non alchemy, and with this switch we don't need the two seperate clients. \*
+to be two clients for an alchemy and a non alchemy, and with this switch we don't need the two separate clients. \*
 
 ## Import
 

docs/pages/signer/as-an-eoa.mdx

@@ -9,7 +9,7 @@ slug: wallets/signer/as-an-eoa
   sponsorship, batched transactions, multi-owner, or plugins. If you want to
   switch from EOA to smart accounts later, then each user will need to transfer
   their assets from the EOA account to a new smart account. It is not currently
-  possible to "upgrade" and EOA to a smart contract account, although the
+  possible to "upgrade" an EOA to a smart contract account, although the
   community is discussing potential
   [EIPs](https://eips.ethereum.org/EIPS/eip-7377) to do that in the future.
 </Warning>

docs/pages/signer/authentication/auth0.mdx

@@ -16,7 +16,7 @@ You’ll also be able to select the attributes and permissions you will be reque
 
 <img
   src="/images/wallets/auth0-config.png"
-  alt="Configure Github auth provider settings Auth0"
+  alt="Configure GitHub auth provider settings Auth0"
 />
 
 Also on this page, note the “Name” field containing “github”. This will be used later as a variable in adding authentication to your app.

docs/pages/smart-contracts/other-accounts/light-account/index.mdx

@@ -29,5 +29,5 @@ Multi-Owner Light Account uses v0.7 of the entry point.
 ## Developer links
 
 - [Light Account deployment addresses](/wallets/smart-contracts/deployed-addresses)
-- [Light Account Github repo](https://github.com/alchemyplatform/light-account)
+- [Light Account GitHub repo](https://github.com/alchemyplatform/light-account)
 - [Quantstamp audit report](https://github.com/alchemyplatform/light-account/blob/develop/audits/2024-04-26_quantstamp_93f46a2.pdf)

docs/pages/smart-contracts/other-accounts/modular-account/session-keys/supported-permissions.mdx

@@ -36,21 +36,21 @@ Note that the gas limit is tracked in terms of native token units (wei), not in
 
 Permissions start with the following default values:
 
-| Permission               | Default Value                                                                                                                                    |
-| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Access control list      | Type: allowlist <br /> The list starts empty. When the allowlist is empty, all calls will be denied.                                             |
-| Time range               | Unlimited                                                                                                                                        |
-| Native token spend limit | 0 <br /> This means all calls spending the native token will be denied, unless the limit is updated or removed.                                  |
-| ERC-20 spend limit       | Unset. If you want to enabled an ERC-20 spend limit, add the ERC-20 token contract to the access control list and set the spending limit amount. |
-| Gas spend limits         | Unset. When defining the session key’s permissions, you should specify either a gas spending limit or a required paymaster.                      |
+| Permission               | Default Value                                                                                                                                   |
+| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- |
+| Access control list      | Type: allowlist <br /> The list starts empty. When the allowlist is empty, all calls will be denied.                                            |
+| Time range               | Unlimited                                                                                                                                       |
+| Native token spend limit | 0 <br /> This means all calls spending the native token will be denied, unless the limit is updated or removed.                                 |
+| ERC-20 spend limit       | Unset. If you want to enable an ERC-20 spend limit, add the ERC-20 token contract to the access control list and set the spending limit amount. |
+| Gas spend limits         | Unset. When defining the session key’s permissions, you should specify either a gas spending limit or a required paymaster.                     |
 
 ## Using the PermissionsBuilder
 
 To construct the data to set a key's permissions, you will need to use the `SessionKeyPermissionBuilder` class. This will allow you to specify a series of updates, and when complete, you may generate the encoded data to perform all updates at once.
 
 The permissions data may be specified in 3 places:
 
-- In the Session Key Plugin's `onInstall` data, setting the intial permissions for a session key added at install time.
+- In the Session Key Plugin's `onInstall` data, setting the initial permissions for a session key added at install time.
 - As data for the initial permissions of a session key added via `addSessionKey`.
 - As a parameter to the `updateKeyPermissions` function, to change the permissions of an existing key.