fixes/clarifications

EIPS/eip-6690.md

@@ -26,7 +26,7 @@ Benefits of the changes proposed in this EIP:
 
 #### Overview
 
-During contract execution, a contract calls a setup instruction `SETUPX`, sourcing a modulus from a specified memory offset/size and computing several parameters used to speed up modular multiplication (referred to as "Montgomery" parameters).  A zeroed memory space is allocated separate from EVM memory.
+During contract execution, a contract calls a setup instruction `SETUPX`, sourcing a modulus from a specified memory offset/size and computing several parameters used to speed up modular multiplication (referred to as "Montgomery" parameters).  A zeroed memory space (whose size is a stack parameter passed to `SETUPX`) is allocated separate from EVM memory.
 
 The modulus, computed parameters and memory space are associated with the current call frame state and referred to as the active modulus state.  If `SETUPX` is called again to switch to a different modulus, the memory space and Montgomery parameters of the previous active modulus state remain allocated (the memory spaces of active/previously-active modulus state are separate).
 
@@ -68,7 +68,6 @@ An arithmetic operation is performed on inputs at index `x`/`y` placing the resu
 | `cost_evm_memory_expansion` | `func(new_size_evm_words: int) -> int` | EVM memory expansion cost function, modified according to this EIP |
 | `evm_stack` | object | Allows access to the stack via `pop()` and `peek(n)` which return `int` stack elements |
 | `contract_code` | `bytes` | code of the currently-executing contract |
-| `setup_sections` | `dict` | map of `mod_id` (`int`) to a setup section object (field names are from setup section spec. `int` values) |
 | `pc` | `int` | EVM program counter |
 
 ```