Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit f42d6fa

Browse filesBrowse files
jeswcollinsMylesBorins
authored andcommitted
doc: excise "periodically" before "emit events"
"periodically" implies regular time intervals between emitted events, but as first example, "peer connects", implies, the time intervals may be irregular or unpredictable. PR-URL: #20581 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
1 parent 4662820 commit f42d6fa
Copy full SHA for f42d6fa

File tree

Expand file treeCollapse file tree

1 file changed

+1
-2
lines changed
Open diff view settings
Filter options
Expand file treeCollapse file tree

1 file changed

+1
-2
lines changed
Open diff view settings
Collapse file

‎doc/api/events.md‎

Copy file name to clipboardExpand all lines: doc/api/events.md
+1-2Lines changed: 1 addition & 2 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,7 @@
88

99
Much of the Node.js core API is built around an idiomatic asynchronous
1010
event-driven architecture in which certain kinds of objects (called "emitters")
11-
periodically emit named events that cause `Function` objects ("listeners") to be
12-
called.
11+
emit named events that cause `Function` objects ("listeners") to be called.
1312

1413
For instance: a [`net.Server`][] object emits an event each time a peer
1514
connects to it; a [`fs.ReadStream`][] emits an event when the file is opened;

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.