From 7795b80331bc386a1f3380be907225a4da2e0c3a Mon Sep 17 00:00:00 2001 From: antews Date: Mon, 9 Dec 2024 16:06:26 +0100 Subject: [PATCH] fix: correct multiple typos around files (#25) --- hub/generalities/gas/constraints.tex | 4 ++-- .../ramToRamSansPadding/micro_instruction_writing.tex | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/hub/generalities/gas/constraints.tex b/hub/generalities/gas/constraints.tex index 83f45a0..0184858 100644 --- a/hub/generalities/gas/constraints.tex +++ b/hub/generalities/gas/constraints.tex @@ -43,7 +43,7 @@ The gas cost of an instruction matters to the present arithmetization \emph{if and only if} it is either unexceptional or raises an \oogxSH{} in the arithmetization. For exceptional instructions the \zkEvm{} sets the next gas value to $0$. -For (most) unexceptional instructions the next value of gas is (unsurprisingly) obtained by substracting the gas cost from the currently avaialble gas. +For (most) unexceptional instructions the next value of gas is (unsurprisingly) obtained by subtracting the gas cost from the currently available gas. However, pricing is special for \inst{CALL}-type and \inst{CREATE}-type instructions and we defer to the relevant instruction handling section. \begin{enumerate}[resume] \item \If @@ -70,6 +70,6 @@ \end{enumerate} Some details: (\ref{hub: generalities: gas: resuming execution gas constraint}) asserts that when an execution context reaches its conclusion (as witnessed by $\cn\new_{i} = \caller_{i}$) the $\gasNext$ column on that row must contain the left over gas in the present context. -We are unable to settle the ``call gas'' or ``create gas'' provided to a child context spawned through a \inst{CREATE}-type or \inst{CALL}-type instruction at this level of generatlity, whence the \relevantValue{} in constraint~(\ref{hub: generalities: gas: spawning new context}). It is a complex question and will be settled when we deal with the processing of those instruction families. +We are unable to settle the ``call gas'' or ``create gas'' provided to a child context spawned through a \inst{CREATE}-type or \inst{CALL}-type instruction at this level of generality, whence the \relevantValue{} in constraint~(\ref{hub: generalities: gas: spawning new context}). It is a complex question and will be settled when we deal with the processing of those instruction families. \issue{Constraint~(\ref{hub: generalities: gas: could blow up}) could blow up if we don't handle precompiles, pure transfers and deployments with empty code correctly.} diff --git a/mmu/instructions/ramToRamSansPadding/micro_instruction_writing.tex b/mmu/instructions/ramToRamSansPadding/micro_instruction_writing.tex index b75bd1d..8314e5c 100644 --- a/mmu/instructions/ramToRamSansPadding/micro_instruction_writing.tex +++ b/mmu/instructions/ramToRamSansPadding/micro_instruction_writing.tex @@ -1,5 +1,5 @@ \begin{center} - \boxed{ \text{The constriants presented below assumes that } \mmuInstFlagRamToRamSansPadding _{i} = 1. } + \boxed{ \text{The constraints presented below assumes that } \mmuInstFlagRamToRamSansPadding _{i} = 1. } \end{center} \begin{description} \item[\underline{Progression:}]