Skip to content

Commit 1dfd03b

Browse files
Update README.md (#1187)
* Update README.md Corrections of misspelled words.
1 parent 576128f commit 1dfd03b

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -16,15 +16,15 @@ provided by Node.js when using C++. It provides a C++ object model
1616
and exception handling semantics with low overhead.
1717

1818
There are three options for implementing addons: Node-API, nan, or direct
19-
use of internal V8, libuv and Node.js libraries. Unless there is a need for
20-
direct access to functionality which is not exposed by Node-API as outlined
19+
use of internal V8, libuv, and Node.js libraries. Unless there is a need for
20+
direct access to functionality that is not exposed by Node-API as outlined
2121
in [C/C++ addons](https://nodejs.org/dist/latest/docs/api/addons.html)
2222
in Node.js core, use Node-API. Refer to
2323
[C/C++ addons with Node-API](https://nodejs.org/dist/latest/docs/api/n-api.html)
2424
for more information on Node-API.
2525

2626
Node-API is an ABI stable C interface provided by Node.js for building native
27-
addons. It is independent from the underlying JavaScript runtime (e.g. V8 or ChakraCore)
27+
addons. It is independent of the underlying JavaScript runtime (e.g. V8 or ChakraCore)
2828
and is maintained as part of Node.js itself. It is intended to insulate
2929
native addons from changes in the underlying JavaScript engine and allow
3030
modules compiled for one version to run on later versions of Node.js without
@@ -46,7 +46,7 @@ provides an [ABI stability guide][] containing a detailed explanation of ABI
4646
stability in general, and the Node-API ABI stability guarantee in particular.
4747

4848
As new APIs are added to Node-API, node-addon-api must be updated to provide
49-
wrappers for those new APIs. For this reason node-addon-api provides
49+
wrappers for those new APIs. For this reason, node-addon-api provides
5050
methods that allow callers to obtain the underlying Node-API handles so
5151
direct calls to Node-API and the use of the objects/methods provided by
5252
node-addon-api can be used together. For example, in order to be able
@@ -56,7 +56,7 @@ APIs exposed by node-addon-api are generally used to create and
5656
manipulate JavaScript values. Concepts and operations generally map
5757
to ideas specified in the **ECMA262 Language Specification**.
5858

59-
The [Node-API Resource](https://nodejs.github.io/node-addon-examples/) offers an
59+
The [Node-API Resource](https://nodejs.github.io/node-addon-examples/) offers an
6060
excellent orientation and tips for developers just getting started with Node-API
6161
and node-addon-api.
6262

@@ -195,7 +195,7 @@ To run the **node-addon-api** tests with `--debug` option:
195195
npm run-script dev
196196
```
197197

198-
If you want faster build, you might use the following option:
198+
If you want a faster build, you might use the following option:
199199

200200
```
201201
npm run-script dev:incremental
@@ -223,7 +223,7 @@ See [benchmark/README.md](benchmark/README.md) for more details about running an
223223

224224
As node-addon-api's core mission is to expose the plain C Node-API as C++
225225
wrappers, tools that facilitate n-api/node-addon-api providing more
226-
convenient patterns on developing a Node.js add-ons with n-api/node-addon-api
226+
convenient patterns for developing a Node.js add-on with n-api/node-addon-api
227227
can be published to NPM as standalone packages. It is also recommended to tag
228228
such packages with `node-addon-api` to provide more visibility to the community.
229229

0 commit comments

Comments
 (0)