fixup! fixup! doc: add more context about benchmark tests and envs used

Author: brunocroh

doc/contributing/writing-and-running-benchmarks.md

@@ -742,26 +742,24 @@ only a single configuration per benchmark executes.
 While this dramatically reduces execution time, it provides limited coverage
 and cannot guarantee that all configurations function properly.
 
-This PR introduce the usage of new env `NODE_RUN_ALL_BENCH_TESTS`, that can be set to all becnhmark configs run in tests to try coverage more scenarios when benchmarks can fails.
-this PR as well document how to write benchmark tests, and give more details about the envs
+This PR introduces the usage of a new environment variable `NODE_RUN_ALL_BENCH_TESTS`, which can be set to run all benchmark configurations in tests to cover more scenarios where benchmarks might fail.
+This PR also documents how to write benchmark tests and provides more details about the environment variables:
 
-- NODE_RUN_ALL_BENCH_TESTS
-- NODEJS_BENCHMARK_ZERO_ALLOWED
+* NODE_RUN_ALL_BENCH_TESTS
+* NODEJS_BENCHMARK_ZERO_ALLOWED
 
-Some benchmarks tests was introduced as well for benchmark groups
+Benchmark tests were added for the following groups:
 
-- abort_controller
-- error
-- https
-- perf_hooks
-- permission
-- sqlite
-- test_runner
-- websocket
+* abort_controller
+* error
+* https
+* perf_hooks
+* permission
+* sqlite
+* test_runner
+* websocket
 
-and some incosistent test files was renamed
+Additionally, some inconsistent test files were renamed:
 
 test/benchmark/test-benchmark-async-hooks.js → test/benchmark/test-benchmark-async_hooks.js
 test/benchmark/test-benchmark-child-process.js → test/benchmark/test-benchmark-child_process.js
-
-