edits

Author: alexandratran

delegation-toolkit/concepts/erc7715.md

@@ -23,8 +23,8 @@ Dapps can use this method to request a wallet to grant the dapp permission to ex
 `wallet_grantPermissions` requires a `signer` parameter, which identifies the entity requesting or managing the permission.
 Common signer implementations include wallet signers, single key and multisig signers, and account signers.
 
-The Delegation Toolkit's implementation uses an account signer.
-A session account is created and used for the single purpose of requesting and redeeming ERC-7715 permissions, and does not contain tokens.
+The Delegation Toolkit supports multiple types of signers, but [an account signer is used in this documentation's examples](../guides/erc7715/execute-on-metamask-users-behalf.md) as a common implementation.
+With an account signer, a session account is created and used for the single purpose of requesting and redeeming ERC-7715 permissions, and does not contain tokens.
 The session account can be granted with permissions and redeem them as specified in [ERC-7710](https://eips.ethereum.org/EIPS/eip-7710).
 The session account can be a smart account or an externally owned account (EOA).
 
@@ -40,6 +40,8 @@ Regular delegations cannot be signed through the MetaMask extension, because if
 
 In contrast, ERC-7715 enables dapps (and AI agents) to request permissions from a user directly via the MetaMask extension.
 ERC-7715 requires a permission configuration which displays a human-readable confirmation for the MetaMask user.
+The user can modify the permission parameters if the request is configured to allow adjustments.
+
 For example, the following ERC-7715 permission request displays a rich UI including the start time, amount, and period duration for an [ERC-20 token periodic transfer](../guides/erc7715/use-permissions/erc20-token.md#erc-20-periodic-permission):
 
 <p align="center">