Update README.md

Author: Salakar

README.md

@@ -7,7 +7,7 @@
 
 A high performance javascript redis parser built for [node_redis](https://github.com/NodeRedis/node_redis) and [ioredis](https://github.com/luin/ioredis).
 
-Generally all [RESP](http://redis.io/topics/protocol) data will be properly parsed by the parser.
+All [RESP](http://redis.io/topics/protocol) data is parsed by this parser.
 
 ## Install
 
@@ -22,7 +22,7 @@ npm install redis-parser
 ```js
 var Parser = require('redis-parser');
 
-new Parser(options);
+var myParser = new Parser(options);
 ```
 
 ### Possible options
@@ -31,7 +31,6 @@ new Parser(options);
 * `returnError`: *function*; mandatory
 * `returnFatalError`: *function*; optional, defaults to the returnError function
 * `returnBuffers`: *boolean*; optional, defaults to false
-* `stringNumbers`: *boolean*; optional, defaults to false
 
 ### Example
 
@@ -69,7 +68,7 @@ You do not have to use the returnFatalError function. Fatal errors will be retur
 
 And if you want to return buffers instead of strings, you can do this by adding the `returnBuffers` option.
 
-If you handle big numbers, you should pass the `stringNumbers` option. That case numbers above 2^53 can be handled properly without reduced precision.
+Big numbers that are too large for JS are automatically stringified.
 
 ```js
 // Same functions as in the first example
@@ -81,7 +80,6 @@ var parser = new Parser({
     returnError: function(err) {
         lib.returnError(err);
     },
-    stringNumbers: true, // Return all numbers as string instead of a js number
     returnBuffers: true // All strings are returned as buffer e.g. <Buffer 48 65 6c 6c 6f>
 });
 
@@ -90,12 +88,11 @@ var parser = new Parser({
 
 ## Protocol errors
 
-To handle protocol errors (this is very unlikely to happen) gracefully you should add the returnFatalError option, reject any still running command (they might have been processed properly but the reply is just wrong), destroy the socket and reconnect. Be aware that while doing this, no new command may be added, so all new commands have to be buffered in the meanwhile.
-Otherwise a chunk might still contain partial data of a following command that was already processed properly but answered in the same chunk as the command that resulted in the protocol error.
+To handle protocol errors (this is very unlikely to happen) gracefully you should add the returnFatalError option, reject any still running command (they might have been processed properly but the reply is just wrong), destroy the socket and reconnect. Note that while doing this no new command may be added, so all new commands have to be buffered in the meantime, otherwise a chunk might still contain partial data of a following command that was already processed properly but answered in the same chunk as the command that resulted in the protocol error.
 
 ## Contribute
 
-The parser is already optimized but there are likely further optimizations possible.
+The parser is highly optimized but there may still be further optimizations possible. 
 
 ```
 npm install