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.

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

Correct typos across multiple documentation files for clarity #7939

Closed
wants to merge 4 commits into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions MAINTAINERS.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@

## Becoming a Maintainer

Besu welcomes community contribution.
Besu welcomes the community contribution.
Each community member may progress to become a maintainer.

How to become a maintainer:
Expand All @@ -73,7 +73,7 @@ How to become a maintainer:

The requirement to be able to be proposed as a maintainer is:

- 5 significant changes on code have been authored in this repos by the proposed maintainer and accepted (merged PRs).
- 5 significant changes on code have been authored in this repository by the proposed maintainer and accepted (merged PRs).

### Maintainers approval process

Expand Down
4 changes: 2 additions & 2 deletions docs/trace_rpc_apis.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,10 +20,10 @@ In the `vmTrace` `op.ex.mem` fields Besu only reports actual data returned
from a `RETURN` opcode. Other implementations return the contents of the
reserved output space for the call operations. Note two major differences:

1. Besu reports `null` when a call operation ends because of a `STOP`, `HALT`,
1. Besu reports `null` when a call operation ends because of a `STOP`, `HALT`,
`REVERT`, running out of instructions, or any exceptional halts.
2. When a `RETURN` operation returns data of a different length than the space
reserved by the call only the data passed to the `RETURN` operation is
reserved by the call, only the data passed to the `RETURN` operation is
reported. Other implementations will include pre-existing memory data or
trim the returned data.

Expand Down
2 changes: 1 addition & 1 deletion ethereum/evmtool/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ Using EVM Tool in execution-specification-tests

Current as of 26 Jun 2024.

MacOS users will typically encounter two problems,one relating to the
MacOS users will typically encounter two problems, one relating to the
version of Python used and one relating to zsh.

Homebrew will only install the most recent version of Python
Expand Down
4 changes: 2 additions & 2 deletions testfuzz/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ BesuFuzz is where all the besu guided fuzzing tools live.

Performs differential fuzzing between Ethereum clients based on
the [txparse eofparse](https://github.com/holiman/txparse/blob/main/README.md#eof-parser-eofparse)
format. Note that only the inital `OK` and `err` values are used to determine if
format. Note that only the initial `OK` and `err` values are used to determine if
there is a difference.

### Prototypical CLI Usage:
Expand All @@ -26,4 +26,4 @@ BesuFuzz eof-container \

There are pre-written Gradle targets for `fuzzEthereumJS`, `fuzzEvmone`,
`fuzzGeth`, `fuzzNethermind`, and `fuzzReth`. Besu is always a fuzzing target.
The `fuzzAll` target will fuzz all clients.
The `fuzzAll` target will fuzz all clients.