--- a/docs/xml/nginx/changes.xml
+++ b/docs/xml/nginx/changes.xml
@@ -9,6 +9,55 @@
 <title lang="en">nginx changelog</title>
 
 
+<changes ver="0.7.3" date="23.06.2008">
+
+<change type="change">
+<para lang="ru">
+MIME-тип для расширения rss изменён на "application/rss+xml".
+</para>
+<para lang="en">
+the "rss" extension MIME type has been changed to "application/rss+xml".
+</para>
+</change>
+
+<change type="change">
+<para lang="ru">
+теперь директива "gzip_vary on" выдаёт строку
+<nobr>"Vary: Accept-Encoding"</nobr>
+в заголовке ответа и для несжатых ответов.
+</para>
+<para lang="en">
+now the "gzip_vary" directive turned on issues
+a <nobr>"Vary: Accept-Encoding"</nobr>
+header line for uncompressed responses too.
+</para>
+</change>
+
+<change type="feature">
+<para lang="ru">
+теперь при использовании протокола "https://" в директиве rewrite
+автоматически делается редирект.
+</para>
+<para lang="en">
+now the "rewrite" directive does a redirect automatically
+if the "https://" protocol is used.
+</para>
+</change>
+
+<change type="bugfix">
+<para lang="ru">
+директива proxy_pass не работала с протоколом HTTPS;
+ошибка появилась в 0.6.9.
+</para>
+<para lang="en">
+the "proxy_pass" directive did not work with the HTTPS protocol;
+the bug had appeared in 0.6.9.
+</para>
+</change>
+
+</changes>
+
+
 <changes ver="0.7.2" date="16.06.2008">
 
 <change type="feature">
@@ -49,7 +98,7 @@ Thanks to Manlio Perillo.
 <para lang="en">
 after changing URI via a "rewrite" directive nginx did not search
 a new location;
-bug appeared in 0.7.1.<br/>
+the bug had appeared in 0.7.1.<br/>
 Thanks to Maxim Dounin.
 </para>
 </change>
@@ -61,7 +110,7 @@ nginx не собирался без библиотеки PCRE;
 </para>
 <para lang="en">
 nginx could not be built without PCRE library;
-bug appeared in 0.7.1.
+the bug had appeared in 0.7.1.
 </para>
 </change>
 
@@ -237,7 +286,7 @@ nginx не обрабатывал ответ FastCGI-сервера, если строка заголовка ответ была
 <para lang="en">
 nginx did not process FastCGI response
 if header was at the end of FastCGI record;
-bug appeared in 0.6.2.<br/>
+the bug had appeared in 0.6.2.<br/>
 Thanks to Sergey Serov.
 </para>
 </change>
@@ -325,7 +374,7 @@ nginx не собирался под OpenBSD;
 </para>
 <para lang="en">
 nginx could not be built on OpenBSD;
-bug appeared in 0.6.15.
+the bug had appeared in 0.6.15.
 </para>
 </change>
 
@@ -350,7 +399,7 @@ the ngx_google_perftools_module.
 </para>
 <para lang="en">
 the ngx_http_perl_module could not be built on 64-bit platforms;
-bug appeared in 0.6.27.
+the bug had appeared in 0.6.27.
 </para>
 </change>
 
@@ -366,7 +415,7 @@ bug appeared in 0.6.27.
 </para>
 <para lang="en">
 the rtsig method could not be built;
-bug appeared in 0.6.27.
+the bug had appeared in 0.6.27.
 </para>
 </change>
 
@@ -608,7 +657,7 @@ nginx выдавал ошибочное сообщение "SSL_shutdown() failed (SSL: )";
 </para>
 <para lang="en">
 nginx issued the bogus error message "SSL_shutdown() failed (SSL: )";
-bug appeared in 0.6.23.
+the bug had appeared in 0.6.23.
 </para>
 </change>
 
@@ -619,7 +668,7 @@ bug appeared in 0.6.23.
 </para>
 <para lang="en">
 in HTTPS mode requests might fail with the "bad write retry" error;
-bug appeared in 0.6.23.
+the bug had appeared in 0.6.23.
 </para>
 </change>
 
@@ -696,7 +745,7 @@ ngx_http_dav_module;
 </para>
 <para lang="en">
 the ngx_http_gzip_static_module did not allow the ngx_http_dav_module to work;
-bug appeared in 0.6.23.
+the bug had appeared in 0.6.23.
 </para>
 </change>
 
@@ -718,7 +767,7 @@ nginx не собирался без библиотеки PCRE;
 </para>
 <para lang="en">
 nginx could not be built without PCRE library;
-bug appeared in 0.6.23.
+the bug had appeared in 0.6.23.
 </para>
 </change>
 
@@ -733,7 +782,7 @@ bug appeared in 0.6.23.
 </para>
 <para lang="en">
 a segmentation fault might occur in worker process if HTTPS was used;
-bug appeared in 0.6.23.
+the bug had appeared in 0.6.23.
 </para>
 </change>
 
@@ -872,7 +921,7 @@ Thanks to Oleg Motienko.
 </para>
 <para lang="en">
 in HTTPS mode requests might fail with the "bad write retry" error;
-bug appeared in 0.5.13.
+the bug had appeared in 0.5.13.
 </para>
 </change>
 
@@ -904,7 +953,7 @@ allocated memory.
 if nginx was built with ngx_http_perl_module,
 the perl before 5.8.6 was used, and perl supported threads,
 then during reconfiguration the master process aborted;
-bug appeared in 0.5.9.<br/>
+the bug had appeared in 0.5.9.<br/>
 Thanks to Boris Zhmurov.
 </para>
 </change>
@@ -951,7 +1000,7 @@ Thanks to Olexander Shtepa.
 </para>
 <para lang="en">
 the last address was missed in the $upstream_addr variable;
-bug appeared in 0.6.18.
+the bug had appeared in 0.6.18.
 </para>
 </change>
 
@@ -978,7 +1027,7 @@ the "fastcgi_next_upstream invalid_heade
 <para lang="en">
 a segmentation fault occurred in master process
 if the "fastcgi_catch_stderr" directive was used;
-bug appeared in 0.6.10.<br/>
+the bug had appeared in 0.6.10.<br/>
 Thanks to Manlio Perillo.
 </para>
 </change>
@@ -1009,7 +1058,7 @@ resolver
 <para lang="en">
 a segmentation fault might occur in worker process
 if a "proxy_pass" directive with URI-part was used;
-bug appeared in 0.6.19.
+the bug had appeared in 0.6.19.
 </para>
 </change>
 
@@ -1066,7 +1115,7 @@ then nginx returned usual response.
 <para lang="en">
 a segmentation fault might occur in worker process
 if a "proxy_pass" directive with URI-part was used;
-bug appeared in 0.6.19.
+the bug had appeared in 0.6.19.
 </para>
 </change>
 
@@ -1172,7 +1221,7 @@ Thanks to Alexander V. Inyukhin.
 </para>
 <para lang="en">
 URL double escaping in a redirect of the "msie_refresh" directive;
-bug appeared in 0.6.4.
+the bug had appeared in 0.6.4.
 </para>
 </change>
 
@@ -1240,7 +1289,7 @@ Thanks to Ilya Novikov.
 <para lang="en">
 if the "?" character was in a "error_page" directive, then it was escaped
 in a proxied request;
-bug appeared in 0.6.11.
+the bug had appeared in 0.6.11.
 </para>
 </change>
 
@@ -1338,7 +1387,7 @@ error_page nginx пытался снова прочитать тело запроса;
 <para lang="en">
 if request with request body was redirected using the "error_page" directive,
 then nginx tried to read the request body again;
-bug appeared in 0.6.7.
+the bug had appeared in 0.6.7.
 </para>
 </change>
 
@@ -1351,7 +1400,7 @@ bug appeared in 0.6.7.
 <para lang="en">
 a segmentation fault occurred in worker process
 if no server_name was explicitly defined for server processing request;
-bug appeared in 0.6.7.
+the bug had appeared in 0.6.7.
 </para>
 </change>
 
@@ -1397,7 +1446,7 @@ the "access_log" directive may be used i
 <para lang="en">
 if all upstream servers were failed, then all servers had got weight
 the was equal one until servers became alive;
-bug appeared in 0.6.6.
+the bug had appeared in 0.6.6.
 </para>
 </change>
 
@@ -1454,7 +1503,7 @@ nginx распознавал параметры "close" и "keep-alive" в строке "Connection"
 <para lang="en">
 nginx supported low case only "close" and "keep-alive" values
 in the "Connection" request header line;
-bug appeared in 0.6.11.
+the bug had appeared in 0.6.11.
 </para>
 </change>
 
@@ -1535,7 +1584,7 @@ wildcard в конце имени сервера не работали;
 </para>
 <para lang="en">
 the trailing wildcards did not work;
-bug appeared in 0.6.9.
+the bug had appeared in 0.6.9.
 </para>
 </change>
 
@@ -1607,7 +1656,7 @@ nginx did not support several "Connectio
 <para lang="en">
 if the "max_fails" was set for upstream server, then after first
 failure server weight was always one;
-bug appeared in 0.6.6.
+the bug had appeared in 0.6.6.
 </para>
 </change>
 
@@ -1633,7 +1682,7 @@ directives.
 </para>
 <para lang="en">
 socket leak;
-bug appeared in 0.6.7.
+the bug had appeared in 0.6.7.
 </para>
 </change>
 
@@ -1672,7 +1721,7 @@ if /dev/poll method was used.
 <para lang="en">
 a worker process may got caught in an endless loop,
 if the HTTPS protocol was used;
-bug appeared in 0.6.7.
+the bug had appeared in 0.6.7.
 </para>
 </change>
 
@@ -1703,7 +1752,7 @@ nginx не собирался на amd64;
 </para>
 <para lang="en">
 nginx could not be built on amd64;
-bug appeared in 0.6.8.
+the bug had appeared in 0.6.8.
 </para>
 </change>
 
@@ -1754,7 +1803,7 @@ now nginx escapes "%" in $memcached_key 
 <para lang="en">
 nginx used path relative to configuration prefix for non-absolute
 configuration file path specified in the "-c" key;
-bug appeared in 0.6.6.
+the bug had appeared in 0.6.6.
 </para>
 </change>
 
@@ -1892,7 +1941,7 @@ Thanks to Jiang Hong.
 <para lang="en">
 a worker process may got caught in an endless loop, if a "server" inside
 "upstream" block was marked as "down";
