Skip to content

Commit a9193f8

Browse files
Update README.md
1 parent a4c0c98 commit a9193f8

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

testdata/benchmarks/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ make stop
2323
```
2424

2525
Collect proof input data for a range of blocks.
26-
As mentioned in the `ev-exec` documentation, using the `--start` and `--blocks` flags allows the user to chose a starting height and number of blocks to gather input data for.
26+
As mentioned in the `ev-exec` documentation, using the `--start` and `--blocks` flags allows the user to choose a starting height and number of blocks to gather input data for.
2727

2828
```shell
2929
cargo run -p ev-exec-script --bin data-gen --release -- --start 15 --blocks 5
@@ -40,7 +40,7 @@ RUST_LOG=info cargo run -p ev-exec-script --release -- --execute --height 15 --o
4040

4141
Using the outputs displayed on screen we can invoke the program for the subsequent blocks passing the `--trusted-height` and `--trusted-root` flags.
4242
Note, as we are chaining celestia blocks sequentially, we do not have a guarantee that each block will contain a `SignedData` blob for the EVM application.
43-
Thus, we explitcitly pass these flags to ensure empty blocks maintain a trusted height and state root moving forward.
43+
Thus, we explicitly pass these flags to ensure empty blocks maintain a trusted height and state root moving forward.
4444

4545
```shell
4646
RUST_LOG=info cargo run -p ev-exec-script --release -- --execute --height 16 --output-file block-15.json --trusted-height {N} --trusted-root {abcdef...}

0 commit comments

Comments
 (0)