nodejs
diff --git a/Collapse file
‎doc/api/events.md‎
Copy file name to clipboardExpand all lines: doc/api/events.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff b/Collapse file
‎doc/api/events.md‎
Copy file name to clipboardExpand all lines: doc/api/events.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
@@ -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