fixed docs only , bumbped version for npm

README.md

@@ -34,7 +34,7 @@ Speed was our greatest concern and not a full featured queue.
 
 ### Using TypeScript
 ```ts
-  import {ZeroQ} from 'zeroq';
+  import {DataQueue , TasksQueue} from 'zeroq';
   //Now you can use both `ZeroQ.DataQueue` and `ZeroQ.TasksQueue`
 
 ```
@@ -155,26 +155,25 @@ While Node.js doesn't preform any task in parallel, the OS do.
 Some of the following messages will be lost because the OS can't write two messages in parallel.
 ```js
 const net = require('net');
-const writeQueue = new TasksQueue(1);
 const client = net.createConnection({ path: '/tmp/app.sock' }, () => {
     for (let i=0;i<10000;i++){
-        writeQueue.push(()=>{
-            client.write(`check out ${i}` , writeQueue.release)
-        })
+        client.write(`check out ${i}`)
     }
 });
-
 ```
 With tasks queue it's super safe and simple to make sure all your messages would arrive
 ```js
 const net = require('net');
+const writeQueue = new TasksQueue(1);
 const client = net.createConnection({ path: '/tmp/app.sock' }, () => {
     for (let i=0;i<10000;i++){
-        client.write(`check out ${i}`)
+        writeQueue.push(()=>{
+            client.write(`check out ${i}` , writeQueue.release)
+        })
     }
 });
-```
 
+```
 ### Asynchronous proccesing thousands of files
 ```js
   const queue = new TasksQueue(1000);

package.json

@@ -1,6 +1,6 @@
 {
   "name": "zeroq",
-  "version": "1.0.7",
+  "version": "1.0.9",
   "description": "Fast and simple in-memory queue implementation with configurable max concurrecy",
   "main": "src/zeroq.js",
   "types": "src/zeroq.d.ts",