-bug appeared in 0.6.6.
+the bug had appeared in 0.6.6.
 </para>
 </change>
 
@@ -1986,7 +2035,7 @@ nginx не собирался на Solaris/amd64 Sun Studio 11 и более ранними версиями;
 </para>
 <para lang="en">
 fix building on Solaris/amd64 by Sun Studio 11 and early versions;
-bug appeared in 0.6.4.
+the bug had appeared in 0.6.4.
 </para>
 </change>
 
@@ -2183,7 +2232,7 @@ if the eventport method was used.
 <para lang="en">
 the "proxy_ignore_client_abort" and "fastcgi_ignore_client_abort" directives
 did not work;
-bug appeared in 0.5.13.
+the bug had appeared in 0.5.13.
 </para>
 </change>
 
@@ -2277,7 +2326,7 @@ nginx не собирался с параметром --without-http_rewrite_module;
 </para>
 <para lang="en">
 nginx could not be built with the --without-http_rewrite_module parameter;
-bug appeared in 0.5.24.
+the bug had appeared in 0.5.24.
 </para>
 </change>
 
@@ -2304,7 +2353,7 @@ using HTTP/0.9.
 </para>
 <para lang="en">
 a part of response body might be passed uncompressed if gzip was used;
-bug appeared in 0.5.23.
+the bug had appeared in 0.5.23.
 </para>
 </change>
 
@@ -2378,7 +2427,7 @@ in the HTTPS protocol in the "proxy_pass
 </para>
 <para lang="en">
 a big request body might not be passed to backend;
-bug appeared in 0.5.21.
+the bug had appeared in 0.5.21.
 </para>
 </change>
 
@@ -2615,7 +2664,7 @@ a segmentation fault occurred in master 
 after first reconfiguration and receiving any signal
 if nginx was built with ngx_http_perl_module and perl
 did not support multiplicity;
-bug appeared in 0.5.9.
+the bug had appeared in 0.5.9.
 </para>
 </change>
 
@@ -2628,7 +2677,7 @@ bug appeared in 0.5.9.
 <para lang="en">
 if perl did not support multiplicity, then after reconfiguration
 perl code did not work;
-bug appeared in 0.3.38.
+the bug had appeared in 0.3.38.
 </para>
 </change>
 
@@ -2714,7 +2763,7 @@ Thanks to Pavel Yarkovoy.
 a segmentation fault might occur in worker process
 if a charset was set in the "Content-Type" header line and the line
 has trailing ";";
-bug appeared in 0.3.50.
+the bug had appeared in 0.3.50.
 </para>
 </change>
 
@@ -2736,7 +2785,7 @@ nginx не собирался на Solaris без параметра --with-debug;
 </para>
 <para lang="en">
 nginx could not be built on Solaris without the --with-debug option;
-bug appeared in 0.5.15.
+the bug had appeared in 0.5.15.
 </para>
 </change>
 
@@ -2914,7 +2963,7 @@ nginx не собирался на платформах, отличных от i386, amd64, sparc и ppc;
 </para>
 <para lang="en">
 nginx could not be built on platforms different from i386, amd64, sparc and ppc;
-bug appeared in 0.5.8.
+the bug had appeared in 0.5.8.
 </para>
 </change>
 
@@ -2930,7 +2979,7 @@ nginx не собирался на платформах, отличных от i386, amd64, sparc и ppc;
 </para>
 <para lang="en">
 nginx could not be built on platforms different from i386, amd64, sparc и ppc;
-bug appeared in 0.5.8.
+the bug had appeared in 0.5.8.
 </para>
 </change>
 
@@ -2943,7 +2992,7 @@ bug appeared in 0.5.8.
 <para lang="en">
 a segmentation fault might occur in worker process
 if the temporarily files were used while working with FastCGI server;
-bug appeared in 0.5.8.
+the bug had appeared in 0.5.8.
 </para>
 </change>
 
@@ -2990,7 +3039,7 @@ Thanks to Chris McGrath.
 </para>
 <para lang="en">
 the response was incorrect if several ranges were requested;
-bug appeared in 0.5.6.
+the bug had appeared in 0.5.6.
 </para>
 </change>
 
@@ -3042,7 +3091,7 @@ if nginx was built with -O2 optimization
 <para lang="en">
 while online executable file upgrade the new master process did not
 inherit the listening sockets;
-bug appeared in 0.5.9.
+the bug had appeared in 0.5.9.
 </para>
 </change>
 
@@ -3055,7 +3104,7 @@ segmentation fault;
 <para lang="en">
 a segmentation fault might occur in worker process
 if nginx was built with -O2 optimization;
-bug appeared in 0.5.1.
+the bug had appeared in 0.5.1.
 </para>
 </change>
 
@@ -3174,7 +3223,7 @@ send_timeout;
 <para lang="en">
 if the "proxy_buffering off" directive was used and a client connection
 was non-active, then the connection was closed after send timeout;
-bug appeared in 0.4.7.
+the bug had appeared in 0.4.7.
 </para>
 </change>
 
@@ -3441,7 +3490,7 @@ nginx might report about configuration e
 </para>
 <para lang="en">
 a segmentation fault might occur if the $host variable was used;
