Update EIP-2315: Catch up to latest Yellow Paper (ethereum#5814)

* Catch up to latest Yellow Paper

* Remove yellow paper ref so that PR can be merged

Co-authored-by: Pandapip1 <[email protected]>

EIPS/eip-2315.md

@@ -96,7 +96,7 @@ _Execution_ is defined in the Yellow Paper as sequence of changes in the EVM sta
 5. Invalid jump destination
 6. Invalid instruction
 
-We would like to consider EVM code valid iff no execution of the program can lead to an exceptional halting state.  In practice, we must test at runtime for conditions 1, 2, and 3 — sufficient gas, sufficient stack, and modification of static state.  We don’t know how much gas there will be, we don’t know how deep a recursion may go, analysis of stack depth even for non-recursive programs is nontrivial, and we don't know whether a call will be static.  All of the remaining conditions MUST be validated statically, in time and space quasi-linear in the size of the code.
+We would like to consider EVM code valid iff no execution of the program can lead to an exceptional halting state.  In practice, we must test at runtime for conditions 1, 2, and 3 — sufficient gas and sufficient stack.  We don’t know how much gas there will be, we don’t know how deep a recursion may go, analysis of stack depth even for non-recursive programs is nontrivial, and we don't know whether a call will be static.  All of the remaining conditions MUST be validated statically, in time and space quasi-linear in the size of the code.
 
 #### Static Constraints on Valid Code