doc: simplify sentences that use "considered"
Change many instances of "x is considered to be y" to "x is y". PR-URL: https://github.com/nodejs/node/pull/18095 Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
This commit is contained in:
parent
e42708c8e3
commit
c6bee70eec
@ -1126,10 +1126,10 @@ process.send({ foo: 'bar', baz: NaN });
|
||||
Child Node.js processes will have a [`process.send()`][] method of their own that
|
||||
allows the child to send messages back to the parent.
|
||||
|
||||
There is a special case when sending a `{cmd: 'NODE_foo'}` message. All messages
|
||||
containing a `NODE_` prefix in its `cmd` property are considered to be reserved
|
||||
for use within Node.js core and will not be emitted in the child's
|
||||
[`process.on('message')`][] event. Rather, such messages are emitted using the
|
||||
There is a special case when sending a `{cmd: 'NODE_foo'}` message. Messages
|
||||
containing a `NODE_` prefix in the `cmd` property are reserved for use within
|
||||
Node.js core and will not be emitted in the child's [`process.on('message')`][]
|
||||
event. Rather, such messages are emitted using the
|
||||
`process.on('internalMessage')` event and are consumed internally by Node.js.
|
||||
Applications should avoid using such messages or listening for
|
||||
`'internalMessage'` events as it is subject to change without notice.
|
||||
|
@ -622,7 +622,7 @@ Once a socket is assigned to this request and is connected
|
||||
added: v0.5.9
|
||||
-->
|
||||
|
||||
* `timeout` {number} Milliseconds before a request is considered to be timed out.
|
||||
* `timeout` {number} Milliseconds before a request times out.
|
||||
* `callback` {Function} Optional function to be called when a timeout occurs. Same as binding to the `timeout` event.
|
||||
|
||||
Once a socket is assigned to this request and is connected
|
||||
|
@ -60,8 +60,8 @@ The `'close'` event is emitted when one of the following occur:
|
||||
|
||||
The listener function is called without passing any arguments.
|
||||
|
||||
The `readline.Interface` instance should be considered to be "finished" once
|
||||
the `'close'` event is emitted.
|
||||
The `readline.Interface` instance is finished once the `'close'` event is
|
||||
emitted.
|
||||
|
||||
### Event: 'line'
|
||||
<!-- YAML
|
||||
|
@ -29,8 +29,7 @@ For example, at the time of this writing:
|
||||
released as part of the Chromium **canary** builds. This branch will be
|
||||
promoted to beta next when V8 5.5 ships as stable.
|
||||
|
||||
All older branches are considered **abandoned**, and are not maintained by the
|
||||
V8 team.
|
||||
All older branches are abandoned and are not maintained by the V8 team.
|
||||
|
||||
### V8 merge process overview
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user