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.

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

doc: reword possessive form of Node.js in docs #31748

Merged
merged 4 commits into from
Feb 18, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion doc/api/debugger.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ Break on start in myscript.js:1
debug>
```

Node.js's debugger client is not a full-featured debugger, but simple step and
The Node.js debugger client is not a full-featured debugger, but simple step and
inspection are possible.

Inserting the statement `debugger;` into the source code of a script will
Expand Down
2 changes: 1 addition & 1 deletion doc/api/http.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ HTTP message headers are represented by an object like this:

Keys are lowercased. Values are not modified.

In order to support the full spectrum of possible HTTP applications, Node.js's
In order to support the full spectrum of possible HTTP applications, the Node.js
HTTP API is very low-level. It deals with stream handling and message
parsing only. It parses a message into headers and body but it does not
parse the actual headers or the body.
Expand Down
8 changes: 4 additions & 4 deletions doc/api/process.md
Original file line number Diff line number Diff line change
Expand Up @@ -833,7 +833,7 @@ added: v0.7.2

* {number}

The port used by Node.js's debugger when enabled.
The port used by the Node.js debugger when enabled.

```js
process.debugPort = 5858;
Expand Down Expand Up @@ -2486,11 +2486,11 @@ cases:
handler.
* `2`: Unused (reserved by Bash for builtin misuse)
* `3` **Internal JavaScript Parse Error**: The JavaScript source code
internal in Node.js's bootstrapping process caused a parse error. This
internal in the Node.js bootstrapping process caused a parse error. This
is extremely rare, and generally can only happen during development
of Node.js itself.
* `4` **Internal JavaScript Evaluation Failure**: The JavaScript
source code internal in Node.js's bootstrapping process failed to
source code internal in the Node.js bootstrapping process failed to
return a function value when evaluated. This is extremely rare, and
generally can only happen during development of Node.js itself.
* `5` **Fatal Error**: There was a fatal unrecoverable error in V8.
Expand All @@ -2509,7 +2509,7 @@ cases:
* `9` **Invalid Argument**: Either an unknown option was specified,
or an option requiring a value was provided without a value.
* `10` **Internal JavaScript Run-Time Failure**: The JavaScript
source code internal in Node.js's bootstrapping process threw an error
source code internal in the Node.js bootstrapping process threw an error
when the bootstrapping function was called. This is extremely rare,
and generally can only happen during development of Node.js itself.
* `12` **Invalid Debug Argument**: The `--inspect` and/or `--inspect-brk`
Expand Down
2 changes: 1 addition & 1 deletion doc/guides/adding-new-napi-api.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Contributing a new API to N-API

N-API is Node.js's next generation ABI-stable API for native modules.
N-API is the next-generation ABI-stable API for native modules.
While improving the API surface is encouraged and welcomed, the following are
a set of principles and guidelines to keep in mind while adding a new
N-API API.
Expand Down