update document

CHANGELOG.md

@@ -5,7 +5,11 @@ Changelog
 
 # 1.x release
 
-## v1.1.2 (master)
+## v1.2.0 (master)
+
+- Enhance: now fetch.Headers and fetch.Response are exposed, making testing easier
+
+## v1.1.2
 
 - Fix: `Headers` should only support `String` and `Array` properties, and ignore others
 

LIMITS.md

@@ -1,6 +1,6 @@
 
-Known limits
-============
+Known differences
+=================
 
 *As of 1.x release*
 
@@ -16,4 +16,6 @@ Known limits
 
 - Only support `res.text()` and `res.json()` at the moment, until there are good use-cases for blob.
 
+- Only expose `Response` and `Headers` constructors at the moment, we don't see a good use-case for `Request` interface yet.
+
 - There is currently no built-in caching, as server-side caching varies by use-cases.

README.md

@@ -26,12 +26,11 @@ Hence `node-fetch`, minimal code for a `window.fetch` compatible API on node.js/
 - Use native stream for body, on both request and response.
 - Decode content encoding (gzip/deflate) properly, and convert string output (such as `res.text()` and `res.json()`) to utf-8 automatically.
 - Useful extensions such as timeout, redirect limit, response size limit.
-- Exposes `Response` and `Headers` constructors
 
 
 # Difference from client-side fetch
 
-- See [Known limits](https://github.com/bitinn/node-fetch/blob/master/LIMITS.md) for details.
+- See [Known Differences](https://github.com/bitinn/node-fetch/blob/master/LIMITS.md) for details.
 - If you happen to use a missing feature that `window.fetch` offers, feel free to open an issue.
 - Pull requests are welcomed too!