From 99a887f8a57cabf77b09ce6106c9c231ccbf24f0 Mon Sep 17 00:00:00 2001
From: howy <132113803+howydev@users.noreply.github.com>
Date: Thu, 5 Sep 2024 17:04:44 -0400
Subject: [PATCH] Update standard/ERCs/erc-6900.md

Co-authored-by: Adam Egyed <5456061+adamegyed@users.noreply.github.com>
---
 standard/ERCs/erc-6900.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/standard/ERCs/erc-6900.md b/standard/ERCs/erc-6900.md
index f5eed8c9..9cfa74ef 100644
--- a/standard/ERCs/erc-6900.md
+++ b/standard/ERCs/erc-6900.md
@@ -517,7 +517,7 @@ During execution uninstallation, the account MUST correctly clear flags and othe
 #### Execution Hooks Data Format
 
 For accounts that implement execution hooks, accounts **MUST** conform to these execution hook formats:
-1. For `executeUserOp` calls, for execution hooks associated with a validator, accounts **MUST** send the full `msg.data`, including the `executeUserOp` selector.
+1. For `executeUserOp` calls, for execution hooks associated with a validation function, accounts **MUST** send the full `msg.data`, including the `executeUserOp` selector.
 2. For `executeUserOp` calls, for execution hooks associated with a selector, accounts **MUST** send `PackedUserOperation.callData` for `executeUserOp` calls, excluding `executeUserOp.selector` and the rest of the `PackedUserOperation`.
 3. For `executeWithAuthorization` calls, for all execution hooks, accounts **MUST** send the inner `data`.
 4. For all other calls, for execution hooks associated with a selector, accounts **MUST** send over `msg.data`.