Updated change log

CHANGES.md

@@ -59,7 +59,7 @@ replacements are listed here:
 (*) Use of ``thisp`` is discouraged. For calling methods, use ``post`` or
 ``invoke``.
 
-## 0.8.11 (unreleased)
+## 0.8.11
  - Added ``nfcall``, ``nfapply``, and ``nfbind`` as ``thisp``-less versions of
    ``ncall`, ``napply``, and ``nbind``. The latter are now deprecated. #142
  - Long stack traces no longer cause linearly-growing memory usage when chaining
@@ -69,6 +69,8 @@ replacements are listed here:
  - Fixed ``Q.timeout`` to clear its timeout handle when the promise is rejected;
    previously, it kept the event loop alive until the timeout period expired.
    #145 @dfilatov
+ - Added `q/queue` module, which exports an infinite promise queue
+   constructor.
 
 ## 0.8.10
 

README.md

@@ -4,9 +4,9 @@ If a function cannot return a value or throw an exception without
 blocking, it can return a promise instead.  A promise is an object
 that represents the return value or the thrown exception that the
 function may eventually provide.  A promise can also be used as a
-proxy for a [remote object][Q-Comm] to overcome latency.
+proxy for a [remote object][Q-Connection] to overcome latency.
 
-[Q-Comm]: https://github.com/kriskowal/q-comm
+[Q-Connection]: https://github.com/kriskowal/q-connection
 
 On the first pass, promises can mitigate the “[Pyramid of
 Doom][POD]”: the situation where code marches to the right faster