Commit 520ef83
doc: remove "note that" from events.md
Refs: nodejs/remark-preset-lint-node#16
PR-URL: #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>1 parent d65c90b commit 520ef83
1 file changed
Lines changed: 3 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -261,7 +261,7 @@ change affects *all* `EventEmitter` instances, including those created before | |||
| 261 | 261 | the change is made. However, calling [`emitter.setMaxListeners(n)`][] still has | |
| 262 | 262 | precedence over `EventEmitter.defaultMaxListeners`. | |
| 263 | 263 | ||
| 264 | - Note that this is not a hard limit. The `EventEmitter` instance will allow | ||
| 264 | + This is not a hard limit. The `EventEmitter` instance will allow | ||
| 265 | 265 | more listeners to be added but will output a trace warning to stderr indicating | |
| 266 | 266 | that a "possible EventEmitter memory leak" has been detected. For any single | |
| 267 | 267 | `EventEmitter`, the `emitter.getMaxListeners()` and `emitter.setMaxListeners()` | |
@@ -508,7 +508,7 @@ added: v0.1.26 | |||
| 508 | 508 | ||
| 509 | 509 | Removes all listeners, or those of the specified `eventName`. | |
| 510 | 510 | ||
| 511 | - Note that it is bad practice to remove listeners added elsewhere in the code, | ||
| 511 | + It is bad practice to remove listeners added elsewhere in the code, | ||
| 512 | 512 | particularly when the `EventEmitter` instance was created by some other | |
| 513 | 513 | component or module (e.g. sockets or file streams). | |
| 514 | 514 | ||
@@ -539,7 +539,7 @@ listener array. If any single listener has been added multiple times to the | |||
| 539 | 539 | listener array for the specified `eventName`, then `removeListener()` must be | |
| 540 | 540 | called multiple times to remove each instance. | |
| 541 | 541 | ||
| 542 | - Note that once an event has been emitted, all listeners attached to it at the | ||
| 542 | + Once an event has been emitted, all listeners attached to it at the | ||
| 543 | 543 | time of emitting will be called in order. This implies that any | |
| 544 | 544 | `removeListener()` or `removeAllListeners()` calls *after* emitting and | |
| 545 | 545 | *before* the last listener finishes execution will not remove them from | |
0 commit comments