src: fix some typo errors and rename some variables

Signed-off-by: Archkon <180910180+Archkon@users.noreply.github.com>

Author: Archkon

doc/api/stream.md

@@ -2001,7 +2001,7 @@ If the loop terminates with a `break`, `return`, or a `throw`, the stream will
 be destroyed. In other terms, iterating over a stream will consume the stream
 fully. The stream will be read in chunks of size equal to the `highWaterMark`
 option. In the code example above, data will be in a single chunk if the file
-has less then 64 KiB of data because no `highWaterMark` option is provided to
+has less than 64 KiB of data because no `highWaterMark` option is provided to
 [`fs.createReadStream()`][].
 
 ##### `readable[Symbol.for('Stream.toAsyncStreamable')]()`

doc/api/vm.md

@@ -2346,7 +2346,7 @@ console.log('OK');
 ```
 
 **Note:** Strictly speaking, in this mode, `node:vm` departs from the letter of
-the ECMAScript specification for [enqueing jobs][], by allowing asynchronous
+the ECMAScript specification for [enqueuing jobs][], by allowing asynchronous
 tasks from different contexts to run in a different order than they were
 enqueued.
 
@@ -2588,7 +2588,7 @@ const { Script, SyntheticModule } = require('node:vm');
 [`vm.runInContext()`]: #vmrunincontextcode-contextifiedobject-options
 [`vm.runInThisContext()`]: #vmruninthiscontextcode-options
 [contextified]: #what-does-it-mean-to-contextify-an-object
-[enqueing jobs]: https://tc39.es/ecma262/#sec-hostenqueuepromisejob
+[enqueuing jobs]: https://tc39.es/ecma262/#sec-hostenqueuepromisejob
 [global object]: https://tc39.es/ecma262/#sec-global-object
 [indirect `eval()` call]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/eval#direct_and_indirect_eval
 [origin]: https://developer.mozilla.org/en-US/docs/Glossary/Origin

test/addons/stringbytes-external-exceed-max/binding.cc

@@ -5,7 +5,7 @@
 #ifdef _AIX
 // AIX allows over-allocation, and will SIGKILL when the allocated pages are
 // used if there is not enough VM. Check for available space until
-// out-of-memory.  Don't allow more then some (large) proportion of it to be
+// out-of-memory.  Don't allow more than some (large) proportion of it to be
 // used for the test strings, so Node & V8 have some space for allocations.
 #include <signal.h>
 #include <sys/vminfo.h>

test/es-module/test-esm-nowarn-exports.mjs

@@ -5,7 +5,7 @@ import { execPath } from 'node:process';
 import { describe, it } from 'node:test';
 
 
-describe('ESM: experiemental warning for import.meta.resolve', { concurrency: !process.env.TEST_PARALLEL }, () => {
+describe('ESM: experimental warning for import.meta.resolve', { concurrency: !process.env.TEST_PARALLEL }, () => {
   it('should not warn when caught', async () => {
     const { code, signal, stderr } = await spawnPromisified(execPath, [
       '--experimental-import-meta-resolve',

test/js-native-api/test_string/test_string.c

@@ -20,7 +20,7 @@ static napi_status validate_and_retrieve_single_string_arg(
 
   NODE_API_ASSERT_STATUS(env,
                          valuetype == napi_string,
-                         "Wrong type of argment. Expects a string.");
+                         "Wrong type of argument. Expects a string.");
 
   return napi_ok;
 }

test/known_issues/test-fs-cp-filter.js

@@ -1,6 +1,6 @@
 'use strict';
 
-// This test will fail because the the implementation does not properly
+// This test will fail because the implementation does not properly
 // handle the case when the `src` or `dest` is a Buffer and the `filter`
 // function is utilized when recursively copying directories.
 // Refs: https://github.com/nodejs/node/issues/58634

test/known_issues/test-fs-readdir-promise-recursive-with-buffer.js

@@ -1,6 +1,6 @@
 'use strict';
 
-// This test will fail because the the implementation does not properly
+// This test will fail because the implementation does not properly
 // handle the case when the path is a Buffer and the function is called
 // in recursive mode.
 

test/known_issues/test-fs-readdir-recursive-with-buffer.js

@@ -1,6 +1,6 @@
 'use strict';
 
-// This test will fail because the the implementation does not properly
+// This test will fail because the implementation does not properly
 // handle the case when the path is a Buffer and the function is called
 // in recursive mode.
 

test/known_issues/test-fs-readdir-sync-recursive-with-buffer.js

@@ -1,6 +1,6 @@
 'use strict';
 
-// This test will fail because the the implementation does not properly
+// This test will fail because the implementation does not properly
 // handle the case when the path is a Buffer and the function is called
 // in recursive mode.
 

test/parallel/test-abortcontroller.js

@@ -13,7 +13,7 @@ const {
 
 const { setTimeout: sleep } = require('timers/promises');
 
-// All of the the tests in this file depend on public-facing Node.js APIs.
+// All of the tests in this file depend on public-facing Node.js APIs.
 // For tests that depend on Node.js internal APIs, please add them to
 // test-abortcontroller-internal.js instead.
 
@@ -93,7 +93,7 @@ test('AbortSignal.abort() creates an already aborted signal', () => {
   assert.ok(signal.aborted);
 });
 
-test('AbortController properties and methods valiate the receiver', () => {
+test('AbortController properties and methods validate the receiver', () => {
   const acSignalGet = Object.getOwnPropertyDescriptor(
     AbortController.prototype,
     'signal'