Correct post commands typos and spelling errors (#28)

hub/generalities/gas/_local.tex

@@ -1,2 +1,2 @@
-\def\locNonOogExceptions    {\col{non\_oog\_exeptions}}
+\def\locNonOogExceptions    {\col{non\_oog\_exceptions}}
 \def\locOogxOrUnexceptional {\col{oogx\_or\_unexceptional}}

hub/instruction_handling/call/precompiles/ecadd_ecmul_ecpairing/success.tex

@@ -231,7 +231,7 @@
 
 				\saNote{} Recall that the return data \textbf{o} of a successful call to the \inst{ECADD}, \inst{ECMUL}, \inst{ECPAIRING} precompile which successfully recovers an address is a $\redm{32}$ byte string $\textbf{o} \in \mathbb{B}_{32}$ is a string of composed of 12 (leading) zero bytes followed by 20 bytes making up the recovered Ethereum public address.
 
-				\saNote{} We remind the reader that \textsc{ram} segments (associated to a nonzero context number) are intialized as \textbf{empty}.
+				\saNote{} We remind the reader that \textsc{ram} segments (associated to a nonzero context number) are initialized as \textbf{empty}.
 				Since the case of \textbf{empty call data} yields the zero string in
 				$\mathbb{B}_{64}$ and
 				$\mathbb{B}_{32}$

hub/instruction_handling/call/precompiles/intro.tex

@@ -1,6 +1,6 @@
 The present section deals with precompiles from the point of view of the \hubMod{} module.
 For the purposes of the \hubMod{} ``dealing with precompiles'' means dealing with \textbf{pricing}, \textbf{control flow} and triggering certain \textsc{ram} instructions \textbf{extracting input data} and \textbf{writing output data} to the caller's \textsc{ram}.
-Concretely this \emph{may} involve any the following:
+Concretely this \emph{may} involve any of the following:
 \begin{enumerate}
 	\item extracting pricing parameters from \textsc{ram};
 	\item extracting input data from \textsc{ram} to detect either malformed / wellformed call data;
@@ -17,4 +17,4 @@
 The exogenous data modules in question, i.e. \shakiraMod{}, \ecDataMod{} and \blkMdxMod{}, may perform some preliminary data vetting before serving the requests to the relevant precompile circuits.
 
 \saNote{} Precompile processing \textbf{does not} mean that we provide a constraint system / circuit for these operations.
-This is not the perview of our arithmetization and is the responsability of a different component of the system. 
+This is not the purview of our arithmetization and is the responsibility of a different component of the system. 

hub/instruction_handling/halt.tex

@@ -236,7 +236,7 @@
 % 				\right.
 % 				\]
 % 				\saNote{} \inst{SELFDESTRUCT} raises the \trmFlag{}; the high part of the recipient address (i.e. $\accAddress\high_{i + 4}$) will be filled in by the \trmMod{} module. \ob{TODO: plookup into \trmMod{}}
-% 				\item[\underline{Row $n°(i + 5)$:}] the fourth account-row (again) peeks into the account was posed to be the recipient of the value tranfer of the \inst{SELFDESTRUCT} and restores it to its previous state:
+% 				\item[\underline{Row $n°(i + 5)$:}] the fourth account-row (again) peeks into the account was posed to be the recipient of the value transfer of the \inst{SELFDESTRUCT} and restores it to its previous state:
 % 				\[
 % 				\left\{
 % 				\begin{array}{lcl}