From 8c8b5ea1319594ddc3fb76452b71ee4b250db0b1 Mon Sep 17 00:00:00 2001 From: Cypher Pepe <125112044+cypherpepe@users.noreply.github.com> Date: Tue, 26 Nov 2024 23:32:55 +0300 Subject: [PATCH 1/4] typos trace_rpc_apis.md Signed-off-by: Cypher Pepe <125112044+cypherpepe@users.noreply.github.com> --- docs/trace_rpc_apis.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/trace_rpc_apis.md b/docs/trace_rpc_apis.md index 7f04d497a7b..0c26349c6bf 100644 --- a/docs/trace_rpc_apis.md +++ b/docs/trace_rpc_apis.md @@ -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. From 5ce7f91c55615b2af949ff908fcfda72b7553dae Mon Sep 17 00:00:00 2001 From: Cypher Pepe <125112044+cypherpepe@users.noreply.github.com> Date: Tue, 26 Nov 2024 23:39:16 +0300 Subject: [PATCH 2/4] typo README.md Signed-off-by: Cypher Pepe <125112044+cypherpepe@users.noreply.github.com> --- ethereum/evmtool/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ethereum/evmtool/README.md b/ethereum/evmtool/README.md index 50db1066f38..56776080636 100644 --- a/ethereum/evmtool/README.md +++ b/ethereum/evmtool/README.md @@ -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 From bf88f6eb95e5db79d704b2f9b09b001d803e9c9c Mon Sep 17 00:00:00 2001 From: Cypher Pepe <125112044+cypherpepe@users.noreply.github.com> Date: Tue, 26 Nov 2024 23:46:13 +0300 Subject: [PATCH 3/4] typo README.md Signed-off-by: Cypher Pepe <125112044+cypherpepe@users.noreply.github.com> --- testfuzz/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/testfuzz/README.md b/testfuzz/README.md index 8f436d70117..2e5d050e248 100644 --- a/testfuzz/README.md +++ b/testfuzz/README.md @@ -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: @@ -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. \ No newline at end of file +The `fuzzAll` target will fuzz all clients. From 11d16cb05462d1a20ba87a8326744ace6aeee08b Mon Sep 17 00:00:00 2001 From: Cypher Pepe <125112044+cypherpepe@users.noreply.github.com> Date: Tue, 26 Nov 2024 23:52:19 +0300 Subject: [PATCH 4/4] typos MAINTAINERS.md Signed-off-by: Cypher Pepe <125112044+cypherpepe@users.noreply.github.com> --- MAINTAINERS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS.md b/MAINTAINERS.md index 6c17df88239..6a9bd33c380 100644 --- a/MAINTAINERS.md +++ b/MAINTAINERS.md @@ -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: @@ -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