Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc: fix typos on n-api #19385

Closed
wants to merge 1 commit into from
Closed

doc: fix typos on n-api #19385

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions doc/api/n-api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -615,7 +615,7 @@ are no longer required, the scope can be 'closed' and any handles associated
with the scope are invalidated. The methods available to open/close scopes are
[`napi_open_handle_scope`][] and [`napi_close_handle_scope`][].

N-API only supports a single nested hiearchy of scopes. There is only one
N-API only supports a single nested hierarchy of scopes. There is only one
active scope at any time, and all new handles will be associated with that
scope while it is active. Scopes must be closed in the reverse order from
which they are opened. In addition, all scopes created within a native method
Expand Down Expand Up @@ -887,7 +887,7 @@ object to which the reference is related.
Returns `napi_ok` if the API succeeded.

If still valid, this API returns the `napi_value` representing the
JavaScript Object associated with the `napi_ref`. Otherise, result
JavaScript Object associated with the `napi_ref`. Otherwise, result
will be NULL.

## Module registration
Expand Down Expand Up @@ -2150,7 +2150,7 @@ napi_status napi_is_arraybuffer(napi_env env, napi_value value, bool* result)

Returns `napi_ok` if the API succeeded.

This API checks if the Object passsed in is an array buffer.
This API checks if the Object passed in is an array buffer.

### napi_is_buffer
<!-- YAML
Expand All @@ -2167,7 +2167,7 @@ object.

Returns `napi_ok` if the API succeeded.

This API checks if the Object passsed in is a buffer.
This API checks if the Object passed in is a buffer.

### napi_is_error
<!-- YAML
Expand All @@ -2183,7 +2183,7 @@ napi_status napi_is_error(napi_env env, napi_value value, bool* result)

Returns `napi_ok` if the API succeeded.

This API checks if the Object passsed in is an Error.
This API checks if the Object passed in is an Error.

### napi_is_typedarray
<!-- YAML
Expand All @@ -2199,7 +2199,7 @@ napi_status napi_is_typedarray(napi_env env, napi_value value, bool* result)

Returns `napi_ok` if the API succeeded.

This API checks if the Object passsed in is a typed array.
This API checks if the Object passed in is a typed array.

### napi_is_dataview
<!-- YAML
Expand Down Expand Up @@ -2469,7 +2469,7 @@ and [`napi_get_element`][].

Returns `napi_ok` if the API succeeded.

This API returns the array of propertys for the Object passed in
This API returns the array of properties for the Object passed in

#### napi_set_property
<!-- YAML
Expand Down Expand Up @@ -3276,7 +3276,7 @@ napi_status napi_create_async_work(napi_env env,
that will be passed to possible async_hooks [`init` hooks][].
- `[in] async_resource_name`: Identifier for the kind of resource that is
being provided for diagnostic information exposed by the `async_hooks` API.
- `[in] execute`: The native function which should be called to excute
- `[in] execute`: The native function which should be called to execute
the logic asynchronously. The given function is called from a worker pool
thread and can execute in parallel with the main event loop thread.
- `[in] complete`: The native function which will be called when the
Expand Down