diff options
author | Rich Trott <rtrott@gmail.com> | 2019-06-20 22:54:55 +0300 |
---|---|---|
committer | Rich Trott <rtrott@gmail.com> | 2019-06-23 17:09:34 +0300 |
commit | 5faa53789a01427928f03c784219395e2092c8ca (patch) | |
tree | 967b179f55b95b25b67f345a54c6ce78b7d5c9be /doc/api/events.md | |
parent | 2cd4a6f4b4727cf939b93c034b3a13285cdb17ec (diff) |
doc: remove "note that" from events.md
Refs: https://github.com/nodejs/remark-preset-lint-node/pull/16
PR-URL: https://github.com/nodejs/node/pull/28329
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Diffstat (limited to 'doc/api/events.md')
-rw-r--r-- | doc/api/events.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/api/events.md b/doc/api/events.md index 37c8716e2c5..1e41b10b8c7 100644 --- a/doc/api/events.md +++ b/doc/api/events.md @@ -261,7 +261,7 @@ change affects *all* `EventEmitter` instances, including those created before the change is made. However, calling [`emitter.setMaxListeners(n)`][] still has precedence over `EventEmitter.defaultMaxListeners`. -Note that this is not a hard limit. The `EventEmitter` instance will allow +This is not a hard limit. The `EventEmitter` instance will allow more listeners to be added but will output a trace warning to stderr indicating that a "possible EventEmitter memory leak" has been detected. For any single `EventEmitter`, the `emitter.getMaxListeners()` and `emitter.setMaxListeners()` @@ -508,7 +508,7 @@ added: v0.1.26 Removes all listeners, or those of the specified `eventName`. -Note that it is bad practice to remove listeners added elsewhere in the code, +It is bad practice to remove listeners added elsewhere in the code, particularly when the `EventEmitter` instance was created by some other component or module (e.g. sockets or file streams). @@ -539,7 +539,7 @@ listener array. If any single listener has been added multiple times to the listener array for the specified `eventName`, then `removeListener()` must be called multiple times to remove each instance. -Note that once an event has been emitted, all listeners attached to it at the +Once an event has been emitted, all listeners attached to it at the time of emitting will be called in order. This implies that any `removeListener()` or `removeAllListeners()` calls *after* emitting and *before* the last listener finishes execution will not remove them from |