Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Fix typos in documentation: local_state.md and machine.md #1672

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: Fix typos in documentation: local_state.md and machine.md #1672

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a73b9b0
docs: typo fix Update local_state.md
mdqst Dec 22, 2024
28d4c81
docs: typo fix Update machine.md
mdqst Dec 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion cairo/kakarot-ssj/docs/general/local_state.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ from using dicts in self-referring data structures, instead of having one state
per execution context that we could merge into the parent state if the context
exits successfully or discard if the context reverts, we have one global `State`
structs that achieves the same behavior by tracking transactional changes, which
refers to the changes made inside the current transaction as a whole, and a
refers to the changes made inside the current transaction as a whole, and
contextual changes, which refers to changes made inside the current execution
context.

Expand Down
2 changes: 1 addition & 1 deletion cairo/kakarot-ssj/docs/general/machine.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ The EVM is a stack-based computer responsible for the execution of EVM bytecode.
It has two context-bound data structures: the stack and the memory. The stack is
a 256bit-words based data structure used to store and retrieve intermediate
values during the execution of opcodes. The memory is a byte-addressable data
structure organized into 32-byte words used a volatile space to store data
structure organized into 32-byte words used volatile space to store data
during execution. Both the stack and the memory are initialized empty at the
start of a call context, and destroyed when a call context ends.

Expand Down
Loading