diff options
| author | Alexander Early <alexander.early@gmail.com> | 2015-08-23 20:53:36 -0700 |
|---|---|---|
| committer | Alexander Early <alexander.early@gmail.com> | 2015-08-23 20:53:36 -0700 |
| commit | b2fded336afaef589eddb602b29a228faffcb21e (patch) | |
| tree | 7f59c4c2b3c3dd6edaa42254b7cb1177a29d5041 | |
| parent | 92f78aebad222d60c13e4299c0e723f2fe2d6611 (diff) | |
| parent | 444a749b81a37ec70f6b833d00a5b947716359a1 (diff) | |
| download | async-b2fded336afaef589eddb602b29a228faffcb21e.tar.gz | |
Merge pull request #890 from gypsydave5/patch-1
adds caps to spelling of JavaScript :scroll:
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -86,7 +86,7 @@ async.eachSeries(hugeArray, function iterator(item, callback) { Async guards against synchronous functions in some, but not all, cases. If you are still running into stack overflows, you can defer as suggested above, or wrap functions with [`async.ensureAsync`](#ensureAsync) Functions that are asynchronous by their nature do not have this problem and don't need the extra callback deferral. -If javascript's event loop is still a bit nebulous, check out [this article](http://blog.carbonfive.com/2013/10/27/the-javascript-event-loop-explained/) or [this talk](http://2014.jsconf.eu/speakers/philip-roberts-what-the-heck-is-the-event-loop-anyway.html) for more detailed information about how it works. +If JavaScript's event loop is still a bit nebulous, check out [this article](http://blog.carbonfive.com/2013/10/27/the-javascript-event-loop-explained/) or [this talk](http://2014.jsconf.eu/speakers/philip-roberts-what-the-heck-is-the-event-loop-anyway.html) for more detailed information about how it works. ### Multiple callbacks |