-bug appeared in 0.4.14.
+the bug had appeared in 0.4.14.
 </para>
 </change>
 
@@ -3494,7 +3543,7 @@ the $r->has_request_body method did not 
 <para lang="en">
 if the "proxy_pass" directive used the name of the "upstream" block,
 then nginx tried to resolve the name;
-bug appeared in 0.5.1.
+the bug had appeared in 0.5.1.
 </para>
 </change>
 
@@ -3521,7 +3570,7 @@ of a request.
 </para>
 <para lang="en">
 for Eudora for Mac;
-bug appeared in 0.4.11.<br/>
+the bug had appeared in 0.4.11.<br/>
 Thanks to Bron Gondwana.
 </para>
 </change>
@@ -3535,7 +3584,7 @@ Thanks to Bron Gondwana.
 <para lang="en">
 if the "upstream" name was used in the "fastcgi_pass", then the message
 "no port in upstream" was issued;
-bug appeared in 0.5.0.
+the bug had appeared in 0.5.0.
 </para>
 </change>
 
@@ -3549,7 +3598,7 @@ bug appeared in 0.5.0.
 <para lang="en">
 if the "proxy_pass" and "fastcgi_pass" directives used the same servers but
 different ports, then these directives uses the first described port;
-bug appeared in 0.5.0.
+the bug had appeared in 0.5.0.
 </para>
 </change>
 
@@ -3562,7 +3611,7 @@ bug appeared in 0.5.0.
 <para lang="en">
 if the "proxy_pass" and "fastcgi_pass" directives used the unix domain sockets,
 then these directives used first described socket;
-bug appeared in 0.5.0.
+the bug had appeared in 0.5.0.
 </para>
 </change>
 
@@ -3658,7 +3707,7 @@ nginx не собирался на 64-битных платформах;
 </para>
 <para lang="en">
 nginx could not be built on 64-bit platforms;
-bug appeared in 0.4.14.
+the bug had appeared in 0.4.14.
 </para>
 </change>
 
@@ -3692,7 +3741,7 @@ ngx_http_perl_module не работал с перлом, собранным с поддержкой потоков;
 </para>
 <para lang="en">
 ngx_http_perl_module did not work with perl built with the threads support;
-bug appeared in 0.3.38.
+the bug had appeared in 0.3.38.
 </para>
 </change>
 
@@ -3810,7 +3859,7 @@ and the deferred accept() were used.
 </para>
 <para lang="en">
 a charset could not be set for ngx_http_autoindex_module responses;
-bug appeared in 0.3.50.
+the bug had appeared in 0.3.50.
 </para>
 </change>
 
@@ -3841,7 +3890,7 @@ 50-й подзапрос в SSI ответе не работал;
 </para>
 <para lang="en">
 the 50th subrequest in SSI response did not work;
-bug appeared in 0.3.50.
+the bug had appeared in 0.3.50.
 </para>
 </change>
 
@@ -3911,7 +3960,7 @@ the ngx_http_perl_module supports the $r
 <para lang="en">
 if the APOP was enabled in the POP3 proxy, then the USER/PASS commands
 might not work;
-bug appeared in 0.4.10.
+the bug had appeared in 0.4.10.
 </para>
 </change>
 
@@ -3958,7 +4007,7 @@ in the "map" directive.
 </para>
 <para lang="en">
 the ngx_http_flv_module did not support the byte ranges for full responses;
-bug appeared in 0.4.7.
+the bug had appeared in 0.4.7.
 </para>
 </change>
 
@@ -3969,7 +4018,7 @@ nginx не собирался на Debian amd64;
 </para>
 <para lang="en">
 nginx could not be built on Debian amd64;
-bug appeared in 0.4.9.
+the bug had appeared in 0.4.9.
 </para>
 </change>
 
