Commit c1fa092
doc: fix typos on n-api
PR-URL: #19385
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Reviewed-By: Franziska Hinkelmann <franziska.hinkelmann@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>1 parent 7a3d1d2 commit c1fa092
1 file changed
Lines changed: 8 additions & 8 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -615,7 +615,7 @@ are no longer required, the scope can be 'closed' and any handles associated | |||
| 615 | 615 | with the scope are invalidated. The methods available to open/close scopes are | |
| 616 | 616 | [`napi_open_handle_scope`][] and [`napi_close_handle_scope`][]. | |
| 617 | 617 | ||
| 618 | - N-API only supports a single nested hiearchy of scopes. There is only one | ||
| 618 | + N-API only supports a single nested hierarchy of scopes. There is only one | ||
| 619 | 619 | active scope at any time, and all new handles will be associated with that | |
| 620 | 620 | scope while it is active. Scopes must be closed in the reverse order from | |
| 621 | 621 | which they are opened. In addition, all scopes created within a native method | |
@@ -886,7 +886,7 @@ object to which the reference is related. | |||
| 886 | 886 | Returns `napi_ok` if the API succeeded. | |
| 887 | 887 | ||
| 888 | 888 | If still valid, this API returns the `napi_value` representing the | |
| 889 | - JavaScript Object associated with the `napi_ref`. Otherise, result | ||
| 889 | + JavaScript Object associated with the `napi_ref`. Otherwise, result | ||
| 890 | 890 | will be NULL. | |
| 891 | 891 | ||
| 892 | 892 | ## Module registration | |
@@ -2148,7 +2148,7 @@ napi_status napi_is_arraybuffer(napi_env env, napi_value value, bool* result) | |||
| 2148 | 2148 | ||
| 2149 | 2149 | Returns `napi_ok` if the API succeeded. | |
| 2150 | 2150 | ||
| 2151 | - This API checks if the Object passsed in is an array buffer. | ||
| 2151 | + This API checks if the Object passed in is an array buffer. | ||
| 2152 | 2152 | ||
| 2153 | 2153 | ### napi_is_buffer | |
| 2154 | 2154 | <!-- YAML | |
@@ -2165,7 +2165,7 @@ object. | |||
| 2165 | 2165 | ||
| 2166 | 2166 | Returns `napi_ok` if the API succeeded. | |
| 2167 | 2167 | ||
| 2168 | - This API checks if the Object passsed in is a buffer. | ||
| 2168 | + This API checks if the Object passed in is a buffer. | ||
| 2169 | 2169 | ||
| 2170 | 2170 | ### napi_is_error | |
| 2171 | 2171 | <!-- YAML | |
@@ -2181,7 +2181,7 @@ napi_status napi_is_error(napi_env env, napi_value value, bool* result) | |||
| 2181 | 2181 | ||
| 2182 | 2182 | Returns `napi_ok` if the API succeeded. | |
| 2183 | 2183 | ||
| 2184 | - This API checks if the Object passsed in is an Error. | ||
| 2184 | + This API checks if the Object passed in is an Error. | ||
| 2185 | 2185 | ||
| 2186 | 2186 | ### napi_is_typedarray | |
| 2187 | 2187 | <!-- YAML | |
@@ -2197,7 +2197,7 @@ napi_status napi_is_typedarray(napi_env env, napi_value value, bool* result) | |||
| 2197 | 2197 | ||
| 2198 | 2198 | Returns `napi_ok` if the API succeeded. | |
| 2199 | 2199 | ||
| 2200 | - This API checks if the Object passsed in is a typed array. | ||
| 2200 | + This API checks if the Object passed in is a typed array. | ||
| 2201 | 2201 | ||
| 2202 | 2202 | ### napi_is_dataview | |
| 2203 | 2203 | <!-- YAML | |
@@ -2467,7 +2467,7 @@ and [`napi_get_element`][]. | |||
| 2467 | 2467 | ||
| 2468 | 2468 | Returns `napi_ok` if the API succeeded. | |
| 2469 | 2469 | ||
| 2470 | - This API returns the array of propertys for the Object passed in | ||
| 2470 | + This API returns the array of properties for the Object passed in | ||
| 2471 | 2471 | ||
| 2472 | 2472 | #### napi_set_property | |
| 2473 | 2473 | <!-- YAML | |
@@ -3275,7 +3275,7 @@ napi_status napi_create_async_work(napi_env env, | |||
| 3275 | 3275 | that will be passed to possible async_hooks [`init` hooks][]. | |
| 3276 | 3276 | - `[in] async_resource_name`: Identifier for the kind of resource that is | |
| 3277 | 3277 | being provided for diagnostic information exposed by the `async_hooks` API. | |
| 3278 | - - `[in] execute`: The native function which should be called to excute | ||
| 3278 | + - `[in] execute`: The native function which should be called to execute | ||
| 3279 | 3279 | the logic asynchronously. The given function is called from a worker pool | |
| 3280 | 3280 | thread and can execute in parallel with the main event loop thread. | |
| 3281 | 3281 | - `[in] complete`: The native function which will be called when the | |
0 commit comments