-
Notifications
You must be signed in to change notification settings - Fork 30.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: fix typos in event loop doc to aid readability #6916
Conversation
Typos in the `setTimeout` vs. `setImmediate` section were hindering readability. Fixed these typos.
LGTM. cc @jasnell - especially for style of language. |
The order in which they are executed varies depending on the context in | ||
which they are called. If both are called in the main module, then you | ||
are bound by how fast your process goes (which is impacted by other | ||
programs running on your machine). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would prefer to rework this a bit to avoid the use of you
and your
. Perhaps...
The order in which the timers are executed will vary depending on the context
in which they are called. If both are called from within the main module, then timing
will be bound by the performance of the process (which can be impacted by other
applications running on the machine).
Or something along those lines.
@kevmannn can you remove the unrelated commits from the branch please? |
Use 'the process' instead of 'your process'.
@eljefedelrodeodeljefe 😰 Yep - done. |
Commit message doesnt meet the standard mentioned in the contributing guidelines I guess. Apart from that LGTM. Can you squash the commits please? |
Typos in the `setTimeout` vs. `setImmediate` section were hindering readability. Fixed these typos. PR-URL: #6916 Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Robert Jefe Lindstaedt <robert.lindstaedt@gmail.com>
I went ahead and formatted this for you. I believe it is you first time contribution here right? Landed in af61ebf. |
Thanks @eljefedelrodeodeljefe - (well one of the first) |
Typos in the `setTimeout` vs. `setImmediate` section were hindering readability. Fixed these typos. PR-URL: nodejs#6916 Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Robert Jefe Lindstaedt <robert.lindstaedt@gmail.com>
Typos in the `setTimeout` vs. `setImmediate` section were hindering readability. Fixed these typos. PR-URL: #6916 Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Robert Jefe Lindstaedt <robert.lindstaedt@gmail.com>
Typos in the `setTimeout` vs. `setImmediate` section were hindering readability. Fixed these typos. PR-URL: #6916 Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Robert Jefe Lindstaedt <robert.lindstaedt@gmail.com>
Typos in the `setTimeout` vs. `setImmediate` section were hindering readability. Fixed these typos. PR-URL: #6916 Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Robert Jefe Lindstaedt <robert.lindstaedt@gmail.com>
Typos in the `setTimeout` vs. `setImmediate` section were hindering readability. Fixed these typos. PR-URL: #6916 Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Robert Jefe Lindstaedt <robert.lindstaedt@gmail.com>
Checklist
Affected core subsystem(s)
doc
Description of change
Typos in the
setTimeout
vs.setImmediate
section were hinderingreadability. Fixed these typos.