Update EIP-7620: Fix failed copy-paste (ethereum#9655)

Author: pdobacz

EIPS/eip-7620.md

@@ -48,15 +48,15 @@ We introduce two new instructions on the same block number [EIP-3540](./eip-3540
 1. `EOFCREATE` (`0xec`)
 2. `RETURNCODE` (`0xee`)
 
+If the code is legacy bytecode, any of these instructions result in an *exceptional halt*. (*Note: This means no change to behaviour.*)
+
 ### Execution Semantics
 
 - The instructions `CREATE`, `CREATE2` are made obsolete and rejected by validation in EOF contracts. They are only available in legacy contracts.
 - If instructions `CREATE` and `CREATE2` have EOF code as initcode (starting with `EF00` magic)
     - deployment fails (returns 0 on the stack)
     - caller's nonce is not updated and gas for initcode execution is not consumed
 
-If the code is legacy bytecode, any of these instructions result in an *exceptional halt*. (*Note: This means no change to behaviour.*)
-
 #### Overview of the new contract creation flow
 
 In EOF EVM, new bytecode is introduced to the state by means of `InitcodeTransaction` delivering an EOF container (`initcontainer`). Such a container may include arbitrarily deeply nesting subcontainers. The `initcontainer` and its subcontainers are recursively validated according to all the validation rules applicable for the EOF version in question. Next, the 0th code section of the `initcontainer` is executed and may eventually call a `RETURNCODE` instruction, which will refer to a subcontainer to be finally deployed to an address.