README.md in boojs-0.0.20 vs README.md in boojs-0.0.21

@@ -8,14 +8,13 @@
 <p align="center">
   <img src="https://raw.githubusercontent.com/sotownsend/boojs/master/usage.gif" />
 </p>
 
 # What is this?
-A simple tool that allows you to execute javascript in the command line as if you were in a browser. Built on-top of [PhantomJS](http://phantomjs.org/) and
-acts as a well-behaved unix tool.
+**BooJS** allows you to execute javascript on the command line as if you were in a browser. It has well defined behavior that follows `unix` conventions and is built on-top of [PhantomJS](http://phantomjs.org/).
 
-**Wait, isn't this just NodeJS? No, they are for different things. BooJS gives you the full DOM, you can call `document` in BooJS and import arbitrary browser javascript libraries.**
+**BooJS** was purpose built for our continuous integration infrastructure at [Fittr®](http://www.fittr.com).
 
 # Setup
 ```sh
 #Setup
 gem install boojs
@@ -72,9 +71,22 @@
 - If you **want to contribute**, submit a pull request.
 
 ---
 
 ## FAQ
+
+### Wait, isn't this just NodeJS?
+No, they are for different things. BooJS gives you the full DOM, you can call `document` in BooJS and import arbitrary browser javascript libraries.
+
+### ...But PhantomJS has a perfectly good REPL, kids these days...
+There are a myriad issues with the *PhantomJS repl*; most notably, the *PhantomJS repl*:
+  * Outputs special format characters even when not attached to a `tty`
+  * Does not have well defined behavior which makes it a nightmare to integrate with
+  * **Has no support for asynchronous stdin**
+  * Changes what it considers a newline based on the attached terminal (A QT quirk)
+  * Is not a unix tool in any sense
+
+I don't think any of this is the `PhantomJS`'s team fault; it's just not their focus or target.
 
 ### When should I use boojs?
 
 When you need to test javascript code that needs to run in a browser but don't necessarily need to test the UI components.