1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: fix typos on n-api

Browse Source 
PR-URL: https://github.com/nodejs/node/pull/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>
This commit is contained in:
Kyle Robinson Young 2018-03-15 22:57:15 -07:00 committed by Vse Mozhet Byt
parent 9f3e5a0941
commit d20f1f004c
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/api/n-api.md
View File

@ -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
@ -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
@ -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
@ -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
@ -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
@ -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
@ -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
@ -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