Skip to content

chore: fix some typos in comments #5913

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

Closed
dockercui wants to merge 1 commit into from
Closed

chore: fix some typos in comments #5913

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 noir-projects/noir-contracts/contracts/auth_contract/src/main.nr
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ contract Auth {
assert(!admin.is_zero(), "invalid admin");
storage.admin.initialize(admin);
// Note that we don't initialize authorized with any value: because storage defaults to 0 it'll have a 'post'
// value of 0 and block of change 0, meaning it is effectively autoinitialized at the zero adddress.
// value of 0 and block of change 0, meaning it is effectively autoinitialized at the zero address.
}

#[aztec(public)]
Expand Down
2 changes: 1 addition & 1 deletion noir/noir-repo/tooling/nargo/src/ops/execute.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -106,7 +106,7 @@ impl<'a, B: BlackBoxFunctionSolver, F: ForeignCallExecutor> ProgramExecutor<'a,
return Err(NargoError::ExecutionError(match call_stack {
Some(call_stack) => {
// First check whether we have a runtime assertion message that should be resolved on an ACVM failure
// If we do not have a runtime assertion message, we check wether the error is a brillig error with a user-defined message,
// If we do not have a runtime assertion message, we check weather the error is a brillig error with a user-defined message,
// and finally we should check whether the circuit has any hardcoded messages associated with a specific `OpcodeLocation`.
// Otherwise return the provided opcode resolution error.
if let Some(assert_message) = assert_message {
Expand Down