doc: fix typos in n-api, tls and worker_threads

PR-URL: #34419
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>

Author: jucke

doc/api/n-api.md

@@ -127,7 +127,7 @@ the native addon will also need to have a C/C++ toolchain installed.
 
 For Linux developers, the necessary C/C++ toolchain packages are readily
 available. [GCC][] is widely used in the Node.js community to build and
-test across a variety of plarforms. For many developers, the [LLVM][]
+test across a variety of platforms. For many developers, the [LLVM][]
 compiler infrastructure is also a good choice.
 
 For Mac developers, [Xcode][] offers all the required compiler tools.

doc/api/tls.md

@@ -85,8 +85,8 @@ all sessions). Methods implementing this technique are called "ephemeral".
 Currently two methods are commonly used to achieve perfect forward secrecy (note
 the character "E" appended to the traditional abbreviations):
 
-* [DHE][]: An ephemeral version of the Diffie Hellman key-agreement protocol.
-* [ECDHE][]: An ephemeral version of the Elliptic Curve Diffie Hellman
+* [DHE][]: An ephemeral version of the Diffie-Hellman key-agreement protocol.
+* [ECDHE][]: An ephemeral version of the Elliptic Curve Diffie-Hellman
   key-agreement protocol.
 
 Ephemeral methods may have some performance drawbacks, because key generation
@@ -1566,7 +1566,7 @@ changes:
     client certificate.
   * `crl` {string|string[]|Buffer|Buffer[]} PEM formatted CRLs (Certificate
     Revocation Lists).
-  * `dhparam` {string|Buffer} Diffie Hellman parameters, required for
+  * `dhparam` {string|Buffer} Diffie-Hellman parameters, required for
     [perfect forward secrecy][]. Use `openssl dhparam` to create the parameters.
     The key length must be greater than or equal to 1024 bits or else an error
     will be thrown. Although 1024 bits is permissible, use 2048 bits or larger

doc/api/worker_threads.md

@@ -110,7 +110,7 @@ const { port1 } = new MessageChannel();
 port1.postMessage(typedArray1, [ typedArray1.buffer ]);
 
 // The following line prints the contents of typedArray1 -- it still owns its
-// memory and has been cloned, not transfered. Without `markAsUntransferable()`,
+// memory and has been cloned, not transferred. Without `markAsUntransferable()`,
 // this would print an empty Uint8Array. typedArray2 is intact as well.
 console.log(typedArray1);
 console.log(typedArray2);