doc: fix typos
PR-URL: https://github.com/nodejs/node/pull/39049 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Khaidi Chu <i@2333.moe> Reviewed-By: Zijian Liu <lxxyxzj@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
This commit is contained in:
parent
0af0d1c30d
commit
5b5a9eb5fd
@ -3863,7 +3863,7 @@ The supplied `callback` function is called with two arguments: `err` and
|
||||
`derivedKey`. If an errors occurs while deriving the key, `err` will be set;
|
||||
otherwise `err` will be `null`. The successfully generated `derivedKey` will
|
||||
be passed to the callback as an {ArrayBuffer}. An error will be thrown if any
|
||||
of the input aguments specify invalid values or types.
|
||||
of the input arguments specify invalid values or types.
|
||||
|
||||
```mjs
|
||||
const {
|
||||
@ -3911,7 +3911,7 @@ given `key`, `salt` and `info` are used with the `digest` to derive a key of
|
||||
|
||||
The successfully generated `derivedKey` will be returned as an {ArrayBuffer}.
|
||||
|
||||
An error will be thrown if any of the input aguments specify invalid values or
|
||||
An error will be thrown if any of the input arguments specify invalid values or
|
||||
types, or if the derived key cannot be generated.
|
||||
|
||||
```mjs
|
||||
|
@ -2502,7 +2502,7 @@ is flushed.
|
||||
Use [`response.writableFinished`][] or [`response.writableEnded`][]
|
||||
accordingly instead to avoid the ambiguity.
|
||||
|
||||
To maintain existing behaviour `response.finished` should be replaced with
|
||||
To maintain existing behavior `response.finished` should be replaced with
|
||||
`response.writableEnded`.
|
||||
|
||||
### DEP0137: Closing fs.FileHandle on garbage collection
|
||||
|
@ -3843,7 +3843,7 @@ for instance).
|
||||
The compatibility API falls back to `host` if `:authority` is not
|
||||
present. See [`request.authority`][] for more information. However,
|
||||
if you don't use the compatibility API (or use `req.headers` directly),
|
||||
you need to implement any fall-back behaviour yourself.
|
||||
you need to implement any fall-back behavior yourself.
|
||||
|
||||
[ALPN Protocol ID]: https://www.iana.org/assignments/tls-extensiontype-values/tls-extensiontype-values.xhtml#alpn-protocol-ids
|
||||
[ALPN negotiation]: #http2_alpn_negotiation
|
||||
|
@ -5228,7 +5228,7 @@ avoid introducing causing memory leaks. However, if the `async_resource` is
|
||||
garbage collected by JavaScript engine before the `napi_async_context` was
|
||||
destroyed by `napi_async_destroy`, calling `napi_async_context` related APIs
|
||||
like [`napi_open_callback_scope`][] and [`napi_make_callback`][] can cause
|
||||
problems like loss of async context when using the `AsyncLocalStoage` API.
|
||||
problems like loss of async context when using the `AsyncLocalStorage` API.
|
||||
|
||||
In order to retain ABI compatibility with previous versions, passing `NULL`
|
||||
for `async_resource` does not result in an error. However, this is not
|
||||
@ -5731,7 +5731,7 @@ after receiving a return value of `napi_closing` in response to a call to
|
||||
`napi_threadsafe_function` can be freed in its `napi_finalize` callback which
|
||||
was passed to `napi_create_threadsafe_function()`. The parameter
|
||||
`initial_thread_count` of `napi_create_threadsafe_function` marks the initial
|
||||
number of aquisitions of the thread-safe functions, instead of calling
|
||||
number of acquisitions of the thread-safe functions, instead of calling
|
||||
`napi_acquire_threadsafe_function` multiple times at creation.
|
||||
|
||||
Once the number of threads making use of a `napi_threadsafe_function` reaches
|
||||
|
Loading…
x
Reference in New Issue
Block a user