doc, lib, src, test, tools: fix assorted typos

PR-URL: #29075
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>

Author: XhmikosR

doc/api/https.md

@@ -42,7 +42,7 @@ changes:
     is specified using an IP address, in which case the default is `''` (no
     extension).
 
-    See [`Session Resumption`][] for infomation about TLS session reuse.
+    See [`Session Resumption`][] for information about TLS session reuse.
 
 ## Class: https.Server
 <!-- YAML

lib/internal/timers.js

@@ -307,7 +307,7 @@ function insert(item, refed, start) {
   if (msecs < 0 || msecs === undefined)
     return;
 
-  // Truncate so that accuracy of sub-milisecond timers is not assumed.
+  // Truncate so that accuracy of sub-millisecond timers is not assumed.
   msecs = Math.trunc(msecs);
 
   item._idleStart = start;

src/node_process_object.cc

@@ -125,7 +125,7 @@ MaybeLocal<Object> CreateProcessObject(Environment* env) {
 #endif  // NODE_HAS_RELEASE_URLS
 
   // process._rawDebug: may be overwritten later in JS land, but should be
-  // availbale from the begining for debugging purposes
+  // available from the beginning for debugging purposes
   env->SetMethod(process, "_rawDebug", RawDebug);
 
   return scope.Escape(process);

test/fixtures/es-modules/loop.mjs

@@ -6,7 +6,7 @@ console.log(message, 5);
 while (t > 0) {
   if (t++ === 1000) {
     t = 0;
-    console.log(`Outputed message #${k++}`);
+    console.log(`Outputted message #${k++}`);
   }
 }
 process.exit(55);

test/parallel/test-timers-non-integer-delay.js

@@ -78,7 +78,7 @@ const interval = setInterval(common.mustCall(() => {
       `Non-integer delay ordering should be ${expected}, but got ${ordering}`
     );
 
-    // 2 should always be last of these delays due to ordering guarentees by
+    // 2 should always be last of these delays due to ordering guarantees by
     // the implementation.
   }), 2);
 }

test/parallel/test-timers-refresh.js

@@ -22,7 +22,7 @@ const { inspect } = require('util');
   }), 1);
   timer.unref();
 
-  // This relies on implicit timers handle sorting withing libuv.
+  // This relies on implicit timers handle sorting within libuv.
 
   setTimeout(common.mustCall(() => {
     strictEqual(called, false, 'unref()\'d timer returned before check');

test/parallel/test-tls-socket-close.js

@@ -13,7 +13,7 @@ const fixtures = require('../common/fixtures');
 // This test has a dependency on the order in which the TCP connection is made,
 // and TLS server handshake completes. It assumes those server side events occur
 // before the client side write callback, which is not guaranteed by the TLS
-// API. It usally passes with TLS1.3, but TLS1.3 didn't exist at the time the
+// API. It usually passes with TLS1.3, but TLS1.3 didn't exist at the time the
 // bug existed.
 //
 // Pin the test to TLS1.2, since the test shouldn't be changed in a way that

test/parallel/test-worker-cleanexit-with-js.js

@@ -6,7 +6,7 @@ const common = require('../common');
 // arbitrary execution points. By running a lot of
 // JS code in a tight loop, the expectation
 // is that those will be at various control flow points
-// preferrably in the JS land.
+// preferably in the JS land.
 
 const { Worker } = require('worker_threads');
 const code = 'setInterval(() => {' +

test/parallel/test-worker-cleanexit-with-moduleload.js

@@ -6,7 +6,7 @@ const common = require('../common');
 // arbitrary execution points. By using a number of
 // internal modules as load candidates, the expectation
 // is that those will be at various control flow points
-// preferrably in the C++ land.
+// preferably in the C++ land.
 
 const { Worker } = require('worker_threads');
 const modules = [ 'fs', 'assert', 'async_hooks', 'buffer', 'child_process',

tools/code_cache/cache_builder.cc

@@ -127,7 +127,7 @@ std::string CodeCacheBuilder::Generate(Local<Context> context) {
     // TODO(joyeecheung): we can only compile the modules that can be
     // required here because the parameters for other types of builtins
     // are still very flexible. We should look into auto-generating
-    // the paramters from the source somehow.
+    // the parameters from the source somehow.
     if (loader->CanBeRequired(id.c_str())) {
       NativeModuleLoader::Result result;
       USE(loader->CompileAsModule(context, id.c_str(), &result));