@@ -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
@@ -2161,7 +2161,7 @@ napi_status napi_is_arraybuffer(napi_env env, napi_value value, bool* result)
2161
2161
2162
2162
Returns `napi_ok` if the API succeeded.
2163
2163
2164
- This API checks if the Object passsed in is an array buffer.
2164
+ This API checks if the Object passed in is an array buffer.
2165
2165
2166
2166
### napi_is_buffer
2167
2167
<!-- YAML
@@ -2178,7 +2178,7 @@ object.
2178
2178
2179
2179
Returns `napi_ok` if the API succeeded.
2180
2180
2181
- This API checks if the Object passsed in is a buffer.
2181
+ This API checks if the Object passed in is a buffer.
2182
2182
2183
2183
### napi_is_error
2184
2184
<!-- YAML
@@ -2194,7 +2194,7 @@ napi_status napi_is_error(napi_env env, napi_value value, bool* result)
2194
2194
2195
2195
Returns `napi_ok` if the API succeeded.
2196
2196
2197
- This API checks if the Object passsed in is an Error.
2197
+ This API checks if the Object passed in is an Error.
2198
2198
2199
2199
### napi_is_typedarray
2200
2200
<!-- YAML
@@ -2210,7 +2210,7 @@ napi_status napi_is_typedarray(napi_env env, napi_value value, bool* result)
2210
2210
2211
2211
Returns `napi_ok` if the API succeeded.
2212
2212
2213
- This API checks if the Object passsed in is a typed array.
2213
+ This API checks if the Object passed in is a typed array.
2214
2214
2215
2215
### napi_is_dataview
2216
2216
<!-- YAML
@@ -2482,7 +2482,7 @@ and [`napi_get_element`][].
2482
2482
2483
2483
Returns `napi_ok` if the API succeeded.
2484
2484
2485
- This API returns the array of propertys for the Object passed in
2485
+ This API returns the array of properties for the Object passed in
2486
2486
2487
2487
#### napi_set_property
2488
2488
<!-- YAML
@@ -3290,7 +3290,7 @@ napi_status napi_create_async_work(napi_env env,
3290
3290
that will be passed to possible async_hooks [`init` hooks][].
3291
3291
- `[in] async_resource_name`: Identifier for the kind of resource that is
3292
3292
being provided for diagnostic information exposed by the `async_hooks` API.
3293
- - `[in] execute`: The native function which should be called to excute
3293
+ - `[in] execute`: The native function which should be called to execute
3294
3294
the logic asynchronously. The given function is called from a worker pool
3295
3295
thread and can execute in parallel with the main event loop thread.
3296
3296
- `[in] complete`: The native function which will be called when the
0 commit comments