Merge 376a6d7 into 2a6fb92

Author: wgyt

EIPS/eip-615.md

@@ -35,7 +35,7 @@ And absent dynamic jumps, and with proper subroutines the EVM is a better target
 
 The result is that all of the following validations and optimizations can be done at deployment time with near-linear `(n log n)` time complexity.
 * The absence of most exceptional halting states can be validated.
-* The maximum use of resources can be sometimes be calculated.
+* The maximum use of resources can sometimes be calculated.
 * Bytecode can be compiled to machine code in near-linear time.
 * Compilation can more effectively optimize use of smaller registers.
 * Compilation can more effectively optimize injection of gas metering.
@@ -155,7 +155,7 @@ Jumps to and returns from subroutines are described here in terms of
 We will adopt the following conventions to describe the machine state:
 * The _program counter_ `PC` is (as usual) the byte offset of the currently executing instruction.
 * The _stack pointer_ `SP` corresponds to the [Yellow Paper](https://ethereum.github.io/yellowpaper/paper.pdf)'s substate `s` of the machine state.
-  * `SP[0]` is where a new item is can be pushed on the stack.
+  * `SP[0]` is where a new item can be pushed on the stack.
   * `SP[1]` is the first item on the stack, which can be popped off the stack.
   * The stack grows towards lower addresses.
 * The _frame pointer_ `FP` is set to `SP + n_args` at entry to the currently executing subroutine.

EIPS/eip-7749.md

@@ -75,7 +75,7 @@ No backward compatibility issues found.
 
 - Signer Address (`0x6aFbBC5e6AFcB251371711a6551E60ead2779Dc0`): This is the address of the account that will be used to sign the constructed message. We have access to the private key of this address, which allows us to generate the signature securely.
 
-- Verifier Address (`0x345B918b9E06fAa7B0e56bd71Ba418F31F47FED4`): This address represents the address verfying the signature, could be an EOA or a smart contract. For example, it could be a contract that performs specific actions based on the validity of the signature. By including this address in the data to be signed, we ensure that the signature cannot be reused by malicious actors for unintended purposes.
+- Verifier Address (`0x345B918b9E06fAa7B0e56bd71Ba418F31F47FED4`): This address represents the address verifying the signature, could be an EOA or a smart contract. For example, it could be a contract that performs specific actions based on the validity of the signature. By including this address in the data to be signed, we ensure that the signature cannot be reused by malicious actors for unintended purposes.
 
 - Data to Sign (`0x59616d656e`): This is the hex-encoded string representing the actual content to be signed. In this example, it is the hex encoding for the ASCII string "Yamen". The data, combined with the verifier address, is hashed and signed to generate a unique signature that cannot be used for any other purpose.