standardize spacing

1 files changed, 17 insertions, 17 deletions

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 442731f..5eef365 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,12 +1,12 @@
 # v2.0.0
 
-Lots of changes here! The biggest feature is modularization.  You can now `require("async/series")` to only require the `series` function.  Every Async library function is available this way.  You still can `require("async")` to require the entire library, like you could do before.
+Lots of changes here! The biggest feature is modularization. You can now `require("async/series")` to only require the `series` function. Every Async library function is available this way. You still can `require("async")` to require the entire library, like you could do before.
 
-We also provide Async as a collection of ES2015 modules. You can now `import {each} from 'async-es'` or `import waterfall from 'async-es/waterfall'`.  If you are using only a few Async functions, and are using a ES bundler such as Rollup, this can significantly lower your build size.
+We also provide Async as a collection of ES2015 modules. You can now `import {each} from 'async-es'` or `import waterfall from 'async-es/waterfall'`. If you are using only a few Async functions, and are using a ES bundler such as Rollup, this can significantly lower your build size.
 
 Major thanks to [**@Kikobeats**](github.com/Kikobeats), [**@aearly**](github.com/aearly) and [**@megawac**](github.com/megawac) for doing the majority of the modularization work, as well as [**@jdalton**](github.com/jdalton) and [**@Rich-Harris**](github.com/Rich-Harris) for advisory work on the general modularization strategy.
 
-Another one of the general themes of the 2.0 release is standardization of what an "async" function is.  We are now more strictly following the node-style continuation passing style.  That is, an async function is a function that:
+Another one of the general themes of the 2.0 release is standardization of what an "async" function is. We are now more strictly following the node-style continuation passing style. That is, an async function is a function that:
 
 1. Takes a variable number of arguments
 2. The last argument is always a callback
@@ -17,12 +17,12 @@ Another one of the general themes of the 2.0 release is standardization of what
 
 There were several cases where Async accepted some functions that did not strictly have these properties, most notably `auto`, `every`, `some`, and `filter`.
 
-Another theme is performance.  We have eliminated internal deferrals in all cases where they make sense.  For example, in `waterfall` and `auto`, there was a `setImmediate` between each task -- these deferrals have been removed.  A `setImmediate` call can add up to 1ms of delay. This might not seem like a lot, but it can add up if you are using many Async functions in the course of processing a HTTP request, for example.  Nearly all asynchronous functions that do I/O already have some sort of deferral built in, so the extra deferral is unnecessary.  The trade-off of this change is removing our built-in stack-overflow defense. Many synchronous callback calls in series can quickly overflow the JS call stack.  If you do have a function that is sometimes synchronous (calling its callback on the same tick), and are running into stack overflows, wrap it with `async.ensureAsync()`.
+Another theme is performance. We have eliminated internal deferrals in all cases where they make sense. For example, in `waterfall` and `auto`, there was a `setImmediate` between each task -- these deferrals have been removed. A `setImmediate` call can add up to 1ms of delay. This might not seem like a lot, but it can add up if you are using many Async functions in the course of processing a HTTP request, for example. Nearly all asynchronous functions that do I/O already have some sort of deferral built in, so the extra deferral is unnecessary. The trade-off of this change is removing our built-in stack-overflow defense. Many synchronous callback calls in series can quickly overflow the JS call stack. If you do have a function that is sometimes synchronous (calling its callback on the same tick), and are running into stack overflows, wrap it with `async.ensureAsync()`.
 
 ## New Features
 
