cleanup: remove bolding from MUSTs

erc6900 · Sep 5, 2024 · eb1b63d · eb1b63d
1 parent 57e4656
commit eb1b63d
Showing 1 changed file with 5 additions and 5 deletions.
diff --git a/standard/ERCs/erc-6900.md b/standard/ERCs/erc-6900.md
@@ -516,11 +516,11 @@ 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.
-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`. 
+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.
+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`. 
 
 #### Hook Execution Order