document the history of this project

Author: gms1

README.md

@@ -297,7 +297,7 @@ Thanks to [Orlando Vazquez](https://github.com/orlandov),
 [Eric Fredricksen](https://github.com/grumdrig) and
 [Ryan Dahl](https://github.com/ry) for their SQLite bindings for node, and to mraleph on Freenode's #v8 for answering questions.
 
-This module was originally created by [Mapbox](https://mapbox.com/), then it was then taken over by [Ghost](https://ghost.org), but was then deprecated without prior notice, so that the original is no longer maintained. See [TryGhost/node-sqlite3](https://github.com/TryGhost/node-sqlite3)
+This module was originally created by [Mapbox](https://mapbox.com/), then it was taken over by [Ghost](https://ghost.org), but was then deprecated without prior notice, so that the original is no longer maintained. See [TryGhost/node-sqlite3](https://github.com/TryGhost/node-sqlite3)
 
 I still hope that it will eventually be taken over by a larger organization, but in the meantime, I'm trying to maintain this fork here.
 

tools/benchmark-drivers/README.md

@@ -141,7 +141,8 @@ The **event loop** metrics show how the driver affects the event loop (measured
 | `@homeofthings/sqlite3` | ~47%        | ~5.3μs/op   | 3.3x more blocking than sync drivers            |
 | `node:sqlite`           | 100%        | ~1.8μs/op   | Blocks completely - all time is event loop time |
 
-Such metric shows the real cost: dependend on the operation, async drivers may even block the event loop **longer in total** for the same amount of work, even though they don't block it **completely** for the whole operation, like the sync drivers do. However, async drivers also do not always block the event loop **longer in total**:
+Such metric shows the real cost. 
+For some operations, especially on very fast operations lasting only a few microseconds, async drivers **may** even block the event loop **longer in total**, even though they don't block it **completely** for the whole operation, like the sync drivers do. Here, for example, even for very short operations, the event loopis is less burdened by the async driver:
 
 ```
 --- inserting rows individually ---
@@ -171,7 +172,7 @@ For I/O-bound operations, the async driver's overhead becomes negligible compare
 
 ### Long Running Query Performance
 
-With such a small amount of data we are currently using, it's not so easy to simulate longer running queries. That's why I tried it here using simple aggregation.
+With such a small amount of data we are currently using for this benchmark, it's not so easy to simulate longer running queries. That's why I tried it here using simple aggregation.
 
 Aggregate functions (COUNT, SUM, AVG, MIN, MAX) with WHERE clauses show even more dramatic async advantages: