docs: refine terminology and clarify procedural details (#13)

hub/columns/storage.tex

@@ -23,7 +23,7 @@
 		$\stoNextValueIsOrig$:
 		binary columns whose purpose is to streamline the computation of gas costs of \inst{SSTORE} instructions.
 \end{enumerate}
-The desired interpretation is straightfoward:
+The desired interpretation is straightforward:
 \[
 	\left\{ \begin{array}{lclclcl}
 		\stoOrigValueIsZero & \!\!\! = \!\!\! & 1 & \iff & \stoOrigValue & \!\!\! = \!\!\! & 0           \\

hub/consistencies/context/constraints.tex

@@ -79,7 +79,7 @@
 Observe that whenever the \zkEvm{} spawns a new execution context it does so with
 $\cn \equiv \hubStamp$\footnote{And
 this may only happen in the \textbf{initialization phase} of a transaction,
-when transfering transaction call data to a designated, fresh new execution context's \textsc{ram};
+when transferring transaction call data to a designated, fresh new execution context's \textsc{ram};
 see section~(\ref{hub: initialization phase: transaction call data copy}) for details.} or 
 $\cn \equiv 1 + \hubStamp$ where moreover
 $\hubStamp > 0$.

log_info/lookups/log_info_into_rlp_log.tex

@@ -1,4 +1,4 @@
-We describe the lookup transfering \emph{verticalized} data from the current module to the \rlpTxnRcptMod{} module.
+We describe the lookup transferring \emph{verticalized} data from the current module to the \rlpTxnRcptMod{} module.
 \begin{description}
 	\item[\underline{Selector:}] none.
 	\item[\underline{Source columns:}] from the \logInfoMod{} module:

notes/stipend.md

@@ -108,7 +108,7 @@ There must be the following:
 
 
 For COUNTER there are two options:
-- either have a very specific behaviour, e.g. COUNTER: 0, 1, 2, 3 or 0, 1, 2 or just 0, 1 depending on CALL transfering value, CALL not transfering value or CREATE
+- either have a very specific behaviour, e.g. COUNTER: 0, 1, 2, 3 or 0, 1, 2 or just 0, 1 depending on CALL transferring value, CALL not transferring value or CREATE
 - either have generic behaviour: COUNTER: 0, 1, 2, 3 _always_ <--- likely the best option
 
 Have some "counter-constancy" constraints on columns imported from the HUB:

pkg/env.sty

@@ -433,8 +433,8 @@
 \newcommand{\firstRowOfNewContext}         [2]  {\texttt{firstRowOfNewContext}       _{#1}  \big[\, #2 \,\big]}
 \newcommand{\precompileScenarioRow}        [2]  {\texttt{precompileScenarioRow}      _{#1}  \big[\, #2 \,\big]}
 %
-\newcommand{\unsuccessfulCall}                {\texttt{unsucessfulCall}}
-\newcommand{\successfulCall}                  {\texttt{sucessfulCall}}
+\newcommand{\unsuccessfulCall}                {\texttt{unsuccessfulCall}}
+\newcommand{\successfulCall}                  {\texttt{successfulCall}}
 %
 \newcommand{\CONTEXTMAYCHANGE} {\col{CONTEXT\_MAY\_CHANGE}}
 \newcommand{\cmc} {\col{CMC}\flag}

txn_data/lookups.md

@@ -266,7 +266,7 @@ Simple bilateral lookup to prove the prewarming of all [addresses, storage key]
 The TX_RLP and TX_DATA modules must be augmented slightly:
 - TX_DATA:
   - we need redundancy to reduce the number of lookups
-  - we need a REQURIES_EVM_EXECUTION binary column (which is justified in the hub)
+  - we need a REQUIRES_EVM_EXECUTION binary column (which is justified in the hub)
   - we should do the gas price computations (for Type 2 transactions) here
 - TX_RLP:
   - we require a transaction-constant binary column REQUIRES_EVM_EXECUTION which is justified in TX_DATA