From d6b9417c5f49aa5bab163cd0419df6e8fe9e74ea Mon Sep 17 00:00:00 2001 From: Mike McNeil Date: Fri, 1 May 2020 19:26:57 -0500 Subject: [PATCH] a touch more realistic --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0c84365..7b2629f 100644 --- a/README.md +++ b/README.md @@ -447,7 +447,7 @@ If you're using Node >= v7.9, you're in luck. With `await`, flow control works Sorry to hear that... Once again, `await` solves all of these problems too. It's the biggest boon to JavaScript development since Node.js was released. -But don't worry- this section's for you. Since Node.js is asynchronous, when using Node < v7.9, seemingly-tricky flow control problems often arise in practical, userland code. Fortunately, they're easy to solve when equipped with the proper tools and strategies. +But don't worry- this section's for you. Since Node.js is asynchronous, when using Node < v7.9, seemingly-tricky flow control problems often arise in practical, userland code. Fortunately, they're solveable when equipped with the proper tools and strategies. > Most of the examples below use simple Node callbacks, but note that many similar affordances are available for promise-chaining -- for example, check out `.toPromise()` ([below](#toPromise)) and `Promise.all()` (in bluebird, or native in ES6, etc.). The concepts are more or less the same regardless. >