--- a/text/en/CHANGES	Mon Nov 14 13:14:48 2011 +0000
+++ b/text/en/CHANGES	Mon Nov 14 15:41:15 2011 +0000
@@ -1,15 +1,45 @@
 
+Changes with nginx 1.1.8                                         14 Nov 2011
+
+    *) Change: the ngx_http_limit_zone_module was renamed to the
+       ngx_http_limit_conn_module.
+
+    *) Change: the "limit_zone" directive was superseded by the
+       "limit_conn_zone" directive with a new syntax.
+
+    *) Feature: support for multiple "limit_conn" limits on the same level.
+
+    *) Feature: the "image_filter_sharpen" directive.
+
+    *) Bugfix: a segmentation fault might occur in a worker process if
+       resolver got a big DNS response.
+       Thanks to Ben Hawkes.
+
+    *) Bugfix: in cache key calculation if internal MD5 implementation was
+       used; the bug had appeared in 1.0.4.
+
+    *) Bugfix: the "If-Modified-Since", "If-Range", etc. client request
+       header lines might be passed to backend while caching; or not passed
+       without caching if caching was enabled in another part of the
+       configuration.
+
+    *) Bugfix: the module ngx_http_mp4_module sent incorrect
+       "Content-Length" response header line if the "start" argument was
+       used.
+       Thanks to Piotr Sikora.
+
+
 Changes with nginx 1.1.7                                         31 Oct 2011
 
-    *) Feature: support of several resolvers in the "resolver" directive.
+    *) Feature: support of several DNS servers in the "resolver" directive.
        Thanks to Kirill A. Korinskiy.
 
-    *) Bugfix: a segmentation fault occurred on start or while
+    *) Bugfix: a segmentation fault occurred on start or during
        reconfiguration if the "ssl" directive was used at http level and
        there was no "ssl_certificate" defined.
 
-    *) Bugfix: reduced memory consumption while proxying of big files if
-       they were buffered to disk.
+    *) Bugfix: reduced memory consumption while proxying big files if they
+       were buffered to disk.
 
     *) Bugfix: a segmentation fault might occur in a worker process if
        "proxy_http_version 1.1" directive was used.