From af483b6e4e286aa16cfe18fde429006c83d852ed Mon Sep 17 00:00:00 2001 From: howy <132113803+howydev@users.noreply.github.com> Date: Fri, 30 Aug 2024 17:22:48 -0400 Subject: [PATCH] Update standard/ERCs/erc-6900.md Co-authored-by: Zer0dot --- 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 bf3ab8be..afd26927 100644 --- a/standard/ERCs/erc-6900.md +++ b/standard/ERCs/erc-6900.md @@ -563,7 +563,7 @@ For all non-view functions within `IModularAccount` except `executeWithAuthoriza If the caller is not the EntryPoint or the account, the account MUST check access control for direct call validation. -Prior to running the target function, the modular account MUST run all pre execution hooks that apply for the current function call. Pre execution hooks apply if they have been installed to the currently running function selector, or if they are installed as a execution hook to the validation function that was used for the current execution. Pre execution hooks MUST run validation-associated hooks first, then selector-associated hooks second. +Prior to running the target function, the modular account MUST run all pre execution hooks that apply for the current function call. Pre execution hooks apply if they have been installed to the currently running function selector, or if they are installed as an execution hook to the validation function that was used for the current execution. Pre execution hooks MUST run validation-associated hooks first, then selector-associated hooks second. Next, the modular account MUST run the target function, either an account native function or a module-defined execution function.