-- Async is now modularized.  Individual functions can be `require()`d from the main package. (`require('async/auto')`) (#984, #996)
-- Async is also available as a collection of ES2015 modules in the new `async-es` package.  (`import {forEachSeries} from 'async-es'`) (#984, #996)
+- Async is now modularized. Individual functions can be `require()`d from the main package. (`require('async/auto')`) (#984, #996)
+- Async is also available as a collection of ES2015 modules in the new `async-es` package. (`import {forEachSeries} from 'async-es'`) (#984, #996)
 - Added `race`, analogous to `Promise.race()`. It will run an array of async tasks in parallel and will call its callback with the result of the first task to respond. (#568, #1038)
 - Added `timeout`, a wrapper for an async function that will make the task time-out after the specified time. (#1007, #1027)
 - `constant` supports dynamic arguments -- it will now always use its last argument as the callback. (#1016, #1052)
@@ -34,18 +34,18 @@ Another theme is performance.  We have eliminated internal deferrals in all case
 
 ## Breaking changes
 
-- Calling a callback more than once is considered an error, and an error will be thrown.  This had an explicit breaking change in `waterfall`. If you were relying on this behavior, you should more accurately represent your control flow as an event emitter or stream. (#814, #815, #1048, #1050)
-- `auto` task functions now always take the callback as the last argument.  If a task has dependencies, the `results` object will be passed as the first argument. To migrate old task functions, wrap them with [`_.flip`](https://lodash.com/docs#flip) (#1036, #1042)
+- Calling a callback more than once is considered an error, and an error will be thrown. This had an explicit breaking change in `waterfall`. If you were relying on this behavior, you should more accurately represent your control flow as an event emitter or stream. (#814, #815, #1048, #1050)
+- `auto` task functions now always take the callback as the last argument. If a task has dependencies, the `results` object will be passed as the first argument. To migrate old task functions, wrap them with [`_.flip`](https://lodash.com/docs#flip) (#1036, #1042)
 - Internal `setImmediate` calls have been refactored away. This may make existing flows vulnerable to stack overflows if you use many synchronous functions in series. Use `ensureAsync` to work around this. (#696, #704, #1049, #1050)
 - `filter`, `reject`, `some`, `every`, and related functions now expect an error as the first callback argument, rather than just a simple boolean. Pass `null` as the first argument, or use `fs.access` instead of `fs.exists`. (#118, #774, #1028, #1041)
-- `{METHOD}` and `{METHOD}Series` are now implemented in terms of `{METHOD}Limit`.  This is a major internal simplification, and is not expected to cause many problems, but it does subtly affect how functions execute internally. (#778, #847)
-- `retry`'s callback is now optional.  Previously, omitting the callback would partially apply the function, meaning it could be passed directly as a task to `series` or `auto`.  The partially applied "control-flow" behavior has been separated out into `retryable`.
+- `{METHOD}` and `{METHOD}Series` are now implemented in terms of `{METHOD}Limit`. This is a major internal simplification, and is not expected to cause many problems, but it does subtly affect how functions execute internally. (#778, #847)
+- `retry`'s callback is now optional. Previously, omitting the callback would partially apply the function, meaning it could be passed directly as a task to `series` or `auto`. The partially applied "control-flow" behavior has been separated out into `retryable`.
 - The timing of the `q.saturated()` callback in a `queue` has been modified to better reflect when tasks pushed to the queue will start queueing. (#724, #1078)
 
 ## Other
 
 - Added `someSeries` and `everySeries` for symmetry, as well as a complete set of `any`/`anyLimit`/`anySeries` and `all`/`/allLmit`/`allSeries` aliases.
-- Added `find` as an alias for `detect`  (as well as `findLimit` and `findSeries`).
+- Added `find` as an alias for `detect. (as well as `findLimit` and `findSeries`).
 - Various doc fixes (#1005, #1008, #1010, #1015, #1021, #1037)
 
 ------------------------------------------
@@ -59,15 +59,15 @@ Another theme is performance.  We have eliminated internal deferrals in all case
 - Fix issue with `pause` in `queue` with concurrency enabled (#946)
 - `while` and `until` now pass the final result to callback (#963)
 - `auto` will properly handle concurrency when there is no callback (#966)
-- `auto` will now  properly stop execution when an error occurs (#988, #993)
+- `auto` will no. properly stop execution when an error occurs (#988, #993)
 - Various doc fixes (#971, #980)
 
 # v1.5.0
 
 - Added `transform`, analogous to [`_.transform`](http://lodash.com/docs#transform) (#892)
 - `map` now returns an object when an object is passed in, rather than array with non-numeric keys. `map` will begin always returning an array with numeric indexes in the next major release. (#873)
-- `auto` now accepts an optional `concurrency` argument to limit the number of  running tasks (#637)
-- Added `queue#workersList()`, to retrieve the list  of currently running tasks. (#891)
+- `auto` now accepts an optional `concurrency` argument to limit the number o. running tasks (#637)
+- Added `queue#workersList()`, to retrieve the lis. of currently running tasks. (#891)
 - Various code simplifications (#896, #904)
 - Various doc fixes :scroll: (#890, #894, #903, #905, #912)
 
@@ -113,7 +113,7 @@ Bug Fixes:
 
 Bug Fix:
 
-- Small regression with synchronous iterator behavior in `eachSeries` with a 1-element array.  Before 1.1.0, `eachSeries`'s callback was called on the same tick, which this patch restores.  In 2.0.0, it will be called on the next tick.  (#782)
+- Small regression with synchronous iterator behavior in `eachSeries` with a 1-element array. Before 1.1.0, `eachSeries`'s callback was called on the same tick, which this patch restores. In 2.0.0, it will be called on the next tick. (#782)
 
 
 # v1.2.0
@@ -121,7 +121,7 @@ Bug Fix:
 New Features:
 
 - Added `timesLimit` (#743)
-- `concurrency` can be changed after initialization in `queue` by setting `q.concurrency`.  The new concurrency will be reflected the next time a task is processed. (#747, #772)
+- `concurrency` can be changed after initialization in `queue` by setting `q.concurrency`. The new concurrency will be reflected the next time a task is processed. (#747, #772)
 
 Bug Fixes:
 
@@ -132,7 +132,7 @@ Bug Fixes:
 
 Bug Fix:
 
-- Small regression with synchronous iterator behavior in `eachSeries` with a 1-element array.  Before 1.1.0, `eachSeries`'s callback was called on the same tick, which this patch restores.  In 2.0.0, it will be called on the next tick.  (#782)
+- Small regression with synchronous iterator behavior in `eachSeries` with a 1-element array. Before 1.1.0, `eachSeries`'s callback was called on the same tick, which this patch restores. In 2.0.0, it will be called on the next tick. (#782)
 
 
 # v1.1.0