Docs small fixes

abstract-global-wallet/agw-client/createAbstractClient.mdx

@@ -108,7 +108,7 @@ If set to `false`, the client will not support offchain CCIP lookups.
     The name of the client.
   </ResponseField>
   <ResponseField name="pollingInterval" type="number">
-    Frequency (in ms) for polling enabled actions & events. Defaults to `4000` milliseconds.
+    Frequency (in ms) for polling-enabled actions & events. Defaults to `4000` milliseconds.
   </ResponseField>
   <ResponseField name="request" type="Function">
     Request function wrapped with friendly error handling.

abstract-global-wallet/agw-client/wallet-linking/overview.mdx

@@ -76,7 +76,7 @@ You can trigger this flow in your application by using the [linkToAgw](/abstract
   </Accordion>
 
   <Accordion title="delegatedWalletsByRights">
-    Given an AGW address as input, returns a list of L1 wallets that have linked to the AGW.
+    Given an AGW address as input, returns a list of L1 wallets that have been linked to the AGW.
     Use this to check what EOAs have been linked to a specific AGW (can be multiple).
 
     ```solidity

abstract-global-wallet/agw-react/hooks/useGlobalWalletSignerClient.mdx

@@ -5,7 +5,7 @@ description: Hook to get a wallet client instance of the approved signer of the
 
 import TanStackQueryReturnTypeSnippet from "/snippets/tanstack-query-return-type.mdx";
 
-Use the `useGlobalWalletSignerClient` hook to get a [wallet client](https://viem.sh/docs/clients/wallet)
+Use the `useGlobalWalletSignerClient` hook to get an [wallet client](https://viem.sh/docs/clients/wallet)
 instance that can perform actions from the underlying [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account)
 approved to sign transactions for the Abstract Global Wallet smart contract.
 

abstract-global-wallet/agw-react/hooks/useWriteContractSponsored.mdx

@@ -75,7 +75,7 @@ Returns a `UseWriteContractSponsoredReturnType<Config, unknown>`.
 </ResponseField>
 
 <ResponseField name="error" type="WriteContractErrorType | null">
-  The error if the transaction failed.
+  The error occurs if the transaction failed.
 </ResponseField>
 
 <ResponseField name="isSuccess" type="boolean">

abstract-global-wallet/architecture.mdx

@@ -5,7 +5,7 @@ description: "Learn more about how Abstract Global Wallet works under the hood."
 
 Abstract Global Wallet makes use of [native account abstraction](/how-abstract-works/native-account-abstraction),
 by creating [smart contract wallets](/how-abstract-works/native-account-abstraction/smart-contract-wallets)
-for users that have more security and flexibility than traditional EOAs.
+for users who have more security and flexibility than traditional EOAs.
 
 Users can connect their Abstract Global Wallet to an application by logging in with their email, social account, or existing wallet.
 Once connected, applications can begin prompting users to approve transactions, which are executed from the

abstract-global-wallet/session-keys/going-to-production.mdx

@@ -48,7 +48,7 @@ or will be rejected with "Unconstrained token approval/transfer destination in c
 
 Session keys specify a **signer** account; an <Tooltip tip="Externally Owned Account, i.e. a public/private key pair.">EOA</Tooltip> that is permitted to perform the actions specified in the session configuration. Therefore, the private key of the signer(s) you create are **SENSITIVE VALUES**!
 
-Exposing the signer private key enables attackers to execute any of the actions specified in a session configuration for any AGW that has approved a session key with that signer&rsquo;s address.
+Exposing the signer's private key enables attackers to execute any of the actions specified in a session configuration for any AGW that has approved a session key with that signer&rsquo;s address.
 
 ```typescript
 await agwClient.createSession({

api-reference/overview/abstract-json-rpc-api.mdx

@@ -5,7 +5,7 @@ description: "View the full reference for the Abstract JSON-RPC API."
 ---
 
 Information about the state of Abstract such as the chain ID, block number, status of transactions and state changing operations
-such as submitting transactions are executed via Abstract’s JSON RPC API.
+such as submitting transactions that are executed via Abstract’s JSON RPC API.
 The JSON RPC API has 4 namespaces:
 
 | Namespace | Description                                                    | Example           |

build-on-abstract/applications/ethers.mdx

@@ -14,7 +14,7 @@ alongside [ethers](https://docs.ethers.io/v6/).
 
 ## 1. Create a new project
 
-Create a new directory and change directory into it.
+Create a new directory and change the directory into it.
 
 ```bash
 mkdir my-abstract-app && cd my-abstract-app

build-on-abstract/smart-contracts/foundry/get-started.mdx

@@ -79,7 +79,7 @@ You may need to restart your terminal session after installation to continue.
 
 ## 2. Create a new project
 
-Create a new project with `forge` and change directory into the project.
+Create a new project with `forge` and change the directory into the project.
 
 ```bash
 forge init my-abstract-project && cd my-abstract-project

build-on-abstract/smart-contracts/foundry/installation.mdx

@@ -69,7 +69,7 @@ You may need to restart your terminal session after installation to continue.
   </Step>
   <Step title="Create a new project">
 
-    Create a new project with `forge` and change directory into the project.
+    Create a new project with `forge` and change the directory into the project.
 
     ```bash
     forge init my-abstract-project && cd my-abstract-project

build-on-abstract/smart-contracts/foundry/testing-contracts.mdx

@@ -78,7 +78,7 @@ contract HelloWorld {
     href="https://getfoundry.sh/reference/cheatcodes/overview"
 >
 
-Reference for all cheatcodes available in Foundry.
+Reference for all cheat codes available in Foundry.
 
 </Card>
 

build-on-abstract/smart-contracts/hardhat/deploying-contracts.mdx

@@ -159,7 +159,7 @@ export default async function (hre: HardhatRuntimeEnvironment) {
 
 ## Create2 & Smart Wallet Deployments
 
-Specify different deployment types through using the third `deploymentType` parameter:
+Specify different deployment types by using the third `deploymentType` parameter:
 
 - **create**: Standard contract deployment (default)
 - **create2**: Deterministic deployment using CREATE2

how-abstract-works/architecture/layer-2s.mdx

@@ -52,7 +52,7 @@ without having to re-execute the transactions on Ethereum.
 ## What is the ZK Stack?
 
 Abstract uses the [ZK stack](https://zkstack.io/components);
-an open-source framework for building sovereign ZK rollups.
+An open-source framework for building sovereign ZK rollups.
 
 <Card
   title="ZKsync Docs - ZK Stack"

how-abstract-works/evm-differences/contract-deployment.mdx

@@ -4,7 +4,7 @@ description: "Learn how to deploy smart contracts on Abstract."
 ---
 
 Unlike Ethereum, Abstract does not store the bytecode of smart contracts directly;
-instead, it stores a hash of the bytecode and publishes the bytecode itself to Ethereum.
+Instead, it stores a hash of the bytecode and publishes the bytecode itself to Ethereum.
 
 This adds several benefits to smart contract deployments on Abstract, including:
 

how-abstract-works/evm-differences/evm-opcodes.mdx

@@ -41,7 +41,7 @@ For this reason:
 ### Address Derivation
 
 The addresses of smart contracts deployed using `create` and `create2` will be different on Abstract
-than Ethereum as they use different bytecode. This means the same bytecode deployed on Ethereum
+than on Ethereum as they use different bytecode. This means the same bytecode deployed on Ethereum
 will have a different contract address on Abstract.
 
 <Accordion title="View address derivation formula">