Commit 1afff98
doc: fix typos
PR-URL: #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>1 parent 3ae2a0b commit 1afff98
4 files changed
Lines changed: 6 additions & 6 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -3863,7 +3863,7 @@ The supplied `callback` function is called with two arguments: `err` and | |||
| 3863 | 3863 | `derivedKey`. If an errors occurs while deriving the key, `err` will be set; | |
| 3864 | 3864 | otherwise `err` will be `null`. The successfully generated `derivedKey` will | |
| 3865 | 3865 | be passed to the callback as an {ArrayBuffer}. An error will be thrown if any | |
| 3866 | - of the input aguments specify invalid values or types. | ||
| 3866 | + of the input arguments specify invalid values or types. | ||
| 3867 | 3867 | ||
| 3868 | 3868 | ```mjs | |
| 3869 | 3869 | const { | |
@@ -3911,7 +3911,7 @@ given `key`, `salt` and `info` are used with the `digest` to derive a key of | |||
| 3911 | 3911 | ||
| 3912 | 3912 | The successfully generated `derivedKey` will be returned as an {ArrayBuffer}. | |
| 3913 | 3913 | ||
| 3914 | - An error will be thrown if any of the input aguments specify invalid values or | ||
| 3914 | + An error will be thrown if any of the input arguments specify invalid values or | ||
| 3915 | 3915 | types, or if the derived key cannot be generated. | |
| 3916 | 3916 | ||
| 3917 | 3917 | ```mjs | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -2497,7 +2497,7 @@ is flushed. | |||
| 2497 | 2497 | Use [`response.writableFinished`][] or [`response.writableEnded`][] | |
| 2498 | 2498 | accordingly instead to avoid the ambiguity. | |
| 2499 | 2499 | ||
| 2500 | - To maintain existing behaviour `response.finished` should be replaced with | ||
| 2500 | + To maintain existing behavior `response.finished` should be replaced with | ||
| 2501 | 2501 | `response.writableEnded`. | |
| 2502 | 2502 | ||
| 2503 | 2503 | ### DEP0137: Closing fs.FileHandle on garbage collection | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -3837,7 +3837,7 @@ for instance). | |||
| 3837 | 3837 | The compatibility API falls back to `host` if `:authority` is not | |
| 3838 | 3838 | present. See [`request.authority`][] for more information. However, | |
| 3839 | 3839 | if you don't use the compatibility API (or use `req.headers` directly), | |
| 3840 | - you need to implement any fall-back behaviour yourself. | ||
| 3840 | + you need to implement any fall-back behavior yourself. | ||
| 3841 | 3841 | ||
| 3842 | 3842 | [ALPN Protocol ID]: https://www.iana.org/assignments/tls-extensiontype-values/tls-extensiontype-values.xhtml#alpn-protocol-ids | |
| 3843 | 3843 | [ALPN negotiation]: #http2_alpn_negotiation | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -5228,7 +5228,7 @@ avoid introducing causing memory leaks. However, if the `async_resource` is | |||
| 5228 | 5228 | garbage collected by JavaScript engine before the `napi_async_context` was | |
| 5229 | 5229 | destroyed by `napi_async_destroy`, calling `napi_async_context` related APIs | |
| 5230 | 5230 | like [`napi_open_callback_scope`][] and [`napi_make_callback`][] can cause | |
| 5231 | - problems like loss of async context when using the `AsyncLocalStoage` API. | ||
| 5231 | + problems like loss of async context when using the `AsyncLocalStorage` API. | ||
| 5232 | 5232 | ||
| 5233 | 5233 | In order to retain ABI compatibility with previous versions, passing `NULL` | |
| 5234 | 5234 | 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 | |||
| 5731 | 5731 | `napi_threadsafe_function` can be freed in its `napi_finalize` callback which | |
| 5732 | 5732 | was passed to `napi_create_threadsafe_function()`. The parameter | |
| 5733 | 5733 | `initial_thread_count` of `napi_create_threadsafe_function` marks the initial | |
| 5734 | - number of aquisitions of the thread-safe functions, instead of calling | ||
| 5734 | + number of acquisitions of the thread-safe functions, instead of calling | ||
| 5735 | 5735 | `napi_acquire_threadsafe_function` multiple times at creation. | |
| 5736 | 5736 | ||
| 5737 | 5737 | Once the number of threads making use of a `napi_threadsafe_function` reaches | |
0 commit comments