Skip to content

Commit cb51d0b

Browse files
authored
chore: redo typo PR by withtimezone (#17942)
Thanks withtimezone for #17743. Our policy is to redo typo changes to dissuade metric farming. This is an automated script.
2 parents 959f0de + aac95a8 commit cb51d0b

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

boxes/bin.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -109,7 +109,7 @@ program
109109
.action(async (options) => {
110110
// this is some bad code, but it's def fun
111111
// I'm matching all keys started with project and
112-
// then using using modulo to say "if one is defined, two must be defined"
112+
// then using modulo to say "if one is defined, two must be defined"
113113
const optsKeys = Object.keys(options).filter((e) => /project*/g.test(e));
114114
if (optsKeys.length % 2) {
115115
throw Error("You must define both the project type and the project name");

docs/versioned_docs/version-v2.0.2/developers/docs/guides/smart_contracts/define_functions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ tags: [functions, smart-contracts]
55
description: Learn how to define functions in your Aztec smart contracts.
66
---
77

8-
There are several types of functions in Aztec contracts that correspond the the different execution environments in which they run. These include:
8+
There are several types of functions in Aztec contracts that correspond the different execution environments in which they run. These include:
99

1010
- private functions
1111
- public functions

yarn-project/BRANCHING.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ Each `rc` tag causes ci3.yml to run, and creates releases because it runs `boots
4545

4646
### master (deprecated)
4747

48-
`master` points at the the version of code which ran the "old" testnet. It should not be updated anymore.
48+
`master` points at the version of code which ran the "old" testnet. It should not be updated anymore.
4949

5050
Functionally, it is `v1`.
5151

0 commit comments

Comments
 (0)