@@ -4122,7 +4171,7 @@ the $r->headers_out("Content-Length", ..
 <para lang="en">
 after redirecting error by an "error_page" directive
 any ngx_http_rewrite_module directive returned this error code;
-bug appeared in 0.4.4.
+the bug had appeared in 0.4.4.
 </para>
 </change>
 
@@ -4138,7 +4187,7 @@ nginx не собирался на Linux и Solaris;
 </para>
 <para lang="en">
 nginx could not be built on Linux and Solaris;
-bug appeared in 0.4.4.
+the bug had appeared in 0.4.4.
 </para>
 </change>
 
@@ -4260,7 +4309,7 @@ unix domain сокет;
 <para lang="en">
 a segmentation fault occurred if an unix domain socket was used in
 a "proxy_pass" directive;
-bug appeared in 0.3.47.
+the bug had appeared in 0.3.47.
 </para>
 </change>
 
@@ -4295,7 +4344,7 @@ of the Sun Studio PAUSE hardware capabil
 </para>
 <para lang="en">
 the O_NOATIME flag support on Linux was canceled;
-bug appeared in 0.4.1.
+the bug had appeared in 0.4.1.
 </para>
 </change>
 
@@ -4400,7 +4449,7 @@ the "ssi" directive is available inside 
 <para lang="en">
 a segmentation fault occurred if there was an "index" directive with
 variables and the first index name was without variables;
-bug appeared in 0.1.29.
+the bug had appeared in 0.1.29.
 </para>
 </change>
 
@@ -4460,7 +4509,7 @@ had the captured escaped symbols from or
 <para lang="en">
 a worker process may got caught in an endless loop
 while an error redirection;
-bug appeared in 0.3.59.
+the bug had appeared in 0.3.59.
 </para>
 </change>
 
@@ -4496,7 +4545,7 @@ the "dav_access" directive did not suppo
 <para lang="en">
 the "error_page" directive did not changes the "Content-Type" header line
 after the "X-Accel-Redirect" was used;
-bug appeared in 0.3.58.
+the bug had appeared in 0.3.58.
 </para>
 </change>
 
@@ -4730,7 +4779,7 @@ was used and nginx switched to a next up
 <para lang="en">
 on some condition while reconfiguration character codes
 inside the "charset_map" may be treated invalid;
-bug appeared in 0.3.50.
+the bug had appeared in 0.3.50.
 </para>
 </change>
 
@@ -4797,7 +4846,7 @@ nginx не собирался на платформе amd64;
 </para>
 <para lang="en">
 nginx could not be built on amd64 platform;
-bug appeared in 0.3.53.
+the bug had appeared in 0.3.53.
 </para>
 </change>
 
@@ -4897,7 +4946,7 @@ to the 0.3.40 version state: the module 
 </para>
 <para lang="en">
 the worker process may got caught in an endless loop if the limit rate was used;
-bug appeared in 0.3.37.
+the bug had appeared in 0.3.37.
 </para>
 </change>
 
@@ -4910,7 +4959,7 @@ bug appeared in 0.3.37.
 <para lang="en">
 ngx_http_charset_module logged "unknown charset" alert, even if the recoding
 was not needed;
-bug appeared in 0.3.50.
+the bug had appeared in 0.3.50.
 </para>
 </change>
 
@@ -4937,7 +4986,7 @@ was not removed.
 </para>
 <para lang="en">
 the "&lt;" symbols might disappeared some conditions in the SSI;
-bug appeared in 0.3.50.
+the bug had appeared in 0.3.50.
 </para>
 </change>
 
@@ -5081,7 +5130,7 @@ X-Accel-Redirect, и у которых метод не равен HEAD;
 the internal redirect always transform client's HTTP method to GET,
 now the transformation is made for the "X-Accel-Redirect" redirects only
 and if the method is not HEAD;
-bug appeared in 0.3.42.
+the bug had appeared in 0.3.42.
 </para>
 </change>
 
@@ -5093,7 +5142,7 @@ bug appeared in 0.3.42.
 <para lang="en">
 the ngx_http_perl_module could not be built, if the perl was built
 with the threads support;
-bug appeared in 0.3.46.
+the bug had appeared in 0.3.46.
 </para>
 </change>
 
@@ -5440,7 +5489,7 @@ SSI-commands, then the "unknown variable
 <para lang="en">
 the active connection counter increased on the exceeding of the connection
 limit specified by the "worker_connections" directive;
-bug appeared in 0.2.0.
+the bug had appeared in 0.2.0.
 </para>
 </change>
 
@@ -5451,7 +5500,7 @@ bug appeared in 0.2.0.
 </para>
 <para lang="en">
 the limit rate might not work on some condition;
-bug appeared in 0.3.38.
+the bug had appeared in 0.3.38.
 </para>
 </change>
 
@@ -5687,7 +5736,7 @@ accept-фильтр и TCP_DEFER_ACCEPT устанавливались только для первой
 <para lang="en">
 the accept-filter and the TCP_DEFER_ACCEPT option were set for first "listen"
 directive only;
-bug appeared in 0.3.31.
+the bug had appeared in 0.3.31.
 </para>
 </change>
 
@@ -5761,7 +5810,7 @@ in the "post_action" directive.
 </para>
 <para lang="en">
 the debug logging on startup and reconfiguration time was removed;
-bug appeared in 0.3.31.
+the bug had appeared in 0.3.31.
 </para>
 </change>
 
@@ -5820,7 +5869,7 @@ Thanks to Andrei Nigmatulin.
 if there were several "listen" directives listening one various addresses
 inside one server, then server names like "*.domain.tld" worked for first
 address only;
-bug appeared in 0.3.18.
+the bug had appeared in 0.3.18.
 </para>
 </change>
 
@@ -5875,7 +5924,7 @@ nginx не собирался на i386 платформе, если использовался PIC;
 </para>
 <para lang="en">
 nginx could not be built on i386 platform, if the PIC was used;
-bug appeared in 0.3.27.
+the bug had appeared in 0.3.27.
 </para>
 </change>
 
@@ -6108,7 +6157,7 @@ segmentation fault;
 <para lang="en">
 the segmentation fault was occurred on start or while reconfiguration
 if there was invalid configuration;
-bug appeared in 0.3.24.
+the bug had appeared in 0.3.24.
 </para>
 </change>
 
@@ -6163,7 +6212,7 @@ the first "proxy_redirect" directive was
 <para lang="en">
 on 64-bit platforms segmentation fault may occurred on start
 if the many names were used in the "server_name" directives;
-bug appeared in 0.3.18.
+the bug had appeared in 0.3.18.
 </para>
 </change>
 
@@ -6231,7 +6280,7 @@ the method $r->query_string of ngx_http_
 <para lang="en">
 segmentation fault was occurred if the "none" or "blocked" values was
 specified in the "valid_referers" directive;
-bug appeared in 0.3.18.
+the bug had appeared in 0.3.18.
 </para>
 </change>
 
@@ -6392,7 +6441,7 @@ some ".domain.tld" names incorrectly pro
 </para>
 <para lang="en">
 segmentation fault was occurred if configuration file did not exist;
-bug appeared in 0.3.12.
+the bug had appeared in 0.3.12.
 </para>
 </change>
 
@@ -6403,7 +6452,7 @@ bug appeared in 0.3.12.
 </para>
 <para lang="en">
 on 64-bit platforms segmentation fault may occurred on start;
-bug appeared in 0.3.16.
+the bug had appeared in 0.3.16.
 </para>
 </change>
 
@@ -6437,7 +6486,7 @@ the "map" directive supports domain name
 </para>
 <para lang="en">
 the timeouts were not used in SSL handshake;
-bug appeared in 0.2.4.
+the bug had appeared in 0.2.4.
 </para>
 </change>
 
@@ -6532,7 +6581,7 @@ nginx не закрывал соединения с IMAP/POP3 бэкендом при использовании SSL
 <para lang="en">
 nginx did not close connection to IMAP/POP3 backend for the SSL
 connections;
-bug appeared in 0.3.13.<br/>
+the bug had appeared in 0.3.13.<br/>
 Thanks to Rob Mueller.
 </para>
 </change>
@@ -6544,7 +6593,7 @@ segmentation fault мог произойти во время SSL shutdown;
 </para>
 <para lang="en">
 segmentation fault may occurred in at SSL shutdown;
-bug appeared in 0.3.13.
+the bug had appeared in 0.3.13.
 </para>
 </change>
 
@@ -6594,7 +6643,7 @@ quit and active "debug_points" directive
 </para>
 <para lang="en">
 in the 304 response the body was transferred;
-bug appeared in 0.3.13.
+the bug had appeared in 0.3.13.
 </para>
 </change>
 
@@ -6648,7 +6697,7 @@ to FastCGI-server via the unix domain so
 </para>
 <para lang="en">
 the "auth_basic" directive did not disable the authorization;
-bug appeared in 0.3.11.
+the bug had appeared in 0.3.11.
 </para>
 </change>
 
@@ -6715,7 +6764,7 @@ the "proxy_buffering" directive.
 </para>
 <para lang="en">
 the changes in accept mutex  handling when the "rtsig" method was used;
-bug appeared in 0.3.0.
+the bug had appeared in 0.3.0.
 </para>
 </change>
 
@@ -6751,7 +6800,7 @@ the "Basic realm" text.
 <para lang="en">
 if the "combined" format was explicitly specified in the "access_log" directive,
 then the empty lines was written to the log;
-bug appeared in 0.3.8.
+the bug had appeared in 0.3.8.
 </para>
 </change>
 
@@ -6787,7 +6836,7 @@ nginx не передавал при проксировании тело запроса и строки заголовка клиента;
 </para>
 <para lang="en">
 nginx did not pass the client request headers and body while proxying;
-bug appeared in 0.3.10.
+the bug had appeared in 0.3.10.
 </para>
 </change>
 
@@ -6923,7 +6972,7 @@ nginx считал небезопасными URI, в которых между двумя слэшами
 </para>
 <para lang="en">
 nginx considered URI as unsafe if two any symbols was between two slashes;
-bug appeared in 0.3.8.
+the bug had appeared in 0.3.8.
 </para>
 </change>
 
@@ -7057,7 +7106,7 @@ the worker processes did not flush the b
 if the request URI was changes by the "rewrite" directive and the request
 was proxied in location given by regular expression, then the incorrect
 request was transferred to backend;
-bug appeared in 0.2.6.
+the bug had appeared in 0.2.6.
 </para>
 </change>
 
@@ -7122,7 +7171,7 @@ nginx не собирался на платформах, отличных от i386, amd64, sparc и ppc;
 </para>
 <para lang="en">
 nginx could not be built on platforms different from i386, amd64, sparc и ppc;
-bug appeared in 0.3.2.
+the bug had appeared in 0.3.2.
 </para>
 </change>
 
@@ -7158,7 +7207,7 @@ nginx не слушал на 80 порту;
 <para lang="en">
 if at least in one server was no the "listen" directive, then nginx did not
 listen on the 80 port;
-bug appeared in 0.3.3.
+the bug had appeared in 0.3.3.
 </para>
 </change>
 
@@ -7186,7 +7235,7 @@ segmentation fault;
 <para lang="en">
 the segmentation fault may occurred if the IMAP/POP3 login was changed
 by authorization server;
-bug appeared in 0.2.2.
+the bug had appeared in 0.2.2.
 </para>
 </change>
 
@@ -7197,7 +7246,7 @@ accept mutex не работал, все соединения обрабатывались одним рабочим процессом;
 </para>
 <para lang="en">
 the accept mutex did not work and all connections were handled by one process;
-bug appeared in 0.3.3.
+the bug had appeared in 0.3.3.
 </para>
 </change>
 
@@ -7224,7 +7273,7 @@ nginx не собирался на Linux 2.4+ и MacOS X;
 </para>
 <para lang="en">
 nginx could not be built on Linux 2.4+ and MacOS X;
-bug appeared in 0.3.3.
+the bug had appeared in 0.3.3.
 </para>
 </change>
 
@@ -7293,7 +7342,7 @@ after the -HUP signal nginx left an open
 <para lang="en">
 the mime type may be incorrectly set to default value for index file with
 variable in the name;
-bug appeared in 0.3.0.
+the bug had appeared in 0.3.0.
 </para>
 </change>
 
@@ -7403,7 +7452,7 @@ directives.
 <para lang="en">
 the segmentation fault occurred when the signal queue overflowed
 if the "rtsig" method was used;
-bug appeared in 0.2.0.
+the bug had appeared in 0.2.0.
 </para>
 </change>
 
@@ -7503,7 +7552,7 @@ new configuration, then the ngx_http_rew
 if the "set" directive set the ngx_http_geo_module variable in some
 configuration part, the this variable was not available in other
 configuration parts and the "using uninitialized variable" error was occurred;
-bug appeared in 0.2.2.
+the bug had appeared in 0.2.2.
 </para>
 </change>
 
@@ -7577,7 +7626,7 @@ in the "if" command.
 </para>
 <para lang="en">
 in proxying location without trailing slash;
-bug appeared in 0.1.44.
+the bug had appeared in 0.1.44.
 </para>
 </change>
 
@@ -7588,7 +7637,7 @@ bug appeared in 0.1.44.
 </para>
 <para lang="en">
 the segmentation fault may occurred if the "rtsig" method was used;
-bug appeared in 0.2.0.
+the bug had appeared in 0.2.0.
 </para>
 </change>
 
@@ -7604,7 +7653,7 @@ nginx не собирался без параметра --with-debug;
 </para>
 <para lang="en">
 nginx could not be built without the --with-debug option;
-bug appeared in 0.2.2.
+the bug had appeared in 0.2.2.
 </para>
 </change>
 
@@ -7696,7 +7745,7 @@ the export versions of MSIE 5.x could no
 <para lang="en">
 if all backend using in load-balancing failed after one error, then
 nginx may got caught in an endless loop;
-bug appeared in 0.2.0.
+the bug had appeared in 0.2.0.
 </para>
 </change>
 
@@ -7956,7 +8005,7 @@ the FastCGI parameters with the empty va
 <para lang="en">
 the segmentation fault may occurred if there were errors while
 working with proxied or FastCGI server;
-in the proxied mode the bug appeared in 0.1.29.
+in the proxied mode the the bug had appeared in 0.1.29.
 </para>
 </change>
 
@@ -7973,7 +8022,7 @@ segmentation fault или рабочий процесс мог зациклится;
 the segmentation fault occurred or the worker process may got caught
 in an endless loop if the proxied or FastCGI server sent the "Cache-Control"
 header line and the "expires" directive was used;
-in the proxied mode the bug appeared in 0.1.29.
+in the proxied mode the the bug had appeared in 0.1.29.
 </para>
 </change>
 
@@ -8002,7 +8051,7 @@ in the ngx_http_proxy_module.
 </para>
 <para lang="en">
 the "limit_rate" directive did not work inside the "if" block;
-bug appeared in 0.1.38.
+the bug had appeared in 0.1.38.
 </para>
 </change>
 
@@ -8046,7 +8095,7 @@ did not logged in the error log.
 <para lang="en">
 the "Set-Cookie" header line was not transferred when the "X-Accel-Redirect"
 was used;
-bug appeared in 0.1.39.
+the bug had appeared in 0.1.39.
 </para>
 </change>
 
@@ -8121,7 +8170,7 @@ the 401 response code redirecting.
 <para lang="en">
 the ngx_http_proxy_module and ngx_http_fastcgi_module may close
 a connection before anything was transferred to a client;
-bug appeared in 0.1.38.
+the bug had appeared in 0.1.38.
 </para>
 </change>
 
@@ -8154,7 +8203,7 @@ the "include virtual" command.
 <para lang="en">
 if the backend response had the "Location" header line and nginx
 should not rewrite this line, then the 500 code response body was transferred;
-bug appeared in 0.1.29.
+the bug had appeared in 0.1.29.
 </para>
 </change>
 
@@ -8167,7 +8216,7 @@ bug appeared in 0.1.29.
 <para lang="en">
 some directives of the ngx_http_proxy_module and ngx_http_fastcgi_module
 were not inherited from the server to the location level;
-bug appeared in 0.1.29.
+the bug had appeared in 0.1.29.
 </para>
 </change>
 
@@ -8187,7 +8236,7 @@ the ngx_http_ssl_module did not support 
 </para>
 <para lang="en">
 the ngx_http_autoindex_module did not show correctly the long file names;
-bug appeared in 0.1.38.
+the bug had appeared in 0.1.38.
 </para>
 </change>
 
@@ -8283,7 +8332,7 @@ nginx считал ответ неверным;
 <para lang="en">
 nginx treated the backend response as invalid if the status line in the
 header was transferred in two packets;
-bug appeared in 0.1.29.
+the bug had appeared in 0.1.29.
 </para>
 </change>
 
@@ -8466,7 +8515,7 @@ the "port_in_redirect" directive.
 <para lang="en">
 the segmentation fault was occurred if the backend response header was in
 several packets;
-bug appeared in 0.1.29.
+the bug had appeared in 0.1.29.
 </para>
 </change>
 
@@ -8502,7 +8551,7 @@ nginx возвращал ошибку 400 на запросы вида
 <para lang="en">
 nginx returned the 400 response on requests like
 <nobr>"GET http://www.domain.com/uri HTTP/1.0"</nobr>;
-bug appeared in 0.1.28.
+the bug had appeared in 0.1.28.
 </para>
 </change>
 
@@ -8561,7 +8610,7 @@ nginx не собирался с параметром --without-pcre;
 </para>
 <para lang="en">
 nginx could not be built with the --without-pcre parameter;
-bug appeared in 0.1.29.
+the bug had appeared in 0.1.29.
 </para>
 </change>
 
@@ -8608,7 +8657,7 @@ the 500 error code was returned.
 </para>
 <para lang="en">
 the arguments were omitted in the redirects, issued by the "rewrite" directive;
-bug appeared in 0.1.29.
+the bug had appeared in 0.1.29.
 </para>
 </change>
 
@@ -8681,7 +8730,7 @@ errors while using SSI and gzipping.
 </para>
 <para lang="en">
 the redirect with the 301 code was transferred without response body;
-bug appeared in 0.1.30.
+the bug had appeared in 0.1.30.
 </para>
 </change>
 
@@ -8717,7 +8766,7 @@ FastCGI сервера была равна 500 байт, то nginx возвращал код ответа 500;
 <para lang="en">
 if the length of the response part received at once from proxied
 or FastCGI server was equal to 500, then nginx returns the 500 response code;
-in proxy mode the bug appeared in 0.1.29 only.
+in proxy mode the the bug had appeared in 0.1.29 only.
 </para>
 </change>
 
@@ -9000,7 +9049,7 @@ segmentation fault;
 <para lang="en">
 the segmentation fault was occurred if the backend sent an invalid line
 in response header;
-bug appeared in 0.1.26.
+the bug had appeared in 0.1.26.
 </para>
 </change>
 
@@ -9391,7 +9440,7 @@ nginx не собирался на платформах, отличных от i386, amd64, sparc и ppc;
 </para>
 <para lang="en">
 nginx could not be built on platforms different from i386, amd64, sparc и ppc;
-bug appeared in 0.1.22.
+the bug had appeared in 0.1.22.
 </para>
 </change>
 
@@ -9441,7 +9490,7 @@ statistics if the proxying or FastCGI se
 </para>
 <para lang="en">
 the installation paths were incorrectly quoted on Linux and Solaris;
-bug appeared in 0.1.21.
+the bug had appeared in 0.1.21.
 </para>
 </change>
 
@@ -9720,7 +9769,7 @@ then the segmentation fault occurred.
 <para lang="en">
 if in a proxied "Location" header was a relative URL,
 then a host name and a slash were added to them;
-bug appeared in 0.1.14.
+the bug had appeared in 0.1.14.
 </para>
 </change>
 
@@ -9806,7 +9855,7 @@ the rewrite directive supports the argum
 <para lang="en">
 the response code 400 was returned for the POST request with the
 "Content-Length: 0" header;
-bug appeared in 0.1.14.
+the bug had appeared in 0.1.14.
 </para>
 </change>
 
@@ -9879,7 +9928,7 @@ the regular expressions in locations.
 <para lang="en">
 the directive <nobr>"proxy_preserve_host  on"</nobr> adds port 80
 to the "Host" headers, if upstream listen on port 80;
-bug appeared in 0.1.14.
+the bug had appeared in 0.1.14.
 </para>
 </change>
 
@@ -9980,7 +10029,7 @@ and fastcgi_x_powered_by.
 </para>
 <para lang="en">
 the "[alert] zero size buf" error;
-bug appeared in 0.1.3.
+the bug had appeared in 0.1.3.
 </para>
 </change>
 
@@ -10249,7 +10298,7 @@ the double slashes in "://" in the URI w
 <para lang="en">
 if the request without arguments contains "//", "/./", "/../" or "%XX"
 then the lost character in the request line was lost;
-bug appeared in 0.1.9.
+the bug had appeared in 0.1.9.
 </para>
 </change>
 
@@ -10306,7 +10355,7 @@ sendfile64().
 <para lang="en">
 while the build configuration on Linux the --with-poll_module parameter
 was required;
-bug appeared in 0.1.8.
+the bug had appeared in 0.1.8.
 </para>
 </change>
 
@@ -10356,7 +10405,7 @@ the proxy_max_temp_file_size directive.
 <para lang="en">
 on FreeBSD the segmentation fault may occur if the size of the transferred
 file was changed;
-bug appeared in 0.1.5.
+the bug had appeared in 0.1.5.
 </para>
 </change>
 
@@ -10550,7 +10599,7 @@ the portability improvements.
 <para lang="en">
 if configuration file was set in command line, the reconfiguration
 was impossible;
-bug appeared in 0.1.1.
+the bug had appeared in 0.1.1.
 </para>
 </change>
 
@@ -10573,7 +10622,7 @@ proxy module may get caught in an endles
 <para lang="en">
 with sendfile the response was not recoded according to the charset
 module directives;
-bug appeared in 0.1.1.
+the bug had appeared in 0.1.1.
 </para>
 </change>