follow new rebrand guidelines

Author: alexandratran

delegation-toolkit/concepts/delegation.md

@@ -5,7 +5,7 @@ sidebar_position: 2
 
 # Delegation
 
-*Delegation* is the ability for a [Smart Account](smart-accounts.md) to grant permission to another Smart Account
+*Delegation* is the ability for a [MetaMask smart account](smart-accounts.md) to grant permission to another smart account
 or externally owned account (EOA) to perform specific executions on their behalf, under defined rules and restrictions.
 The account that grants the permission is called the *delegator account*, while the account that receives the permission
 is called the *delegate account*.

delegation-toolkit/concepts/environment.md

@@ -18,7 +18,7 @@ The delegator environment serves several key purposes:
 
 ## Resolve the delegator environment
 
-When you create a [MetaMask Smart Account](smart-accounts.md), the Delegation Toolkit automatically
+When you create a [MetaMask smart account](smart-accounts.md), the Delegation Toolkit automatically
 resolves the environment based on the version it requires and the chain configured.
 If no environment is found for the specified chain, it throws an error.
 
@@ -70,7 +70,7 @@ See the changelog of the toolkit version you are using (in the left sidebar) for
 :::
 
 Alternatively, you can use the [`getDelegatorEnvironment`](../reference/api/delegation.md#getdelegatorenvironment) function to resolve the environment.
-This function is especially useful if your delegator is not a Smart Account when
+This function is especially useful if your delegator is not a smart account when
 [creating a redelegation](../how-to/create-delegation/index.md#create-a-redelegation).
 
 ```typescript

delegation-toolkit/concepts/smart-accounts.md

@@ -6,12 +6,12 @@ sidebar_position: 1
 # MetaMask Smart Accounts
 
 The MetaMask Delegation Toolkit enables you to create and manage MetaMask Smart Accounts.
-Smart Accounts are [ERC-4337](https://eips.ethereum.org/EIPS/eip-4337) smart contract accounts
+MetaMask Smart Accounts are [ERC-4337](https://eips.ethereum.org/EIPS/eip-4337) smart contract accounts
 that support programmable account behavior and advanced features such as multi-signature approvals,
 automated transaction batching, and custom security policies.
-Unlike traditional wallets, which rely on private keys for every transaction, MetaMask Smart Accounts use smart contracts to govern account logic.
+Unlike traditional wallets, which rely on private keys for every transaction, smart accounts use smart contracts to govern account logic.
 
-Smart Accounts are referenced in the toolkit as `MetaMaskSmartAccount`.
+Smart accounts are referenced in the toolkit as `MetaMaskSmartAccount`.
 
 ## Account abstraction (ERC-4337)
 
@@ -23,7 +23,7 @@ accounts, or externally owned accounts (EOAs).
 ERC-4337 introduces the following concepts:
 
 - **User operation** - A package of instructions signed by a user, specifying executions for
-  the Smart Account to perform.
+  the smart account to perform.
   User operations are collected and submitted to the network by bundlers.
 
 - **Bundler** - A service that collects multiple user operations, packages them into a single transaction,
@@ -33,42 +33,42 @@ ERC-4337 introduces the following concepts:
   adhere to the required rules and security checks.
 
 - **Paymasters** - Entities that handle the payment of gas fees on behalf of users, often integrated
-  into Smart Accounts to facilitate gas abstraction.
+  into smart accounts to facilitate gas abstraction.
 
-## Smart Account implementation types
+## Smart account implementation types
 
-The MetaMask Delegation Toolkit supports three types of Smart Accounts, each offering unique features and use cases.
+The MetaMask Delegation Toolkit supports three types of MetaMask Smart Accounts, each offering unique features and use cases.
 
 See [Configure accounts and signers](../how-to/create-smart-account/configure-accounts-signers.md) to learn how to use these different account types.
 
-### Hybrid Smart Account
+### Hybrid smart account
 
-The Hybrid Smart Account is a flexible implementation that supports both an externally owned account (EOA) "owner" and any number of P256 (passkey) signers.
-You can configure any of these signers as the signatory, and use them to sign any data, including user operations, on behalf of the Smart Account.
+The Hybrid smart account is a flexible implementation that supports both an externally owned account (EOA) "owner" and any number of P256 (passkey) signers.
+You can configure any of these signers as the signatory, and use them to sign any data, including user operations, on behalf of the smart account.
 
 This type is referenced in the toolkit as `Implementation.Hybrid`.
 
-### Multisig Smart Account
+### Multisig smart account
 
-The Multisig Smart Account is an implementation that supports multiple signers with a configurable threshold for valid signatures, allowing for enhanced security and flexibility in account management.
+The Multisig smart account is an implementation that supports multiple signers with a configurable threshold for valid signatures, allowing for enhanced security and flexibility in account management.
 The signatory must have at least as many signers include as the threshold is configured for the account.
 
 This type is referenced in the toolkit as `Implementation.Multisig`.
 
-### Stateless 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 [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.
+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 referenced in the toolkit as `Implementation.Stateless7702`.
 
-## Smart Account flow
+## Smart account flow
 
-The MetaMask Smart Account flow is as follows:
+The MetaMask Smart Accounts flow is as follows:
 
-1. **Account setup** - A user creates a Smart Account by deploying a smart contract, and initializing it with
+1. **Account setup** - A user creates a smart account by deploying a smart contract, and initializing it with
    ownership and security settings.
-   The user can customize the Smart Account in the following ways:
+   The user can customize the smart account in the following ways:
 
     - **Account logic** - They can configure custom logic for actions such as multi-signature
       approvals, spending limits, and automated transaction batching.
@@ -90,6 +90,6 @@ The MetaMask Smart Account flow is as follows:
 
 ## Delegator accounts
 
-Delegator accounts are a type of Smart Account that allows users to grant permission to other Smart Accounts or EOAs
+Delegator accounts are a type of MetaMask smart account that allows users to grant permission to other smart accounts or EOAs
 to perform specific executions on their behalf, under defined rules and restrictions.
 Learn more about [delegation](delegation.md).

delegation-toolkit/experimental/erc-7710-redeem-delegations.md

@@ -12,8 +12,8 @@ import TabItem from "@theme/TabItem";
 This is an experimental feature and may change in future releases.
 :::
 
-[ERC-7710](https://eip.tools/eip/7710) introduces a standard way for Smart Accounts to delegate capabilities to other
-Smart Accounts or externally owned accounts (EOAs).
+[ERC-7710](https://eip.tools/eip/7710) introduces a standard way for MetaMask Smart Accounts to delegate capabilities to other
+smart accounts or externally owned accounts (EOAs).
 
 The MetaMask Delegation Toolkit provides two experimental functions, `erc7710BundlerActions()` and `erc7710WalletActions()`, that let
 a caller redeem delegations granted by MetaMask's permissions system.
@@ -57,7 +57,7 @@ const permissionsResponse = [{
 
 const permissionsContext = permissionsResponse[0].context;
 const delegationManager = permissionsResponse[0].signerMeta.delegationManager;
-// accountMeta is only present when the Smart Account is not deployed.
+// accountMeta is only present when the smart account is not deployed.
 const accountMetadata = permissionsResponse[0].accountMeta;
 ```
 
@@ -80,11 +80,11 @@ If you redeem delegations in any other way, it is your responsibility to validat
 
 ## Redeem the permission
 
-Redeem a delegation with a [Smart Account](#redeem-with-a-smart-account) or an [externally owned account (EOA)](#redeem-with-an-eoa).
+Redeem a delegation with a [MetaMask smart account](#redeem-with-a-metamask-smart-account) or an [externally owned account (EOA)](#redeem-with-an-eoa).
 
-### Redeem with a Smart Account
+### Redeem with a MetaMask smart account
 
-To redeem a delegation with a Smart Account, create a [`MetaMaskSmartAccount`](../how-to/create-smart-account/index.md#create-a-metamasksmartaccount)
+To redeem a delegation with a MetaMask smart account, create a [`MetaMaskSmartAccount`](../how-to/create-smart-account/index.md#create-a-metamasksmartaccount)
 and a [Viem Bundler Client](https://viem.sh/account-abstraction/clients/bundler).
 
 After setting up your Bundler Client, you can extend its functionality with `erc7710BundlerActions` actions to support ERC-7710. Once extended, use [`sendUserOperationWithDelegation`](../reference/api/experimental-actions/bundler-client.md#senduseroperationwithdelegation) to redeem the permission.

delegation-toolkit/experimental/erc-7715-request-permissions.md

@@ -21,8 +21,8 @@ The MetaMask Delegation Toolkit provides the experimental actions for ERC-7715 t
 ## Request permissions
 
 To request permissions, extend your [Viem Wallet Client](https://viem.sh/docs/clients/wallet) with `erc7715ProviderActions` actions.
-You'll need a session account to request the permission, which can be either a Smart Account or an externally owned account (EOA).
-This example uses a Smart Account:
+You'll need a session account to request the permission, which can be either a MetaMask smart account or an externally owned account (EOA).
+This example uses a smart account:
 
 <Tabs>
 <TabItem value="example.ts">

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

@@ -1,12 +1,12 @@
 ---
-description: Upgrade an externally owned account (EOA) to a Smart Account
+description: Upgrade an externally owned account (EOA) to a smart account
 sidebar_position: 3
 sidebar_label: EIP-7702 quickstart
 ---
 
 # EIP-7702 quickstart
 
-This page demonstrates how to upgrade your externally owned account (EOA) to support MetaMask Smart Account 
+This page demonstrates how to upgrade your externally owned account (EOA) to support MetaMask Smart Accounts 
 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).
 
@@ -73,7 +73,7 @@ does not support JSON-RPC accounts.
 
 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.
+provides a lightweight and secure way to upgrade an EOA to a smart account.
 
 ```typescript
 import {
@@ -108,9 +108,9 @@ const hash = await walletClient.sendTransaction({
 });
 ```
 
-### 6. Create a MetaMask Smart Account
+### 6. Create a MetaMask smart account
 
-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

delegation-toolkit/get-started/install.md

@@ -9,7 +9,7 @@ import TabItem from "@theme/TabItem";
 
 # Install and set up the Delegation Toolkit
 
-This page provides instructions to install and set up the MetaMask Delegation Toolkit, enabling you to integrate [Smart Accounts](../concepts/smart-accounts.md) into your dapp.
+This page provides instructions to install and set up the MetaMask Delegation Toolkit, enabling you to integrate [MetaMask Smart Accounts](../concepts/smart-accounts.md) into your dapp.
 
 ## Prerequisites
 

delegation-toolkit/how-to/configure.md

@@ -6,7 +6,7 @@ sidebar_label: Configure the toolkit
 
 # Configure the Delegation Toolkit
 
-The MetaMask Delegation Toolkit enables you to easily integrate [Smart Accounts](../concepts/smart-accounts.md) into your dapp,
+The MetaMask Delegation Toolkit enables you to easily integrate [MetaMask Smart Accounts](../concepts/smart-accounts.md) into your dapp,
 enabling a more flexible, secure, and frictionless experience for your users.
 
 The toolkit is highly configurable, allowing you to tailor it to your project's specific needs. It includes support for custom signers, multiple signatory schemes, custom paymasters and bundlers, and more.

delegation-toolkit/how-to/create-delegation/index.md

@@ -28,7 +28,7 @@ Learn how to [restrict a delegation](./restrict-delegation.md) using caveat enfo
 
 - [Install and set up the Delegation Toolkit.](../../get-started/install.md)
 - [Configure the Delegation Toolkit.](../configure.md)
-- [Create a Smart Account.](../create-smart-account/index.md)
+- [Create a MetaMask smart account.](../create-smart-account/index.md)
 
 ## Create a root delegation
 
@@ -44,7 +44,7 @@ import { createDelegation } from "@metamask/delegation-toolkit";
 import { delegatorSmartAccount } from "./config.ts";
 
 // The address to which the delegation is granted. It can be an EOA address, or 
-// Smart Account address.
+// smart account address.
 const delegate = "0x2FcB88EC2359fA635566E66415D31dD381CF5585";
 
 const delegation = createDelegation({
@@ -298,7 +298,7 @@ import { createDelegation } from "@metamask/delegation-toolkit";
 import { delegatorSmartAccount } from "./config.ts";
 
 // The address to which the delegation is granted. It can be an EOA address, or 
-// Smart Account address.
+// smart account address.
 const delegate = "0x2FcB88EC2359fA635566E66415D31dD381CF5585";
 
 const delegation = createDelegation({

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

@@ -1,43 +1,43 @@
 ---
 sidebar_label: Configure accounts and signers
-description: Learn how to configure different types of delegator accounts and signers using Viem.
+description: Learn how to configure different types of smart accounts and signers using Viem.
 sidebar_position: 1
 ---
 
 import Tabs from "@theme/Tabs";
 import TabItem from "@theme/TabItem";
 
-# Configure Smart Accounts and signers
+# Configure MetaMask Smart Accounts and signers
 
-The MetaMask Delegation Toolkit supports different [Smart Account types](../../concepts/smart-accounts.md#smart-account-implementation-types),
+The MetaMask Delegation Toolkit supports different [MetaMask smart account types](../../concepts/smart-accounts.md#smart-account-implementation-types),
 each with its own configuration and support for different signing mechanisms.
 You can create flexible and secure delegator accounts tailored to your specific needs.
 
 ## Prerequisites
 
 - [Install and set up the Delegation Toolkit.](../../get-started/install.md)
 - [Configure the Delegation Toolkit.](../configure.md)
-- [Create a Smart Account.](index.md)
+- [Create a MetaMask smart account.](index.md)
 
-## Configure a Hybrid Smart Account
+## Configure a Hybrid smart account
 
-The [Hybrid Smart Account](../../concepts/smart-accounts.md#hybrid-smart-account) supports both an EOA "owner" and any number of P256 (passkey) signers.
+The [Hybrid smart account](../../concepts/smart-accounts.md#hybrid-smart-account) supports both an EOA "owner" and any number of P256 (passkey) signers.
 
-To configure a Hybrid Smart Account, provide the following parameters:
+To configure a Hybrid smart account, provide the following parameters:
 
 - `owner`: The owner's account address as a hex string.
   The owner can be the zero address, indicating that there is no owner configured.
 - `p256KeyIds`: An array of key identifiers for P256 signers as hex strings.
 - `p256XValues`: An array of public key x-values for P256 signers as `bigint`s.
 - `p256YValues`: An array of public key y-values for P256 signers as `bigint`s.
-- `signatory`: A signer that will sign on behalf of the Smart Account.
+- `signatory`: A signer that will sign on behalf of the smart account.
 
 :::note
 You can set all `p256` parameters to empty arrays to configure no WebAuthn signer.
 However, we recommend configuring at least one signer for account recoverability.
 :::
 
-For a Hybrid Smart Account, you can configure the following types of signatories:
+For a Hybrid smart account, you can configure the following types of signatories:
 
 ### Configure an account signatory
 
@@ -222,7 +222,7 @@ import {
 } from "viem/account-abstraction";
 
 export const credential = await createWebAuthnCredential({
-  name: "MetaMask Smart Account",
+  name: "MetaMask smart account",
 });
 
 export const webAuthnAccount = toWebAuthnAccount({ credential });
@@ -232,19 +232,19 @@ export const webAuthnAccount = toWebAuthnAccount({ credential });
 </Tabs>
 
 
-## Configure a Multisig Smart Account
+## Configure a Multisig smart account
 
-The [Multisig Smart Account](../../concepts/smart-accounts.md#multisig-smart-account) supports multiple EOA signers with a configurable threshold for execution.
+The [Multisig smart account](../../concepts/smart-accounts.md#multisig-smart-account) supports multiple EOA signers with a configurable threshold for execution.
 
-To configure a Multisig Smart Account, provide the following parameters:
+To configure a Multisig smart account, provide the following parameters:
 
 - `signers`: An array of EOA signer addresses as hex strings.
 - `threshold`: The number of signers required to execute a transaction, as a `bigint`.
-- `signatory`: A signer that will sign on behalf of the Smart Account.
+- `signatory`: A signer that will sign on behalf of the smart account.
 
 ### Configure signatories
 
-For a Multisig Smart Account, you can use a combination of account signatories and Wallet Client signatories.
+For a Multisig smart account, you can use a combination of account signatories and Wallet Client signatories.
 For example:
 
 <Tabs>
@@ -316,17 +316,17 @@ export const walletClient = createWalletClient({
 The number of signers in the signatories must be at least equal to the threshold for valid signature generation.
 :::
 
-## Configure a Stateless 7702 Smart Account
+## Configure a Stateless 7702 smart account
 
-The [Stateless 7702 Smart Account](../../concepts/smart-accounts.md#stateless-7702-smart-account) represents an EOA that has been upgraded to support Smart Account 
+The [Stateless 7702 smart account](../../concepts/smart-accounts.md#stateless-7702-smart-account) represents an EOA that has been upgraded to support MetaMask Smart Accounts 
 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/eip7702-quickstart.md) to learn how to upgrade.
 
-To configure a Stateless 7702 Smart Account, provide the following parameters:
+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.
+- `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 Stateless 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