Update ERC-7579: fix typo

Merged by EIP-Bot.

ERCS/erc-7579.md

@@ -93,7 +93,7 @@ function executeUserOp(PackedUserOperation calldata userOp, bytes32 userOpHash)
 
 The execution mode is a `bytes32` value that is structured as follows:
 
-- callType (1 byte): `0x00` for a single `call`, `0x01` for a batch `call` and `0xff` for `delegatecall`
+- callType (1 byte): `0x00` for a single `call`, `0x01` for a batch `call`, `0xfe` for `staticcall` and `0xff` for `delegatecall`
 - execType (1 byte): `0x00` for executions that revert on failure, `0x01` for executions that do not revert on failure but implement some form of error handling
 - unused (4 bytes): this range is reserved for future standardization
 - modeSelector (4 bytes): an additional mode selector that can be used to create further execution modes
@@ -105,7 +105,7 @@ Here is a visual representation of the execution mode:
 | -------- | -------- | ------- | ------------ | ----------- |
 | 1 byte   | 1 byte   | 4 bytes | 4 bytes      | 22 bytes    |
 
-Accounts are NOT REQUIRED to implement all execution modes. The account MUST declare what modes are supported in `supportsAccountMode` (see below) and if a mode is requested that is not supported by the account, the account MUST revert.
+Accounts are NOT REQUIRED to implement all execution modes. The account MUST declare what modes are supported in `supportsExecutionMode` (see below) and if a mode is requested that is not supported by the account, the account MUST revert.
 
 The account MUST encode the execution data the following ways: