edits and add image

Author: alexandratran

delegation-toolkit/assets/erc7715-request.png

@@ -30,11 +30,21 @@ The session account can be a smart account or an externally owned account (EOA).
 
 The MetaMask user that the session account requests permissions from must be upgraded to a [MetaMask smart account](smart-accounts.md).
 
-:::info ERC-7715 vs. delegations
+## ERC-7715 vs. delegations
+
 ERC-7715 expands on regular [delegations](delegation/index.md) by enabling permission sharing *via the MetaMask browser extension*.
+
+With a regular delegation, the dapp constructs the delegation and requests the user to sign it.
+Delegated permissions are not human-readable, so it is up to the dapp to provide context for the user.
 Regular delegations cannot be signed through the MetaMask extension, because if a dapp requests a delegation without constraints, the whole wallet can be exposed to the dapp.
-In contrast, ERC-7715 requires a [permission type](#permission-types) which displays a readable confirmation for the MetaMask user.
-:::
+
+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.
+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):
+
+<p align="center">
+<img src={require("../assets/erc7715-request.png").default} alt="ERC-7715 request" width="450px" class="appScreen" />
+</p>
 
 ## ERC-7715 permissions lifecycle
 
@@ -44,18 +54,9 @@ The ERC-7715 permissions lifecycle is as follows:
   It can be a [smart account](smart-accounts.md) or an externally owned account (EOA).
 
 2. **Request permissions** - Request permissions from the user.
-  MetaMask supports multiple ERC-7715 [permission types](#permission-types).
-
-3. **Set up a Viem client** - Set up a Viem client (the client type depends on the session account type) to redeem permissions.
+  The Delegation Toolkit supports [ERC-20 token permissions](../guides/erc7715/use-permissions/erc20-token.md) and
+  [native token permissions](../guides/erc7715/use-permissions/native-token.md).
 
 4. **Redeem permissions** - Once the permission is granted, the session account redeems the permission.
 
 See [how to perform executions on a MetaMask user's behalf](../guides/erc7715/execute-on-metamask-user-behalf.md) to get started with the ERC-7715 lifecycle.
-
-## Permission types
-
-The Delegation Toolkit currently supports the following types of ERC-7715 permissions:
-
-- **Native token permissions** - Define how dapps can use users' native tokens.
-
-- **ERC-20 token permissions** - Define how dapps can use users' ERC-20 tokens.