nginx-0.8.18-RELEASE
diff --git a/docs/xml/nginx/changes.xml b/docs/xml/nginx/changes.xml
index 53a2583..3df3bee 100644
--- a/docs/xml/nginx/changes.xml
+++ b/docs/xml/nginx/changes.xml
@@ -9,6 +9,94 @@
 <title lang="en">nginx changelog</title>
 
 
+<changes ver="0.8.18" date="06.10.2009">
+
+<change type="feature">
+<para lang="ru">
+ÄÉÒÅËÔÉ×Á read_ahead.
+</para>
+<para lang="en">
+the "read_ahead" directive.
+</para>
+</change>
+
+<change type="feature">
+<para lang="ru">
+ÔÅÐÅÒØ ÍÏÖÎÏ ÉÓÐÏÌØÚÏ×ÁÔØ ÎÅÓËÏÌØËÏ ÄÉÒÅËÔÉ× perl_modules.
+</para>
+<para lang="en">
+now several "perl_modules" directive may be used.
+</para>
+</change>
+
+<change type="feature">
+<para lang="ru">
+ÄÉÒÅËÔÉ×Ù limit_req_log_level É limit_conn_log_level.
+</para>
+<para lang="en">
+the "limit_req_log_level" and "limit_conn_log_level" directives.
+</para>
+</change>
+
+<change type="bugfix">
+<para lang="ru">
+ôÅÐÅÒØ ÄÉÒÅËÔÉ×Á limit_req ÓÏÏÔ×ÅÔÓÔ×ÕÅÔ ÁÌÇÏÒÉÔÍÕ leaky bucket.<br/>
+óÐÁÓÉÂÏ íÁËÓÉÍÕ äÕÎÉÎÕ.
+</para>
+<para lang="en">
+now "limit_req" directive conforms to the leaky bucket algorithm.<br/>
+Thanks to Maxim Dounin.
+</para>
+</change>
+
+<change type="bugfix">
+<para lang="ru">
+nginx ÎÅ ÒÁÂÏÔÁÌ ÎÁ Linux/sparc.<br/>
+óÐÁÓÉÂÏ Marcus Ramberg.
+</para>
+<para lang="en">
+nginx did not work on Linux/sparc.<br/>
+Thanks to Marcus Ramberg.
+</para>
+</change>
+
+<change type="bugfix">
+<para lang="ru">
+nginx ÓÌÁÌ ÓÉÍ×ÏÌ '\0' × ÓÔÒÏËÅ "Location" × ÚÁÇÏÌÏ×ËÅ × ÏÔ×ÅÔÅ ÎÁ ÚÁÐÒÏÓ
+MKCOL.<br/>
+óÐÁÓÉÂÏ Xie Zhenye.
+</para>
+<para lang="en">
+nginx sent '\0' in a "Location" response header line on MKCOL request.<br/>
+Thanks to Xie Zhenye.
+</para>
+</change>
+
+<change type="bugfix">
+<para lang="ru">
+×ÍÅÓÔÏ ËÏÄÁ ÏÔ×ÅÔÁ 499 × ÌÏÇ ÚÁÐÉÓÙ×ÁÌÓÑ ËÏÄ 0;
+ÏÛÉÂËÁ ÐÏÑ×ÉÌÁÓØ × 0.8.11.
+</para>
+<para lang="en">
+zero status code was logged instead of 499 status code;
+the bug had appeared in 0.8.11.
+</para>
+</change>
+
+<change type="bugfix">
+<para lang="ru">
+ÕÔÅÞËÉ ÓÏËÅÔÏ×;
+ÏÛÉÂËÁ ÐÏÑ×ÉÌÁÓØ × 0.8.11.
+</para>
+<para lang="en">
+socket leak;
+the bug had appeared in 0.8.11.
+</para>
+</change>
+
+</changes>
+
+
 <changes ver="0.8.17" date="28.09.2009">
 
 <change type="security">