--- a/xml/en/docs/http/ngx_http_access_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_access_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -16,7 +16,7 @@
 
 <para>
 The <literal>ngx_http_access_module</literal> module allows
-to limit access to certain client addresses.
+limiting access to certain client addresses.
 </para>
 
 <para>
@@ -45,7 +45,7 @@
 
 <para>
 The rules are checked in sequence until the first match is found.
-In this example, an access is allowed only for IPv4 networks
+In this example, access is allowed only for IPv4 networks
 <literal>10.1.1.0/16</literal> and <literal>192.168.1.0/24</literal>
 excluding the address <literal>192.168.1.1</literal>,
 and for IPv6 network <literal>2001:0db8::/32</literal>.

--- a/xml/en/docs/http/ngx_http_addition_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_addition_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -16,7 +16,7 @@
 
 <para>
 The <literal>ngx_http_addition_module</literal> module is a filter
-that adds a text before and after a response.
+that adds text before and after a response.
 This module is not built by default, it should be enabled with the
 <literal>--with-http_addition_module</literal>
 configuration parameter.
@@ -49,7 +49,7 @@
 <context>location</context>
 
 <para>
-Adds a text returned as a result of processing a given subrequest,
+Adds the text returned as a result of processing a given subrequest
 before the response body.
 An empty string (<literal>""</literal>) as a parameter cancels addition
 inherited from the previous configuration level.
@@ -66,7 +66,7 @@
 <context>location</context>
 
 <para>
-Adds a text returned as a result of processing a given subrequest,
+Adds the text returned as a result of processing a given subrequest
 after the response body.
 An empty string (<literal>""</literal>) as a parameter cancels addition
 inherited from the previous configuration level.
@@ -84,7 +84,7 @@
 <appeared-in>0.7.9</appeared-in>
 
 <para>
-Allows to add text in responses with the specified MIME types,
+Allows adding text in responses with the specified MIME types,
 in addition to “<literal>text/html</literal>”.
 The special value “<literal>*</literal>” matches any MIME type (0.8.29).
 </para>

--- a/xml/en/docs/http/ngx_http_auth_basic_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_auth_basic_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -16,7 +16,7 @@
 
 <para>
 The <literal>ngx_http_auth_basic_module</literal> module allows
-to limit access to resources by validating the user name and password
+limiting access to resources by validating the user name and password
 using the “HTTP Basic Authentication” protocol.
 </para>
 
@@ -58,8 +58,8 @@
 Enables validation of user name and password using the
 “HTTP Basic Authentication” protocol.
 The specified parameter is used as a <value>realm</value>.
-Value of the parameter can contain variables (1.3.10, 1.2.7).
-The special value <literal>off</literal> allows to cancel the effect
+Parameter value can contain variables (1.3.10, 1.2.7).
+The special value <literal>off</literal> allows cancelling the effect
 of the <literal>auth_basic</literal> directive
 inherited from the previous configuration level.
 </para>
@@ -113,7 +113,7 @@
 <note>
 Support for <literal>SHA</literal> scheme was added only to aid
 in migration from other web servers.
-It should not be used for new passwords since unsalted SHA-1 hashing
+It should not be used for new passwords, since unsalted SHA-1 hashing
 that it employs is vulnerable to
 <link url="http://en.wikipedia.org/wiki/Rainbow_attack">rainbow table</link>
 attacks.

--- a/xml/en/docs/http/ngx_http_autoindex_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_autoindex_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -21,7 +21,7 @@
 Usually a request is passed to the <literal>ngx_http_autoindex_module</literal>
 module when the
 <link doc="ngx_http_index_module.xml">ngx_http_index_module</link> module
-could not find an index file.
+cannot find an index file.
 </para>
 
 </section>
@@ -50,7 +50,7 @@
 <context>location</context>
 
 <para>
-Enables or disables a directory listing output.
+Enables or disables the directory listing output.
 </para>
 
 </directive>
@@ -64,8 +64,8 @@
 <context>location</context>
 
 <para>
-Specifies whether file sizes in the directory listing should be
-output exactly, or rounded to kilobytes, megabytes, and gigabytes.
+Specifies whether exact file sizes should be output in the directory listing,
+or rather rounded to kilobytes, megabytes, and gigabytes.
 </para>
 
 </directive>
@@ -80,7 +80,7 @@
 
 <para>
 Specifies whether times in the directory listing should be
-output in a local time zone or UTC.
+output in the local time zone or UTC.
 </para>
 
 </directive>

--- a/xml/en/docs/http/ngx_http_browser_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_browser_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -22,13 +22,13 @@
 
 <tag-name><var>$modern_browser</var></tag-name>
 <tag-desc>
-equals to the value set by the <link id="modern_browser_value"/> directive,
+equals the value set by the <link id="modern_browser_value"/> directive,
 if a browser was identified as modern;
 </tag-desc>
 
 <tag-name><var>$ancient_browser</var></tag-name>
 <tag-desc>
-equals to the value set by the <link id="ancient_browser_value"/> directive,
+equals the value set by the <link id="ancient_browser_value"/> directive,
 if a browser was identified as ancient;
 </tag-desc>
 
@@ -93,7 +93,7 @@
 
 <para>
 If any of the specified substrings is found in the <header>User-Agent</header>
-request header field, a browser will be considered ancient.
+request header field, the browser will be considered ancient.
 The special string “<literal>netscape4</literal>” corresponds to the
 regular expression “<literal>^Mozilla/[1-4]</literal>”.
 </para>
@@ -144,7 +144,7 @@
 directives.
 Otherwise such a browser is considered ancient.
 If a request does not provide the <header>User-Agent</header> field
-in the header, a browser is treated as not being listed.
+in the header, the browser is treated as not being listed.
 </para>
 
 </directive>

--- a/xml/en/docs/http/ngx_http_charset_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_charset_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -85,7 +85,7 @@
 <link id="charset_map"/>, <link id="charset"/>, or
 <link id="source_charset"/> directives.
 For <literal>utf-8</literal>, <literal>windows-1251</literal>, and
-<literal>koi8-r</literal> charsets it is sufficient to include the files
+<literal>koi8-r</literal> charsets, it is sufficient to include the files
 <path>conf/koi-win</path>, <path>conf/koi-utf</path>, and
 <path>conf/win-utf</path> into configuration.
 For other charsets, simply making a fictitious conversion table works,
@@ -96,9 +96,9 @@
 </para>
 
 <para>
-In addition, charset can also be set in the
+In addition, a charset can be set in the
 <header>X-Accel-Charset</header> response header field.
-This ability can be disabled using the
+This capability can be disabled using the
 <link doc="ngx_http_proxy_module.xml" id="proxy_ignore_headers"/>
 and
 <link doc="ngx_http_fastcgi_module.xml" id="fastcgi_ignore_headers"/>
@@ -194,16 +194,16 @@
 <context>if in location</context>
 
 <para>
-Determines if a conversion should be performed for answers
-received from a proxied or FastCGI server,
-if the answers already carry a charset in the <header>Content-Type</header>
+Determines whether a conversion should be performed for answers
+received from a proxied or FastCGI server
+when the answers already carry a charset in the <header>Content-Type</header>
 response header field.
 If conversion is enabled, a charset specified in the received
 response is used as a source charset.
 <note>
-It should be noted that if a response was received in a subrequest
-then conversion from the response charset to the main request charset
-is always performed regardless of the <literal>override_charset</literal>
+It should be noted that if a response is received in a subrequest
+then the conversion from the response charset to the main request charset
+is always performed, regardless of the <literal>override_charset</literal>
 directive setting.
 </note>
 </para>

--- a/xml/en/docs/http/ngx_http_core_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_core_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -317,7 +317,7 @@
 
 <para>
 Defines a timeout for reading client request body.
-The timeout is only set for a period between two successive read operations,
+The timeout is set only for a period between two successive read operations,
 not for the transmission of the whole request body.
 If a client does not transmit anything within this time, the
 <http-status code="408" text="Request Time-out"/>
@@ -411,7 +411,7 @@
 <context>location</context>
 
 <para>
-Defines the default MIME-type of a response.
+Defines the default MIME type of a response.
 Mapping of file name extensions to MIME types can be set
 with the <link id="types"/> directive.
 </para>
@@ -657,7 +657,7 @@
 <context>main</context>
 
 <para>
-Provides a configuration file context in which the HTTP server directives
+Provides the configuration file context in which the HTTP server directives
 are specified.
 </para>
 
@@ -949,7 +949,7 @@
 <para>
 Limits the rate of response transmission to a client.
 The <value>rate</value> is specified in bytes per second.
-The value 0 disables rate limiting.
+The zero value disables rate limiting.
 <!--
 The smaller the rate, the more accurate will be the limitation.
 -->
@@ -1137,8 +1137,8 @@
 <context>server</context>
 
 <para>
-Sets an <value>address</value> and a <value>port</value> for IP,
-or a <value>path</value> for a UNIX-domain socket on which
+Sets the <value>address</value> and <value>port</value> for IP,
+or the <value>path</value> for a UNIX-domain socket on which
 the server will accept requests.
 Both <value>address</value> and <value>port</value>,
 or only <value>address</value> or only <value>port</value> can be specified.
@@ -1285,8 +1285,8 @@
 <literal>listen</literal> directives listens on all addresses
 for the given port (<literal>*:</literal><value>port</value>), nginx
 will <c-func>bind</c-func> only to <literal>*:</literal><value>port</value>.
-It should be noted that in this case the address that accepted the
-connection is determined by a <c-func>getsockname</c-func> system call.
+It should be noted that the <c-func>getsockname</c-func> system call will be
+made in this case to determine the address that accepted the connection.
 If the <literal>backlog</literal>, <literal>rcvbuf</literal>,
 <literal>sndbuf</literal>, <literal>accept_filter</literal>,
 <literal>deferred</literal>, or <literal>so_keepalive</literal> parameters
@@ -2109,7 +2109,7 @@
 
 <para>
 Sets a timeout for transmitting a response to the client.
-A timeout is only set between two successive write operations,
+A timeout is set only between two successive write operations,
 not for the transmission of the whole response.
 If a client does not receive anything within this time,
 a connection is closed.
@@ -2353,7 +2353,7 @@
 <para>
 Sets the bucket size for the server names hash tables.
 The default value depends on the size of the processor’s cache line.
-Details of setting up hash tables are provided in a separate
+The details of setting up hash tables are provided in a separate
 <link doc="../hash.xml">document</link>.
 </para>
 
@@ -2367,7 +2367,7 @@
 
 <para>
 Sets the maximum <value>size</value> of the server names hash tables.
-Details of setting up hash tables are provided in a separate
+The details of setting up hash tables are provided in a separate
 <link doc="../hash.xml">document</link>.
 </para>
 
@@ -2630,7 +2630,7 @@
 <para>
 Sets the bucket size for the types hash tables.
 The default value depends on the size of the processor’s cache line.
-Details of setting up hash tables are provided in a separate
+The details of setting up hash tables are provided in a separate
 <link doc="../hash.xml">document</link>.
 </para>
 
@@ -2646,7 +2646,7 @@
 
 <para>
 Sets the maximum <value>size</value> of the types hash tables.
-Details of setting up hash tables are provided in a separate
+The details of setting up hash tables are provided in a separate
 <link doc="../hash.xml">document</link>.
 </para>
 
@@ -2684,7 +2684,7 @@
 
 <para>
 Sets the bucket size for the variables hash table.
-Details of setting up hash tables are provided in a separate
+The details of setting up hash tables are provided in a separate
 <link doc="../hash.xml">document</link>.
 </para>
 
@@ -2698,7 +2698,7 @@
 
 <para>
 Sets the maximum <value>size</value> of the variables hash table.
-Details of setting up hash tables are provided in a separate
+The details of setting up hash tables are provided in a separate
 <link doc="../hash.xml">document</link>.
 </para>
 

--- a/xml/en/docs/http/ngx_http_dav_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_dav_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -108,14 +108,15 @@
 
 <para>
 A file uploaded with the PUT method is first written to a temporary file,
-then a file is renamed.
-Starting from version 0.8.9 temporary files and the persistent store
-can be put on different file systems but be aware that in this case
-a file is copied across two file systems instead of the cheap rename operation.
+and then the file is renamed.
+Starting from version 0.8.9, temporary files and the persistent store
+can be put on different file systems.
+However, be aware that in this case a file is copied
+across two file systems instead of the cheap renaming operation.
 It is thus recommended that for any given location both saved files and a
-directory holding temporary files set by the
+directory holding temporary files, set by the
 <link doc="ngx_http_core_module.xml" id="client_body_temp_path"/>
-directive are put on the same file system.
+directive, are put on the same file system.
 </para>
 
 <para>
@@ -135,9 +136,9 @@
 <context>location</context>
 
 <para>
-The WebDAV specification only allows to create files in already
+The WebDAV specification only allows creating files in already
 existing directories.
-This directive allows to create all needed intermediate directories.
+This directive allows creating all needed intermediate directories.
 </para>
 
 </directive>
@@ -152,12 +153,13 @@
 
 <para>
 Allows the DELETE method to remove files provided that
-the number of elements in a request path is not less than the specified.
+the number of elements in a request path is not less than the specified
+number.
 For example, the directive
 <example>
 min_delete_depth 4;
 </example>
-allows to remove files on requests
+allows removing files on requests
 <example>
 /users/00/00/name
 /users/00/00/name/pic.jpg

--- a/xml/en/docs/http/ngx_http_empty_gif_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_empty_gif_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -15,7 +15,7 @@
 <section id="summary">
 
 <para>
-The module <literal>ngx_http_empty_gif_module</literal> emits
+The <literal>ngx_http_empty_gif_module</literal> module emits
 single-pixel transparent GIF.
 </para>
 

--- a/xml/en/docs/http/ngx_http_fastcgi_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_fastcgi_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -15,7 +15,7 @@
 <section id="summary">
 
 <para>
-The <literal>ngx_http_fastcgi_module</literal> module allows to pass
+The <literal>ngx_http_fastcgi_module</literal> module allows passing
 requests to a FastCGI server.
 </para>
 
@@ -53,13 +53,13 @@
 <appeared-in>0.8.22</appeared-in>
 
 <para>
-Forces outgoing connections to a FastCGI server to originate
+Makes outgoing connections to a FastCGI server originate
 from the specified local IP <value>address</value>.
-Value of the parameter can contain variables (1.3.12).
+Parameter value can contain variables (1.3.12).
 The special value <literal>off</literal> (1.3.12) cancels the effect
 of the <literal>fastcgi_bind</literal> directive
-inherited from the previous configuration level, allowing the
-system to auto-assign local address.
+inherited from the previous configuration level, which allows the
+system to auto-assign the local IP address.
 </para>
 
 </directive>
@@ -73,7 +73,7 @@
 <context>location</context>
 
 <para>
-Sets <value>size</value> of the buffer used for reading the first part
+Sets the <value>size</value> of the buffer used for reading the first part
 of a response received from the FastCGI server.
 This part usually contains a small response header.
 By default, the buffer size is equal to the size of one
@@ -115,7 +115,7 @@
 yet fully read.
 In the mean time, the rest of the buffers can be used for reading a response
 and, if needed, buffering part of a response to a temporary file.
-By default, <value>size</value> is limited by two buffers set by the
+By default, <value>size</value> is limited by the size of two buffers set by the
 <link id="fastcgi_buffer_size"/> and <link id="fastcgi_buffers"/> directives.
 </para>
 
@@ -190,7 +190,7 @@
 a new cache element identified according to the <link id="fastcgi_cache_key"/>
 directive by passing a request to a FastCGI server.
 Other requests of the same cache element will either wait
-for a response to appear in the cache, or the cache lock for
+for a response to appear in the cache or the cache lock for
 this element to be released, up to the time set by the
 <link id="fastcgi_cache_lock_timeout"/> directive.
 </para>
@@ -265,7 +265,7 @@
 <context>http</context>
 
 <para>
-Sets path and other parameters of a cache.
+Sets the path and other parameters of a cache.
 Cache data are stored in files.
 Both the key and file name in a cache are a result of
 applying the MD5 function to the proxied URL.
@@ -282,12 +282,14 @@
 </para>
 
 <para>
-A cached response is first written to a temporary file, then a file is renamed.
-Starting from version 0.8.9 temporary files and the cache can be put on
-different file systems but be aware that in this case a file is copied
-across two file systems instead of the cheap rename operation.
+A cached response is first written to a temporary file,
+and then the file is renamed.
+Starting from version 0.8.9, temporary files and the cache can be put on
+different file systems.
+However, be aware that in this case a file is copied
+across two file systems instead of the cheap renaming operation.
 It is thus recommended that for any given location both cache and a directory
-holding temporary files set by the <link id="fastcgi_temp_path"/> directive
+holding temporary files, set by the <link id="fastcgi_temp_path"/> directive,
 are put on the same file system.
 </para>
 
@@ -302,22 +304,22 @@
 </para>
 
 <para>
-The special process “cache manager” monitors the maximum cache size set
-by the <literal>max_size</literal> parameter;
-when this size is exceeded it removes the least recently used data.
+The special “cache manager” process monitors the maximum cache size set
+by the <literal>max_size</literal> parameter.
+When this size is exceeded, it removes the least recently used data.
 </para>
 
 <para>
-A minute after the start the special process “cache loader” is activated
-that loads information about previously cached data stored on file system
+A minute after the start the special “cache loader” process is activated.
+It loads information about previously cached data stored on file system
 into a cache zone.
-A load is done in iterations.
+The loading is done in iterations.
 During one iteration no more than <literal>loader_files</literal> items
 are loaded (by default, 100).
 Besides, the duration of one iteration is limited by the
 <literal>loader_threshold</literal> parameter (by default, 200 milliseconds).
-A pause is made between iterations, configured by the
-<literal>loader_sleep</literal> parameter (by default, 50 milliseconds).
+Between iterations, a pause configured by the <literal>loader_sleep</literal>
+parameter (by default, 50 milliseconds) is made.
 </para>
 
 </directive>
@@ -341,17 +343,16 @@
 <context>location</context>
 
 <para>
-If an error occurs while working with the FastCGI server it is possible
-to use a stale cached response.
-This directives determines in which cases it is permitted.
-The directive’s parameters match those of the
+Determines in which cases a stale cached response can be used
+when an error occurs during communication with the FastCGI server.
+The directive’s parameters match the parameters of the
 <link id="fastcgi_next_upstream"/> directive.
 </para>
 
 <para>
 Additionally, the <literal>updating</literal> parameter permits
-to use a stale cached response if it is currently being updated.
-This allows to minimize the number of accesses to FastCGI servers
+using a stale cached response if it is currently being updated.
+This allows minimizing the number of accesses to FastCGI servers
 when updating cached data.
 </para>
 
@@ -378,7 +379,7 @@
 fastcgi_cache_valid 200 302 10m;
 fastcgi_cache_valid 404      1m;
 </example>
-set 10 minutes of caching for responses with codes 200 and 302,
+set 10 minutes of caching for responses with codes 200 and 302
 and 1 minute for responses with code 404.
 </para>
 
@@ -391,8 +392,8 @@
 </para>
 
 <para>
-In addition, it can be specified to cache any responses using the
-<literal>any</literal> parameter:
+In addition, the <literal>any</literal> parameter can be specified
+to cache any responses:
 <example>
 fastcgi_cache_valid 200 302 10m;
 fastcgi_cache_valid 301      1h;
@@ -403,11 +404,11 @@
 <para>
 Parameters of caching can also be set directly
 in the response header.
-This has a higher precedence than setting of caching time using the directive.
+This has higher priority than setting of caching time using the directive.
 The <header>X-Accel-Expires</header> header field sets caching time of a
 response in seconds.
-The value 0 disables to cache a response.
-If a value starts with the prefix <literal>@</literal>, it sets an absolute
+The zero value disables caching for a response.
+If a value starts with the <literal>@</literal> prefix, it sets an absolute
 time in seconds since Epoch, up to which the response may be cached.
 If header does not include the <header>X-Accel-Expires</header> field,
 parameters of caching may be set in the header fields
@@ -432,8 +433,8 @@
 Sets a string to search for in the error stream of a response
 received from a FastCGI server.
 If the <value>string</value> is found then it is considered that the FastCGI
-server returned an <link id="fastcgi_next_upstream">invalid response</link>.
-This allows to handle application errors in nginx, for example:
+server has returned an <link id="fastcgi_next_upstream">invalid response</link>.
+This allows handling application errors in nginx, for example:
 <example>
 location /php {
     fastcgi_pass backend:9000;
@@ -455,7 +456,7 @@
 <context>location</context>
 
 <para>
-Defines a timeout for establishing a connection with the FastCGI server.
+Defines a timeout for establishing a connection with a FastCGI server.
 It should be noted that this timeout cannot usually exceed 75 seconds.
 </para>
 
@@ -472,7 +473,7 @@
 <para>
 By default,
 nginx does not pass the header fields <header>Status</header> and
-<header>X-Accel-...</header> from the response of the FastCGI
+<header>X-Accel-...</header> from the response of a FastCGI
 server to a client.
 The <literal>fastcgi_hide_header</literal> directive sets additional fields
 that will not be passed.
@@ -491,8 +492,8 @@
 <context>location</context>
 
 <para>
-Determines should the connection with the FastCGI server be
-closed if a client closes a connection without waiting
+Determines whether the connection with a FastCGI server should be
+closed when a client closes a connection without waiting
 for a response.
 </para>
 
@@ -516,13 +517,14 @@
 </para>
 
 <para>
-If not disabled, processing of these header fields has the following effect:
+If not disabled, processing of these header fields has the following
+effect:
 <list type="bullet" compact="no">
 
 <listitem>
 <header>X-Accel-Expires</header>, <header>Expires</header>,
 <header>Cache-Control</header>, and <header>Set-Cookie</header>
-set parameters of response <link id="fastcgi_cache_valid">caching</link>;
+set the parameters of response <link id="fastcgi_cache_valid">caching</link>;
 </listitem>
 
 <listitem>
@@ -532,7 +534,7 @@
 </listitem>
 
 <listitem>
-<header>X-Accel-Limit-Rate</header> sets a
+<header>X-Accel-Limit-Rate</header> sets the
 <link doc="ngx_http_core_module.xml" id="limit_rate">rate
 limit</link> for transmission of a response to a client;
 </listitem>
@@ -589,7 +591,7 @@
 <para>
 Determines whether FastCGI server responses with codes greater than or equal
 to 300 should be passed to a client or be redirected to nginx for processing
-using the <link doc="ngx_http_core_module.xml" id="error_page"/> directive.
+with the <link doc="ngx_http_core_module.xml" id="error_page"/> directive.
 </para>
 
 </directive>
@@ -606,9 +608,9 @@
 <para>
 By default, a FastCGI server will close a connection right after
 sending the response.
-When set to the value <literal>on</literal>, nginx will instruct
-a FastCGI server to keep connections open.
-This in particular is necessary for
+However, when this directive is set to the value <literal>on</literal>,
+nginx will instruct a FastCGI server to keep connections open.
+This is necessary, in particular, for
 <link doc="ngx_http_upstream_module.xml" id="keepalive"/>
 connections to FastCGI servers to function.
 </para>
@@ -624,16 +626,16 @@
 <context>location</context>
 
 <para>
-When the whole response does not fit into memory buffers
+When the whole response does not fit into the memory buffers
 set by the <link id="fastcgi_buffer_size"/> and <link id="fastcgi_buffers"/>
-directives, part of a response can be saved to a temporary file.
+directives, a part of the response can be saved to a temporary file.
 This directive sets the maximum <value>size</value> of a temporary file.
 The size of data written to a temporary file at a time is set
 by the <link id="fastcgi_temp_file_write_size"/> directive.
 </para>
 
 <para>
-Value of zero disables buffering of responses to temporary files.
+The zero value disables buffering of responses to temporary files.
 </para>
 
 </directive>
@@ -661,14 +663,14 @@
 
 <tag-name><literal>error</literal></tag-name>
 <tag-desc>an error occurred while establishing a connection with the
-server, passing it a request, or reading the response header;</tag-desc>
+server, passing a request to it, or reading the response header;</tag-desc>
 
 <tag-name><literal>timeout</literal></tag-name>
 <tag-desc>a timeout has occurred while establishing a connection with the
-server, passing it a request, or reading the response header;</tag-desc>
+server, passing a request to it, or reading the response header;</tag-desc>
 
 <tag-name><literal>invalid_header</literal></tag-name>
-<tag-desc>a server returned empty or invalid response;</tag-desc>
+<tag-desc>a server returned an empty or invalid response;</tag-desc>
 
 <tag-name><literal>http_500</literal></tag-name>
 <tag-desc>a server returned a response with the code 500;</tag-desc>
@@ -689,10 +691,10 @@
 </para>
 
 <para>
-It should be understood that passing a request to the next server is
-only possible if a client was not sent anything yet.
-That is, if an error or a timeout occurs in the middle of
-transferring a response, fixing this is impossible.
+One should bear in mind that passing a request to the next server is
+only possible if nothing has been sent to a client yet.
+That is, if an error or timeout occurs in the middle of the
+transferring of a response, fixing this is impossible.
 </para>
 
 <para>
@@ -801,9 +803,9 @@
 <context>if in location</context>
 
 <para>
-Sets an address of the FastCGI server.
-An address can be specified as a domain name or an address, and a port,
-for example,
+Sets the address of a FastCGI server.
+The address can be specified as a domain name or IP address,
+and an optional port:
 <example>
 fastcgi_pass localhost:9000;
 </example>
@@ -831,8 +833,8 @@
 <context>location</context>
 
 <para>
-Permits to pass <link id="fastcgi_hide_header">otherwise disabled</link> header
-fields from the FastCGI server to a client.
+Permits passing <link id="fastcgi_hide_header">otherwise disabled</link> header
+fields from a FastCGI server to a client.
 </para>
 
 </directive>
@@ -847,7 +849,7 @@
 
 <para>
 Defines a timeout for reading a response from the FastCGI server.
-A timeout is only set between two successive read operations,
+A timeout is set only between two successive read operations,
 not for the transmission of the whole response.
 If a FastCGI server does not transmit anything within this time,
 a connection is closed.
@@ -864,7 +866,7 @@
 <context>location</context>
 
 <para>
-If disabled, the original request body will not be passed
+Indicates whether the original request body is passed
 to the FastCGI server.
 See also the <link id="fastcgi_pass_request_headers"/> directive.
 </para>
@@ -880,8 +882,8 @@
 <context>location</context>
 
 <para>
-If disabled, header fields of the original request will not be passed to the
-FastCGI server.
+Indicates whether the header fields of the original request are passed
+to the FastCGI server.
 See also the <link id="fastcgi_pass_request_body"/> directive.
 </para>
 
@@ -896,7 +898,8 @@
 <context>location</context>
 
 <para>
-If set to a non-zero value, nginx will try to minimize the number
+If the directive is set to a non-zero value, nginx will try to
+minimize the number
 of send operations on outgoing connections to a FastCGI server by using either
 <c-def>NOTE_LOWAT</c-def> flag of the
 <link doc="../events.xml" id="kqueue"/> method,
@@ -920,7 +923,7 @@
 
 <para>
 Sets a timeout for transmitting a request to the FastCGI server.
-A timeout is only set between two successive write operations,
+A timeout is set only between two successive write operations,
 not for the transmission of the whole request.
 If a FastCGI server does not receive anything within this time,
 a connection is closed.
@@ -937,7 +940,7 @@
 <para>
 Defines a regular expression that captures a value for the
 <var>$fastcgi_path_info</var> variable.
-A regular expression should have two captures, the first becomes
+A regular expression should have two captures: the first becomes
 a value of the <var>$fastcgi_script_name</var> variable, the second
 becomes a value of the <var>$fastcgi_path_info</var> variable.
 For example, with these settings
@@ -984,13 +987,14 @@
 <para>
 The modification time of files is set according to the received
 <header>Last-Modified</header> response header field.
-A response is first written to a temporary file, then a file is renamed.
-Starting from version 0.8.9 temporary files and the persistent store
-can be put on different file systems but be aware that in this case
-a file is copied across two file systems instead of the cheap rename operation.
+A response is first written to a temporary file, and then the file is renamed.
+Starting from version 0.8.9, temporary files and the persistent store
+can be put on different file systems.
+However, be aware that in this case a file is copied
+across two file systems instead of the cheap renaming operation.
 It is thus recommended that for any given location both saved files and a
-directory holding temporary files set by the <link id="fastcgi_temp_path"/>
-directive are put on the same file system.
+directory holding temporary files, set by the <link id="fastcgi_temp_path"/>
+directive, are put on the same file system.
 </para>
 
 <para>
@@ -1105,7 +1109,7 @@
 these parameters are usually made available as environment variables.
 For example, the <header>User-Agent</header> header field is passed as the
 <literal>HTTP_USER_AGENT</literal> parameter.
-In addition to HTTP request header fields it is possible to pass arbitrary
+In addition to HTTP request header fields, it is possible to pass arbitrary
 parameters using the <link id="fastcgi_param"/> directive.
 </para>
 
@@ -1138,7 +1142,7 @@
 
 <para>
 When using the <link id="fastcgi_split_path_info"/> directive,
-the <var>$fastcgi_script_name</var> variable equals to the value of
+the <var>$fastcgi_script_name</var> variable equals the value of
 the first capture set by the directive.
 </para>
 </tag-desc>

--- a/xml/en/docs/http/ngx_http_flv_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_flv_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -15,15 +15,15 @@
 <section id="summary">
 
 <para>
-The module <literal>ngx_http_flv_module</literal> provides pseudo-streaming
+The <literal>ngx_http_flv_module</literal> module provides pseudo-streaming
 server-side support for Flash Video (FLV) files.
 </para>
 
 <para>
 It handles requests with the <literal>start</literal> argument in
 the request URI’s query string specially, by sending back the contents
-of a file starting from the requested byte offset, and with the FLV
-header prepended.
+of a file starting from the requested byte offset and with the prepended FLV
+header.
 </para>
 
 <para>

--- a/xml/en/docs/http/ngx_http_geo_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_geo_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -16,7 +16,7 @@
 
 <para>
 The <literal>ngx_http_geo_module</literal> module creates variables
-whose values depend on the client IP address.
+with values depending on the client IP address.
 </para>
 
 </section>
@@ -52,7 +52,7 @@
 <para>
 Describes the dependency of values of the specified variable
 on the client IP address.
-By default an address is taken from the <var>$remote_addr</var> variable
+By default, the address is taken from the <var>$remote_addr</var> variable,
 but it can also be taken from another variable (0.7.27), for example:
 <example>
 geo $arg_remote_addr $geo {
@@ -65,7 +65,7 @@
 <note>
 Since variables are evaluated only when used, the mere existence
 of even a large number of declared “<literal>geo</literal>” variables
-does not incur any extra costs for request processing.
+does not cause any extra costs for request processing.
 </note>
 </para>
 
@@ -93,7 +93,7 @@
 
 <tag-name><literal>default</literal></tag-name>
 <tag-desc>
-a value of variable if the client address does not
+a value set to the variable if the client address does not
 match any of the specified addresses.
 When addresses are specified in CIDR notation,
 “<literal>0.0.0.0/0</literal>” and “<literal>::/0</literal>”
@@ -124,10 +124,10 @@
 <tag-name><literal>proxy_recursive</literal></tag-name>
 <tag-desc>
 enables recursive address search (1.3.0, 1.2.1).
-If recursive search is disabled then instead of an original client
+If recursive search is disabled then instead of the original client
 address that matches one of the trusted addresses, the last
 address sent in <header>X-Forwarded-For</header> will be used.
-If recursive search is enabled then instead an original client
+If recursive search is enabled then instead of the original client
 address that matches one of the trusted addresses, the last
 non-trusted address sent in <header>X-Forwarded-For</header> will be used.
 </tag-desc>
@@ -136,7 +136,7 @@
 <tag-desc>
 indicates that addresses are specified as ranges (0.7.23).
 This parameter should be the first.
-To speed up loading of a geo base, addresses should be put in increasing order.
+To speed up loading of a geo base, addresses should be put in ascending order.
 </tag-desc>
 
 </list>

--- a/xml/en/docs/http/ngx_http_geoip_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_geoip_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -16,12 +16,12 @@
 
 <para>
 The <literal>ngx_http_geoip_module</literal> module (0.8.6+) creates variables
-whose values depend on the client IP address, using the precompiled
+with values depending on the client IP address, using the precompiled
 <link url="http://www.maxmind.com">MaxMind</link> databases.
 </para>
 
 <para>
-When using IPv6 databases (1.3.12, 1.2.7),
+When using the databases with IPv6 support (1.3.12, 1.2.7),
 IPv4 addresses are looked up as IPv4-mapped IPv6 addresses.
 </para>
 
@@ -63,7 +63,7 @@
 <context>http</context>
 
 <para>
-Specifies a database used to determine a country
+Specifies a database used to determine the country
 depending on the client IP address.
 The following variables are available when using this database:
 <list type="tag">
@@ -98,7 +98,7 @@
 <context>http</context>
 
 <para>
-Specifies a database used to determine a country, region, and city
+Specifies a database used to determine the country, region, and city
 depending on the client IP address.
 The following variables are available when using this database:
 <list type="tag">
@@ -185,7 +185,7 @@
 <appeared-in>1.0.3</appeared-in>
 
 <para>
-Specifies a database used to determine an organization
+Specifies a database used to determine the organization
 depending on the client IP address.
 The following variable is available when using this database:
 <list type="tag">
@@ -226,10 +226,10 @@
 <appeared-in>1.2.1</appeared-in>
 
 <para>
-If recursive search is disabled then instead of an original client
+If recursive search is disabled then instead of the original client
 address that matches one of the trusted addresses, the last
 address sent in <header>X-Forwarded-For</header> will be used.
-If recursive search is enabled then instead an original client
+If recursive search is enabled then instead of the original client
 address that matches one of the trusted addresses, the last
 non-trusted address sent in <header>X-Forwarded-For</header> will be used.
 </para>

--- a/xml/en/docs/http/ngx_http_gunzip_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_gunzip_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -19,7 +19,7 @@
 decompresses responses with “<literal>Content-Encoding: gzip</literal>”
 for clients that do not support “gzip” encoding method.
 The module will be useful when it is desirable to store
-data compressed, to save space and reduce I/O costs.
+data compressed to save space and reduce I/O costs.
 </para>
 
 <para>

--- a/xml/en/docs/http/ngx_http_gzip_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_gzip_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -17,7 +17,7 @@
 <para>
 The <literal>ngx_http_gzip_module</literal> module is a filter
 that compresses responses using the “gzip” method.
-This often allows to reduce the size of transmitted data by half or even more.
+This often helps to reduce the size of transmitted data by half or even more.
 </para>
 
 </section>
@@ -89,7 +89,7 @@
 
 <para>
 Sets a gzip compression <value>level</value> of a response.
-Acceptable values are in the 1..9 range.
+Acceptable values are in the range from 1 to 9.
 </para>
 
 </directive>
@@ -111,7 +111,7 @@
 
 <para>
 The special mask “<literal>msie6</literal>” (0.7.12) corresponds to
-the regular expression “<literal>MSIE [4-6]\.</literal>” but works faster.
+the regular expression “<literal>MSIE [4-6]\.</literal>”, but works faster.
 Starting from version 0.8.11, “<literal>MSIE 6.0; ... SV1</literal>”
 is excluded from this mask.
 </para>
@@ -169,7 +169,7 @@
 <para>
 Enables or disables gzipping of responses for proxied
 requests depending on the request and response.
-The fact that the response is proxied is determined based on
+The fact that the response is proxied is determined by
 the presence of the <header>Via</header> request header field.
 A directive accepts multiple parameters:
 <list type="tag">
@@ -182,45 +182,47 @@
 
 <tag-name><literal>expired</literal></tag-name>
 <tag-desc>
-enables compression if a response header includes the field
-<header>Expires</header> with a value that disables caching;
+enables compression if a response header includes the
+<header>Expires</header> field with a value that disables caching;
 </tag-desc>
 
 <tag-name><literal>no-cache</literal></tag-name>
 <tag-desc>
-enables compression if a response header includes the field
-<header>Cache-Control</header> with the parameter “<literal>no-cache</literal>”;
+enables compression if a response header includes the
+<header>Cache-Control</header> field with the
+“<literal>no-cache</literal>” parameter;
 </tag-desc>
 
 <tag-name><literal>no-store</literal></tag-name>
 <tag-desc>
-enables compression if a response header includes the field
-<header>Cache-Control</header> with the parameter
-“<literal>no-store</literal>”;
+enables compression if a response header includes the
+<header>Cache-Control</header> field with the
+“<literal>no-store</literal>” parameter;
 </tag-desc>
 
 <tag-name><literal>private</literal></tag-name>
 <tag-desc>
-enables compression if a response header includes the field
-<header>Cache-Control</header> with the parameter “<literal>private</literal>”;
+enables compression if a response header includes the
+<header>Cache-Control</header> field with the
+“<literal>private</literal>” parameter;
 </tag-desc>
 
 <tag-name><literal>no_last_modified</literal></tag-name>
 <tag-desc>
-enables compression if a response header does not include the field
-<header>Last-Modified</header>;
+enables compression if a response header does not include the
+<header>Last-Modified</header> field;
 </tag-desc>
 
 <tag-name><literal>no_etag</literal></tag-name>
 <tag-desc>
-enables compression if a response header does not include the field
-<header>ETag</header>;
+enables compression if a response header does not include the
+<header>ETag</header> field;
 </tag-desc>
 
 <tag-name><literal>auth</literal></tag-name>
 <tag-desc>
-enables compression if a request header includes the field
-<header>Authorization</header>;
+enables compression if a request header includes the
+<header>Authorization</header> field;
 </tag-desc>
 
 <tag-name><literal>any</literal></tag-name>
@@ -245,7 +247,7 @@
 Enables gzipping of responses for the specified MIME types in addition
 to “<literal>text/html</literal>”.
 The special value “<literal>*</literal>” matches any MIME type (0.8.29).
-Responses with the type “<literal>text/html</literal>” are always compressed.
+Responses with the “<literal>text/html</literal>” type are always compressed.
 </para>
 
 </directive>
@@ -259,7 +261,7 @@
 <context>location</context>
 
 <para>
-Enables or disables emitting the <header>Vary: Accept-Encoding</header>
+Enables or disables inserting the <header>Vary: Accept-Encoding</header>
 response header field if the directives
 <link id="gzip"/>,
 <link doc="ngx_http_gzip_static_module.xml" id="gzip_static"/>, or
@@ -279,7 +281,7 @@
 
 <tag-name id="var_gzip_ratio"><var>$gzip_ratio</var></tag-name>
 <tag-desc>achieved compression ratio, computed as the ratio between the
-original and compressed response size.</tag-desc>
+original and compressed response sizes.</tag-desc>
 
 </list>
 </para>

--- a/xml/en/docs/http/ngx_http_gzip_static_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_gzip_static_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -16,7 +16,7 @@
 
 <para>
 The <literal>ngx_http_gzip_static_module</literal> module allows
-to send precompressed files with the “<literal>.gz</literal>”
+sending precompressed files with the “<literal>.gz</literal>”
 filename extension instead of regular files.
 </para>
 
@@ -73,7 +73,7 @@
 
 <para>
 The files can be compressed using the <command>gzip</command> command,
-or any other compatible.
+or any other compatible one.
 It is recommended that the modification date and time of original and
 compressed files be the same.
 </para>

--- a/xml/en/docs/http/ngx_http_headers_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_headers_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -15,9 +15,9 @@
 <section id="summary">
 
 <para>
-The <literal>ngx_http_headers_module</literal> module allows to emit
+The <literal>ngx_http_headers_module</literal> module allows adding
 the <header>Expires</header> and <header>Cache-Control</header> header
-fields, and to add arbitrary fields to a response header.
+fields, and arbitrary fields, to a response header.
 </para>
 
 </section>

--- a/xml/en/docs/http/ngx_http_image_filter_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_image_filter_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -26,8 +26,7 @@
 <note>
 This module utilizes the
 <link url="http://libgd.org">libgd</link> library.
-It is recommended to use the latest available version of the library;
-it is version 2.0.35 as of this writing.
+It is recommended to use the latest available version of the library.
 </note>
 </para>
 
@@ -87,9 +86,9 @@
 <tag-name><literal>test</literal></tag-name>
 <tag-desc>
 ensures that responses are images in either JPEG, GIF, or PNG format.
-Otherwise, the error
+Otherwise, the
 <http-status code="415" text="Unsupported Media Type"/>
-is returned.
+error is returned.
 </tag-desc>
 
 <tag-name><literal>size</literal></tag-name>
@@ -98,7 +97,7 @@
 <example>
 { "img" : { "width": 100, "height": 100, "type": "gif" } }
 </example>
-In case of an error, the following is output:
+In case of an error, the output is as follows:
 <example>
 {}
 </example>
@@ -109,8 +108,8 @@
 </tag-name>
 <tag-desc>
 rotates images counter-clockwise by the specified number of degrees.
-Value of the parameter can contain variables.
-Can be used either alone, or along with the
+Parameter value can contain variables.
+This mode can be used either alone or along with the
 <literal>resize</literal> and <literal>crop</literal> transformations.
 </tag-desc>
 
@@ -124,7 +123,7 @@
 “<literal>-</literal>”.
 In case of an error, the server will return code
 <http-status code="415" text="Unsupported Media Type"/>.
-Values of parameters can contain variables.
+Parameter values can contain variables.
 When used along with the <literal>rotate</literal> parameter,
 the rotation happens <emphasis>after</emphasis> reduction.
 </tag-desc>
@@ -134,13 +133,13 @@
 <value>height</value>
 </tag-name>
 <tag-desc>
-proportionally reduces an image to the size of the largest side
+proportionally reduces an image to the larger side size
 and crops extraneous edges by another side.
 To reduce by only one dimension, another dimension can be specified as
 “<literal>-</literal>”.
 In case of an error, the server will return code
 <http-status code="415" text="Unsupported Media Type"/>.
-Values of parameters can contain variables.
+Parameter values can contain variables.
 When used along with the <literal>rotate</literal> parameter,
 the rotation happens <emphasis>before</emphasis> reduction.
 </tag-desc>
@@ -160,7 +159,7 @@
 
 <para>
 Sets the maximum size of the buffer used for reading images.
-When a size is exceeded the server will return error
+When the size is exceeded the server returns error
 <http-status code="415" text="Unsupported Media Type"/>.
 </para>
 
@@ -192,10 +191,10 @@
 
 <para>
 Sets the desired <value>quality</value> of the transformed JPEG images.
-Acceptable values are in the 1..100 range.
+Acceptable values are in the range from 1 to 100.
 Lesser values usually imply both lower image quality and less data to transfer.
 The maximum recommended value is 95.
-Value of the parameter can contain variables.
+Parameter value can contain variables.
 </para>
 
 </directive>
@@ -211,8 +210,8 @@
 <para>
 Increases sharpness of the final image.
 The sharpness percentage can exceed 100.
-The value of 0 disables sharpening.
-Value of the parameter can contain variables.
+The zero value disables sharpening.
+Parameter value can contain variables.
 </para>
 
 </directive>
@@ -227,8 +226,8 @@
 
 <para>
 Defines whether transparency should be preserved when transforming
-PNG images with colors specified by a palette, or in GIF images.
-The loss of transparency allows to obtain images of a better quality.
+GIF images or PNG images with colors specified by a palette.
+The loss of transparency results in images of a better quality.
 The alpha channel transparency in PNG is always preserved.
 </para>
 

--- a/xml/en/docs/http/ngx_http_index_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_index_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -15,9 +15,9 @@
 <section id="summary">
 
 <para>
-The module <literal>ngx_http_index_module</literal> processes requests
+The <literal>ngx_http_index_module</literal> module processes requests
 ending with the slash character (‘<literal>/</literal>’).
-Such requests can also be processed by
+Such requests can also be processed by the
 <link doc="ngx_http_autoindex_module.xml">ngx_http_autoindex_module</link>
 and
 <link doc="ngx_http_random_index_module.xml">ngx_http_random_index_module</link>
@@ -61,8 +61,8 @@
 </para>
 
 <para>
-It should be noted that when using an index file, an internal redirect
-is made, and request can be processed in a different location.
+It should be noted that using an index file causes an internal redirect,
+and the request can be processed in a different location.
 For example, with the following configuration:
 <example>
 location = / {
@@ -73,7 +73,7 @@
     ...
 }
 </example>
-a request of “<literal>/</literal>” will actually be processed in the
+a “<literal>/</literal>” request will actually be processed in the
 second location as “<literal>/index.html</literal>”.
 </para>
 

--- a/xml/en/docs/http/ngx_http_limit_conn_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_limit_conn_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -15,15 +15,15 @@
 <section id="summary">
 
 <para>
-The <literal>ngx_http_limit_conn_module</literal> module allows
-to limit the number of connections per defined key, in
+The <literal>ngx_http_limit_conn_module</literal> module is used to
+limit the number of connections per the defined key, in
 particular, the number of connections from a single IP address.
 </para>
 
 <para>
-Not all connections are counted; only those that have requests
-currently being processed by the server, in which request header has
-been fully read.
+Not all connections are counted.
+A connection is counted only if it has a request processed by the server
+and the whole request header has already been read.
 </para>
 
 </section>
@@ -61,11 +61,11 @@
 <context>location</context>
 
 <para>
-Sets a shared memory zone
+Sets the shared memory zone
 and the maximum allowed number of connections for a given key value.
-When this limit is exceeded, the server will return error
+When this limit is exceeded, the server will return the
 <http-status code="503" text="Service Temporarily Unavailable"/>
-in reply to a request.
+error in reply to a request.
 For example, the directives
 <example>
 limit_conn_zone $binary_remote_addr zone=addr:10m;
@@ -75,15 +75,15 @@
         limit_conn addr 1;
     }
 </example>
-allow for only a single connection at a time, per unique IP address.
+allow only one connection per an IP address at a time.
 </para>
 
 <para>
 When several <literal>limit_conn</literal> directives are specified,
 any configured limit will apply.
 For example, the following configuration will limit the number
-of connections to the server per client IP and at the same time
-will limit the total number of connections to the virtual host:
+of connections to the server per a client IP and, at the same time,
+the total number of connections to the virtual host:
 <example>
 limit_conn_zone $binary_remote_addr zone=perip:10m;
 limit_conn_zone $server_name zone=perserver:10m;
@@ -136,7 +136,7 @@
 <appeared-in>1.3.15</appeared-in>
 
 <para>
-Sets status code to be used when requests are rejected.
+Sets the status code to return in response to rejected requests.
 </para>
 
 </directive>
@@ -150,30 +150,32 @@
 <context>http</context>
 
 <para>
-Sets parameters of a shared memory zone that keeps states
-for various keys.
-This state stores the current number of connections in particular.
+Sets parameters for a shared memory zone
+that will keep states for various keys.
+In particular, the state includes the current number of connections.
 The key is any non-empty value of the specified variable
 (empty values are not accounted).
-Example usage:
+Usage example:
 <example>
 limit_conn_zone $binary_remote_addr zone=addr:10m;
 </example>
-Here, an IP address of the client serves as a key.
+Here, a client IP address serves as a key.
 Note that instead of <var>$remote_addr</var>, the
 <var>$binary_remote_addr</var> variable is used here.
-The length of the <var>$remote_addr</var> variable’s value can
-range from 7 to 15 bytes, and the stored state occupies either
-32 or 64 bytes of memory on 32-bit platforms, and always 64
+The <var>$remote_addr</var> variable’s size can
+vary from 7 to 15 bytes.
+The stored state occupies either
+32 or 64 bytes of memory on 32-bit platforms and always 64
 bytes on 64-bit platforms.
-The length of the <var>$binary_remote_addr</var> variable’s value
-is always 4 bytes, and the stored state always occupies 32 bytes
-on 32-bit platforms, and 64 bytes on 64-bit platforms.
-One megabyte zone can keep about 32 thousand 32-byte states,
-and about 16 thousand 64-byte states.
-If the storage for a zone is exhausted, the server will return error
+The <var>$binary_remote_addr</var> variable’s size
+is always 4 bytes.
+The stored state always occupies 32 bytes
+on 32-bit platforms and 64 bytes on 64-bit platforms.
+One megabyte zone can keep about 32 thousand 32-byte states
+or about 16 thousand 64-byte states.
+If the zone storage is exhausted, the server will return the
 <http-status code="503" text="Service Temporarily Unavailable"/>
-to all further requests.
+error to all further requests.
 </para>
 
 </directive>

--- a/xml/en/docs/http/ngx_http_limit_req_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_limit_req_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -15,8 +15,8 @@
 <section id="summary">
 
 <para>
-The <literal>ngx_http_limit_req_module</literal> module (0.7.21) allows
-to limit the request processing rate per defined key,
+The <literal>ngx_http_limit_req_module</literal> module (0.7.21) is used
+to limit the request processing rate per a defined key,
 in particular, the processing rate of requests coming
 from a single IP address.
 The limitation is done using the “leaky bucket” method.
@@ -60,9 +60,9 @@
 <context>location</context>
 
 <para>
-Sets a shared memory zone
+Sets the shared memory zone
 and the maximum burst size of requests.
-If the rate of requests exceeds the rate configured for a zone,
+If the requests rate exceeds the rate configured for a zone,
 their processing is delayed such that requests are processed
 at a defined rate.
 Excessive requests are delayed until their number exceeds the
@@ -109,9 +109,9 @@
 <para>
 Sets the desired logging level
 for cases when the server refuses to process requests
-due to rate being exceeded,
+due to rate exceeding,
 or delays request processing.
-Delays are logged with the level one less than refusals; for example,
+Logging level for delays is one point less than for refusals; for example,
 if “<literal>limit_req_log_level notice</literal>” is specified,
 delays are logged with the <literal>info</literal> level.
 </para>
@@ -128,7 +128,7 @@
 <appeared-in>1.3.15</appeared-in>
 
 <para>
-Sets status code to be used when requests are rejected.
+Sets the status code to return in response to rejected requests.
 </para>
 
 </directive>
@@ -143,12 +143,12 @@
 <context>http</context>
 
 <para>
-Sets parameters of a shared memory zone
-that keeps states for various keys.
-The state stores the current number of excessive requests in particular.
+Sets parameters for a shared memory zone
+that will keep states for various keys.
+In particular, the state stores the current number of excessive requests.
 The key is any non-empty value of the specified variable
 (empty values are not accounted).
-Example usage:
+Usage example:
 <example>
 limit_req_zone $binary_remote_addr zone=one:10m rate=1r/s;
 </example>
@@ -161,14 +161,14 @@
 </para>
 
 <para>
-An IP address of the client serves as a key.
+A client IP address serves as a key.
 Note that instead of <var>$remote_addr</var>, the
 <var>$binary_remote_addr</var> variable is used here,
-allowing to lower the size of a state down to 64 bytes.
+that allows to decrease the state size down to 64 bytes.
 One megabyte zone can keep about 16 thousand 64-byte states.
-If the storage for a zone is exhausted, the server will return error
+If the zone storage is exhausted, the server will return the
 <http-status code="503" text="Service Temporarily Unavailable"/>
-to all further requests.
+error to all further requests.
 </para>
 
 <para>

--- a/xml/en/docs/http/ngx_http_log_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_log_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -20,8 +20,8 @@
 </para>
 
 <para>
-Requests are logged in a context of a location where processing ends.
-This may be different from the original location, if an
+Requests are logged in the context of a location where processing ends.
+It may be different from the original location, if an
 <link doc="ngx_http_core_module.xml" id="internal">internal
 redirect</link> happens during request processing.
 </para>
@@ -70,14 +70,14 @@
 <context>limit_except</context>
 
 <para>
-Sets the path, format, and configuration of the buffered log writes.
+Sets the path, format, and configuration for a buffered log write.
 Several logs can be specified on the same level.
 Logging to syslog can be configured by specifying
 the “<literal>syslog:</literal>” prefix in the first parameter.
 The special value <literal>off</literal> cancels all
 <literal>access_log</literal> directives on the current level.
-If format is not specified then the predefined format
-“<literal>combined</literal>” is used.
+If the format is not specified then the predefined
+“<literal>combined</literal>” format is used.
 </para>
 
 <para>
@@ -85,7 +85,7 @@
 (1.3.10, 1.2.7)
 parameter is used, writes to log will be buffered.
 <note>
-The buffer size must not exceed the size of the atomic write to a disk file.
+The buffer size must not exceed the size of an atomic write to a disk file.
 For FreeBSD this size is unlimited.
 </note>
 </para>
@@ -116,7 +116,7 @@
 be compressed before writing to the file.
 The compression level can be set between 1 (fastest, less compression)
 and 9 (slowest, best compression).
-By default the buffer size is equal to 64K bytes, and the compression level
+By default, the buffer size is equal to 64K bytes, and the compression level
 is set to 1.
 Since the data is compressed in atomic blocks, the log file can be decompressed
 or read by “<literal>zcat</literal>” at any time.
@@ -152,12 +152,11 @@
 </listitem>
 
 <listitem>
-a file is opened and closed for each log write.
+the file is opened and closed for each log write.
 However, since the descriptors of frequently used files can be stored
-in a <link id="open_log_file_cache">cache</link>, writes during the
-time specified by the <literal>valid</literal> parameter of the
-<link id="open_log_file_cache"/> directive can continue to be made
-to the old file.
+in a <link id="open_log_file_cache">cache</link>, writing to the old file
+can continue during the time specified by the <link id="open_log_file_cache"/>
+directive’s <literal>valid</literal> parameter
 </listitem>
 
 <listitem>
@@ -260,7 +259,7 @@
 <context>http</context>
 
 <para>
-Specifies format of a log.
+Specifies log format.
 </para>
 
 <para>
@@ -285,7 +284,7 @@
 
 <tag-name><var>$msec</var></tag-name>
 <tag-desc>
-time in seconds with a milliseconds resolution at the time of log write
+time in seconds with a milliseconds resolution at the time of the log write
 </tag-desc>
 
 <tag-name><var>$pipe</var></tag-name>
@@ -324,7 +323,7 @@
 </list>
 
 <note>
-In modern versions of nginx variables
+In the modern nginx versions variables
 <link doc="ngx_http_core_module.xml" id="var_status">$status</link>
 (1.3.2, 1.2.2),
 <link doc="ngx_http_core_module.xml" id="var_bytes_sent">$bytes_sent</link>
@@ -358,8 +357,8 @@
 </para>
 
 <para>
-The configuration always includes the predefined format
-“<literal>combined</literal>”:
+The configuration always includes the predefined
+“<literal>combined</literal>” format:
 <example>
 log_format combined '$remote_addr - $remote_user [$time_local] '
                     '"$request" $status $body_bytes_sent '
@@ -384,36 +383,36 @@
 <context>location</context>
 
 <para>
-Defines a cache that stores file descriptors of frequently used logs
+Defines a cache that stores the file descriptors of frequently used logs
 whose names contain variables.
 The directive has the following parameters:
 <list type="tag">
 
 <tag-name><literal>max</literal></tag-name>
 <tag-desc>
-sets a maximum number of descriptors in a cache;
-if cache becomes full the least recently used (LRU)
+sets the maximum number of descriptors in a cache;
+if the cache becomes full the least recently used (LRU)
 descriptors are closed
 </tag-desc>
 
 <tag-name><literal>inactive</literal></tag-name>
 <tag-desc>
-sets a time after which the cached descriptor is closed
+sets the time after which the cached descriptor is closed
 if there were no access during this time;
 by default, 10 seconds
 </tag-desc>
 
 <tag-name><literal>min_uses</literal></tag-name>
 <tag-desc>
-sets a minimum number of file uses during the time
+sets the minimum number of file uses during the time
 defined by the <literal>inactive</literal> parameter
-after which the descriptor will stay open in a cache;
+to let the descriptor stay open in a cache;
 by default, 1
 </tag-desc>
 
 <tag-name><literal>valid</literal></tag-name>
 <tag-desc>
-sets a time after which it should be checked that the file
+sets the time after which it should be checked that the file
 still exists with the same name; by default, 60 seconds
 </tag-desc>
 
@@ -426,7 +425,7 @@
 </para>
 
 <para>
-Example usage:
+Usage example:
 <example>
 open_log_file_cache max=1000 inactive=20s valid=1m min_uses=2;
 </example>

--- a/xml/en/docs/http/ngx_http_map_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_map_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -70,9 +70,9 @@
 
 <para>
 <note>
-Since variables are evaluated only when used, the mere existence
-of even a large number of declared “<literal>map</literal>” variables
-does not incur any extra costs for request processing.
+Since variables are evaluated only when they are used, the mere declaration
+even of a large number of “<literal>map</literal>” variables
+does not add any extra costs to request processing.
 </note>
 </para>
 
@@ -117,8 +117,7 @@
 
 <tag-name><literal>hostnames</literal></tag-name>
 <tag-desc>
-allows to specify hostnames with a prefix or suffix mask, as source
-values, for example,
+indicates that source values can be hostnames with a prefix or suffix mask:
 <example>
 *.example.com 1;
 example.*     1;
@@ -146,8 +145,8 @@
 
 <para>
 If the source value matches more than one of the specified variants,
-e.g. both mask and regular expression match, the first matching
-variant will be chosen, in the following order of precedence:
+e.g. both a mask and a regular expression match, the first matching
+variant will be chosen, in the following order of priority:
 <list type="enum">
 
 <listitem>
@@ -186,8 +185,8 @@
 
 <para>
 Sets the bucket size for the <link id="map"/> variables hash tables.
-Default value depends on the size of the processor’s cache line.
-Details of setting up hash tables are provided in a separate
+Default value depends on the processor’s cache line size.
+The details of setting up hash tables are provided in a separate
 <link doc="../hash.xml">document</link>.
 </para>
 
@@ -202,7 +201,7 @@
 <para>
 Sets the maximum <value>size</value> of the <link id="map"/> variables
 hash tables.
-Details of setting up hash tables are provided in a separate
+The details of setting up hash tables are provided in a separate
 <link doc="../hash.xml">document</link>.
 </para>
 

--- a/xml/en/docs/http/ngx_http_memcached_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_memcached_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -15,10 +15,10 @@
 <section id="summary">
 
 <para>
-The <literal>ngx_http_memcached_module</literal> module allows to obtain
+The <literal>ngx_http_memcached_module</literal> module is used to obtain
 responses from a memcached server.
 The key is set in the <var>$memcached_key</var> variable.
-A response should be put in memcached in advance via means that are
+A response should be put in memcached in advance by means
 external to nginx.
 </para>
 
@@ -57,13 +57,13 @@
 <appeared-in>0.8.22</appeared-in>
 
 <para>
-Forces outgoing connections to a memcached server to originate
+Makes outgoing connections to a memcached server originate
 from the specified local IP <value>address</value>.
-Value of the parameter can contain variables (1.3.12).
+Parameter value can contain variables (1.3.12).
 The special value <literal>off</literal> (1.3.12) cancels the effect
 of the <literal>memcached_bind</literal> directive
-inherited from the previous configuration level, allowing the
-system to auto-assign local address.
+inherited from the previous configuration level, which allows the
+system to auto-assign the local IP address.
 </para>
 
 </directive>
@@ -77,9 +77,9 @@
 <context>location</context>
 
 <para>
-Sets <value>size</value> of the buffer used for reading a response
+Sets the <value>size</value> of the buffer used for reading a response
 received from the memcached server.
-A response is passed to a client synchronously, immediately as it is received.
+A response is passed to a client synchronously, as soon as it is received.
 </para>
 
 </directive>
@@ -93,7 +93,7 @@
 <context>location</context>
 
 <para>
-Defines a timeout for establishing a connection with the memcached server.
+Defines a timeout for establishing a connection with a memcached server.
 It should be noted that this timeout cannot usually exceed 75 seconds.
 </para>
 
@@ -110,8 +110,8 @@
 
 <para>
 Enables the test for the <value>flag</value> presence in the memcached
-server response and sets the response header field
-“<literal>Content-Encoding</literal>” to “<literal>gzip</literal>”
+server response and sets the “<literal>Content-Encoding</literal>”
+response header field to “<literal>gzip</literal>”
 if the flag is set.
 </para>
 
@@ -137,14 +137,14 @@
 
 <tag-name><literal>error</literal></tag-name>
 <tag-desc>an error occurred while establishing a connection with the
-server, passing it a request, or reading the response header;</tag-desc>
+server, passing a request to it, or reading the response header;</tag-desc>
 
 <tag-name><literal>timeout</literal></tag-name>
 <tag-desc>a timeout has occurred while establishing a connection with the
-server, passing it a request, or reading the response header;</tag-desc>
+server, passing a request to it, or reading the response header;</tag-desc>
 
 <tag-name><literal>invalid_response</literal></tag-name>
-<tag-desc>a server returned empty or invalid response;</tag-desc>
+<tag-desc>a server returned an empty or invalid response;</tag-desc>
 
 <tag-name><literal>not_found</literal></tag-name>
 <tag-desc>a response was not found on the server;</tag-desc>
@@ -156,10 +156,10 @@
 </para>
 
 <para>
-It should be understood that passing a request to the next server is
-only possible if a client was not sent anything yet.
-That is, if an error or a timeout occurs in the middle of
-transferring a response, fixing this is impossible.
+One should bear in mind that passing a request to the next server is
+only possible if nothing has been sent to a client yet.
+That is, if an error or timeout occurs in the middle of the
+transferring of a response, fixing this is impossible.
 </para>
 
 <para>
@@ -183,9 +183,8 @@
 <context>if in location</context>
 
 <para>
-Sets an address of the memcached server.
-An address can be specified as a domain name or an address, and a port,
-for example,
+Sets the memcached server address.
+The address can be specified as a domain name or an address, and a port:
 <example>
 memcached_pass localhost:11211;
 </example>
@@ -214,10 +213,10 @@
 
 <para>
 Defines a timeout for reading a response from the memcached server.
-A timeout is only set between two successive read operations,
+A timeout is set only between two successive read operations,
 not for the transmission of the whole response.
 If a memcached server does not transmit anything within this time,
-a connection is closed.
+the connection is closed.
 </para>
 
 </directive>
@@ -232,7 +231,7 @@
 
 <para>
 Sets a timeout for transmitting a request to the memcached server.
-A timeout is only set between two successive write operations,
+A timeout is set only between two successive write operations,
 not for the transmission of the whole request.
 If a memcached server does not receive anything within this time,
 a connection is closed.

--- a/xml/en/docs/http/ngx_http_mp4_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_mp4_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -14,24 +14,25 @@
 <section id="summary">
 
 <para>
-The module <literal>ngx_http_mp4_module</literal> provides pseudo-streaming
-server-side support for H.264/AAC files typically having filename extensions
-<path>.mp4</path>, <path>.m4v</path>, and <path>.m4a</path>.
+The <literal>ngx_http_mp4_module</literal> module provides pseudo-streaming
+server-side support for H.264/AAC files.
+Such files typically have the <path>.mp4</path>, <path>.m4v</path>,
+or <path>.m4a</path> filename extensions.
 </para>
 
 <para>
-Pseudo-streaming works in alliance with conforming Flash players.
+The pseudo-streaming works in alliance with a compatible Flash players.
 A player sends an HTTP request to the server with a start time
-argument in the request URI’s query string (named simply
+specified in the query string argument (named simply
 <literal>start</literal>
-and specified in seconds), and the server responds with a stream
-so that its start position corresponds to the requested time,
+and specified in seconds), and the server responds with the stream
+such that its start position corresponds to the requested time,
 for example:
 <example>
 http://example.com/elephants_dream.mp4?start=238.88
 </example>
-This allows for a random seeking at any time, or starting playback
-in the middle of a timeline.
+This allows performing a random seeking at any time, or starting playback
+in the middle of the timeline.
 </para>
 
 <para>
@@ -45,14 +46,14 @@
 To start playback, a player first needs to read metadata.
 This is done by sending a special request with the
 <literal>start=0</literal>
-argument.  Many encoding software will insert the metadata at
+argument.  Much of encoding software will insert the metadata at
 the end of the file.  This is bad for pseudo-streaming:
-the metadata needs to be located at the beginning of the file,
-or else the entire file will have to be downloaded before it
-starts playing.  If a file is well-formed (with metadata at the
-beginning of a file), nginx just sends back the contents of a file.
+the metadata should be located at the beginning of the file,
+or else the entire file will have to be downloaded to
+start playing.  If a file is well-formed (with metadata at the
+beginning of a file), nginx just sends back the file contents.
 Otherwise, it has to read the file and prepare a new stream so that
-metadata comes before media data.
+the metadata comes before the media data.
 This involves some CPU, memory, and disk I/O overhead,
 so it is a good idea to
 <link
@@ -64,7 +65,7 @@
 <para>
 For a matching request with a non-zero
 <literal>start</literal>
-argument, nginx will read metadata from the file, prepare the
+argument, nginx will read the metadata from the file, prepare the
 stream starting from the requested offset, and send it to a client.
 This has the same overhead as described above.
 </para>
@@ -82,13 +83,13 @@
 <literal>--with-http_mp4_module</literal>
 configuration parameter.
 <note>
-If a third-party mp4 module was previously used, it needs to be disabled.
+If a third-party mp4 module was previously used, it should be disabled.
 </note>
 </para>
 
 <para>
-A similar pseudo-streaming support for FLV files is provided by the module
-<link doc="ngx_http_flv_module.xml">ngx_http_flv_module</link>.
+A similar pseudo-streaming support for FLV files is provided by the
+<link doc="ngx_http_flv_module.xml">ngx_http_flv_module</link> module.
 </para>
 
 </section>
@@ -133,7 +134,7 @@
 <context>location</context>
 
 <para>
-Sets the initial size of a memory buffer used to process MP4 files.
+Sets the initial size of a memory buffer used for processing MP4 files.
 </para>
 
 </directive>
@@ -149,9 +150,9 @@
 <para>
 During metadata processing, a larger buffer may become necessary.
 Its size cannot exceed the specified <value>size</value>,
-or else nginx will return the server error
-<http-status code="500" text="Internal Server Error"/>,
-and log the following:
+or else nginx will return the
+<http-status code="500" text="Internal Server Error"/> server error,
+and log the following message:
 <example>
 "/some/movie/file.mp4" mp4 moov atom is too large:
 12583268, you may want to increase mp4_max_buffer_size

--- a/xml/en/docs/http/ngx_http_perl_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_perl_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -15,8 +15,8 @@
 <section id="summary">
 
 <para>
-The <literal>ngx_http_perl_module</literal> module allows to implement
-location and variable handlers in Perl, and to insert Perl calls into SSI.
+The <literal>ngx_http_perl_module</literal> module is used to implement
+location and variable handlers in Perl and insert Perl calls into SSI.
 </para>
 
 <para>
@@ -25,7 +25,7 @@
 configuration parameter.
 <note>
 This module requires Perl version 5.6.1 or higher.
-The C compiler should be compatible with that used to build Perl.
+The C compiler should be compatible with the one used to build Perl.
 </note>
 </para>
 
@@ -40,11 +40,11 @@
 
 <para>
 In order for Perl to recompile the modified modules during
-reconfiguration, it needs to be built with the parameters
+reconfiguration, it should be built with the
 <literal>-Dusemultiplicity=yes</literal> or
-<literal>-Dusethreads=yes</literal>.
-Also, in order for Perl to leak less memory at run time,
-it needs to be built with the
+<literal>-Dusethreads=yes</literal> parameters.
+Also, to make Perl leak less memory at run time,
+it should be built with the
 <literal>-Dusemymalloc=no</literal> parameter.
 To check the values of these parameters in an already built
 Perl (preferred values are specified in the example), run:
@@ -56,40 +56,40 @@
 </para>
 
 <para>
-Note that after rebuilding Perl with the new parameters
+Note that after rebuilding Perl with the new
 <literal>-Dusemultiplicity=yes</literal> or
-<literal>-Dusethreads=yes</literal>,
+<literal>-Dusethreads=yes</literal> parameters,
 all binary Perl modules will have to be rebuilt as well —
 they will just stop working with the new Perl.
 </para>
 
 <para>
-It is possible for the main process and then worker processes
-to grow in size after every reconfiguration.
+There is a possibility that the main process and then worker processes will
+grow in size after every reconfiguration.
 If the main process grows to an unacceptable size, the
 <link doc="../control.xml" id="upgrade">live upgrade</link>
-procedure can be applied without changing an executable file.
+procedure can be applied without changing the executable file.
 </para>
 
 <para>
-While a Perl module performs long term operation, for example, resolves
-a domain name, connects to another server, queries a database,
-other requests assigned to this worker process will not be processed.
-It is thus recommended to limit the work done to operations
-that have predictable and short execution time, for example,
-access local file system.
+While the Perl module is performing a long-running operation, such as
+resolving a domain name, connecting to another server, or querying a database,
+other requests assigned to the current worker process will not be processed.
+It is thus recommended to perform only such operations
+that have predictable and short execution time, such as
+accessing the local file system.
 </para>
 
 <para>
-The below mentioned issues only affect versions of nginx before 0.6.22.
+The issues mentioned below affect only the nginx versions before 0.6.22.
 
 <note>
-Data returned by the <literal>$r</literal> request object methods
-only has a text value, and the value itself is stored in memory
+The <literal>$r</literal> request object methods return
+data only as a string value, and the value itself is stored in memory
 allocated by nginx from its own pools, not by Perl.
-This allows to reduce the number of copy operations involved in
-most cases, however it can lead to errors in some cases.
-For example, a worker process trying to use such a data in the
+This helps to reduce the number of copy operations involved in
+most cases; however it can lead to errors in some cases.
+For example, a worker process trying to use such data in the
 numeric context will terminate with an error (FreeBSD):
 <example>
 nginx in realloc(): warning: pointer to wrong page
@@ -102,7 +102,7 @@
 Out of memory!
 Callback called exit.
 </example>
-The workaround is simple — a method’s value should be assigned
+The workaround is simple — the method’s value should be assigned
 to a variable.
 For example, the following code
 <example>
@@ -121,8 +121,8 @@
 object methods (except for the <literal>$r->filename</literal> and
 <literal>$r->request_body_file</literal> methods).
 Thus, such values cannot be used as filenames and the likes.
-The workaround is similar to a previous case — the value should either be
-assigned to a variable (this results in data copying that in turn adds
+The workaround is similar to the previous case — the value should either be
+assigned to a variable (this results in data copying and adding of
 the necessary null character) or used in an expression, for example:
 <example>
 open FILE, '/path/' . $r->variable('name');
@@ -203,7 +203,7 @@
 <context>limit_except</context>
 
 <para>
-Installs a Perl handler for the given location.
+Sets a Perl handler for the given location.
 </para>
 
 </directive>
@@ -229,7 +229,7 @@
 <para>
 Defines the name of a module that will be loaded during each
 reconfiguration.
-There could be several <literal>perl_require</literal> directives.
+Several <literal>perl_require</literal> directives can be present.
 </para>
 
 </directive>
@@ -284,9 +284,9 @@
 </tag-name>
 <tag-desc>
 returns 0 if there is no body in a request.
-If there is a body, the specified handler is installed
+If there is a body, the specified handler is set for the request
 and 1 is returned.
-After reading the request body, nginx will call the installed handler.
+After reading the request body, nginx will call the specified handler.
 Note that the handler function should be passed by reference.
 Example:
 <example>
@@ -332,17 +332,18 @@
 
 <tag-name><literal>$r->discard_request_body</literal></tag-name>
 <tag-desc>
-instructs nginx to discard a request body.
+instructs nginx to discard the request body.
 </tag-desc>
 
 <tag-name><literal>$r->header_in(<value>field</value>)</literal></tag-name>
 <tag-desc>
-returns value of the specified client request header field.
+returns the value of the specified client request header field.
 </tag-desc>
 
 <tag-name><literal>$r->header_only</literal></tag-name>
 <tag-desc>
-determines should the whole response or only its header be sent to a client.
+determines whether the whole response or only its header should be sent to
+the client.
 </tag-desc>
 
 <tag-name>
@@ -358,9 +359,9 @@
 </tag-name>
 <tag-desc>
 does an internal redirect to the specified <value>uri</value>.
-An actual redirect happens after the Perl handler has completed.
+An actual redirect happens after the Perl handler execution is completed.
 <note>
-Redirections to named locations are not currently supported.
+Redirections to named locations are currently not supported.
 </note>
 </tag-desc>
 
@@ -380,37 +381,37 @@
 
 <tag-name><literal>$r->request_body</literal></tag-name>
 <tag-desc>
-returns a client request body if it was not
+returns the client request body if it has not been
 written to a temporary file.
-To ensure that a client request body is in memory,
-its size should be limited with
+To ensure that the client request body is in memory,
+its size should be limited by
 <link doc="ngx_http_core_module.xml" id="client_max_body_size"/>,
-and a sufficient buffer size should be set with
+and a sufficient buffer size should be set using
 <link doc="ngx_http_core_module.xml" id="client_body_buffer_size"/>.
 </tag-desc>
 
 <tag-name><literal>$r->request_body_file</literal></tag-name>
 <tag-desc>
-returns the name of a file with the client request body.
-At the end of processing, the file needs to be removed.
+returns the name of the file with the client request body.
+After the processing, the file should be removed.
 To always write a request body to a file,
 <link doc="ngx_http_core_module.xml" id="client_body_in_file_only"/>
-needs to be enabled.
+should be enabled.
 </tag-desc>
 
 <tag-name><literal>$r->request_method</literal></tag-name>
 <tag-desc>
-returns client request HTTP method.
+returns the client request HTTP method.
 </tag-desc>
 
 <tag-name><literal>$r->remote_addr</literal></tag-name>
 <tag-desc>
-returns client IP address.
+returns the client IP address.
 </tag-desc>
 
 <tag-name><literal>$r->flush</literal></tag-name>
 <tag-desc>
-immediately sends data to a client.
+immediately sends data to the client.
 </tag-desc>
 
 <tag-name>
@@ -419,9 +420,9 @@
     <value>length</value>]])</literal>
 </tag-name>
 <tag-desc>
-sends the specified file content to a client.
+sends the specified file content to the client.
 Optional parameters
-specify an initial offset and length of data to be transmitted.
+specify the initial offset and length of the data to be transmitted.
 The actual data transmission happens after the Perl handler
 has completed.
 </tag-desc>
@@ -430,11 +431,11 @@
     <literal>$r->send_http_header([<value>type</value>])</literal>
 </tag-name>
 <tag-desc>
-sends the response header to a client.
-An optional <value>type</value> parameter sets the value of
+sends the response header to the client.
+The optional <value>type</value> parameter sets the value of
 the <header>Content-Type</header> response header field.
 If the value is an empty string, the <header>Content-Type</header>
-header field will not be passed.
+header field will not be sent.
 </tag-desc>
 
 <tag-name><literal>$r->status(<value>code</value>)</literal></tag-name>
@@ -500,7 +501,7 @@
     <value>value</value>])</literal>
 </tag-name>
 <tag-desc>
-returns or sets a value of the specified variable.
+returns or sets the value of the specified variable.
 Variables are local to each request.
 </tag-desc>
 

--- a/xml/en/docs/http/ngx_http_proxy_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_proxy_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -48,12 +48,12 @@
 <appeared-in>0.8.22</appeared-in>
 
 <para>
-Makes outgoing connections to a proxied server to originate
+Makes outgoing connections to a proxied server originate
 from the specified local IP <value>address</value>.
-Value of the parameter can contain variables (1.3.12).
+Parameter value can contain variables (1.3.12).
 The special value <literal>off</literal> (1.3.12) cancels the effect
 of the <literal>proxy_bind</literal> directive
-inherited from the previous configuration level, allowing the
+inherited from the previous configuration level, which allows the
 system to auto-assign the local IP address.
 </para>
 
@@ -324,9 +324,10 @@
 
 <para>
 A cached response is first written to a temporary file,
-then the file is renamed.
+and then the file is renamed.
 Starting from version 0.8.9, temporary files and the cache can be put on
-different file systems, but be aware that in this case a file is copied
+different file systems.
+However, be aware that in this case a file is copied
 across two file systems instead of the cheap renaming operation.
 It is thus recommended that for any given location both cache and a directory
 holding temporary files, set by the <link id="proxy_temp_path"/> directive,
@@ -386,7 +387,7 @@
 
 <para>
 Determines in which cases a stale cached response can be used
-when an error occurs in working with the proxied server.
+when an error occurs during communication with the proxied server.
 The directive’s parameters match the parameters of the
 <link id="proxy_next_upstream"/> directive.
 </para>
@@ -421,7 +422,7 @@
 proxy_cache_valid 200 302 10m;
 proxy_cache_valid 404      1m;
 </example>
-set 10 minutes of caching for responses with codes 200 and 302,
+set 10 minutes of caching for responses with codes 200 and 302
 and 1 minute for responses with code 404.
 </para>
 
@@ -449,7 +450,7 @@
 This has higher priority than setting of caching time using the directive.
 The <header>X-Accel-Expires</header> header field sets caching time of a
 response in seconds.
-The 0 value disables caching for a response.
+The zero value disables caching for a response.
 If a value starts with the <literal>@</literal> prefix, it sets an absolute
 time in seconds since Epoch, up to which the response may be cached.
 If header does not include the <header>X-Accel-Expires</header> field,
@@ -775,7 +776,7 @@
 <para>
 Determines whether proxied responses with codes greater than or equal
 to 300 should be passed to a client or be redirected to nginx for processing
-by the <link doc="ngx_http_core_module.xml" id="error_page"/> directive.
+with the <link doc="ngx_http_core_module.xml" id="error_page"/> directive.
 </para>
 
 </directive>
@@ -792,7 +793,7 @@
 When <link id="proxy_buffering">buffering</link> of responses from the proxied
 server is enabled, and the whole response does not fit into the memory buffers
 set by the <link id="proxy_buffer_size"/> and <link id="proxy_buffers"/>
-directives, a part of a response can be saved to a temporary file.
+directives, a part of the response can be saved to a temporary file.
 This directive sets the maximum <value>size</value> of a temporary file.
 The size of data written to a temporary file at a time is set
 by the <link id="proxy_temp_file_write_size"/> directive.
@@ -1072,7 +1073,7 @@
 
 <para>
 Defines a timeout for reading a response from the proxied server.
-A timeout is only set between two successive read operations,
+A timeout is set only between two successive read operations,
 not for the transmission of the whole response.
 If a proxied server does not transmit anything within this time,
 a connection is closed.
@@ -1089,7 +1090,7 @@
 <context>location</context>
 
 <para>
-Allows disabling a passing of the original request body
+Indicates whether the original request body is passed
 to the proxied server.
 <example>
 location /x-accel-redirect-here/ {
@@ -1115,7 +1116,7 @@
 <context>location</context>
 
 <para>
-Allows disabling a passing of the header fields of the original request
+Indicates whether the header fields of the original request are passed
 to the proxied server.
 <example>
 location /x-accel-redirect-here/ {
@@ -1277,7 +1278,7 @@
 
 <para>
 Sets a timeout for transmitting a request to the proxied server.
-A timeout is only set between two successive write operations,
+A timeout is set only between two successive write operations,
 not for the transmission of the whole request.
 If a proxied server does not receive anything within this time,
 a connection is closed.
@@ -1406,14 +1407,14 @@
 <para>
 The modification time of files is set according to the received
 <header>Last-Modified</header> response header field.
-A response is first written to a temporary file, then a file is renamed.
+A response is first written to a temporary file, and then the file is renamed.
 Starting from version 0.8.9, temporary files and the persistent store
-can be put on different file systems, but be aware that in this case
-a file is copied across two file systems instead of the cheap renaming
-operation.
+can be put on different file systems.
+However, be aware that in this case a file is copied
+across two file systems instead of the cheap renaming operation.
 It is thus recommended that for any given location both saved files and a
-directory holding temporary files set by the <link id="proxy_temp_path"/>
-directive are put on the same file system.
+directory holding temporary files, set by the <link id="proxy_temp_path"/>
+directive, are put on the same file system.
 </para>
 
 <para>

--- a/xml/en/docs/http/ngx_http_random_index_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_random_index_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -17,8 +17,8 @@
 <para>
 The <literal>ngx_http_random_index_module</literal> module processes requests
 ending with the slash character (‘<literal>/</literal>’) and picks a random
-file in a directory as an index file.
-It works before the
+file in a directory to serve as an index file.
+The module is processed before the
 <link doc="ngx_http_index_module.xml">ngx_http_index_module</link>
 module.
 </para>

--- a/xml/en/docs/http/ngx_http_realip_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_realip_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -15,7 +15,7 @@
 <section id="summary">
 
 <para>
-The <literal>ngx_http_realip_module</literal> module allows
+The <literal>ngx_http_realip_module</literal> module is used
 to change the client address to the one sent in the specified header field.
 </para>
 

--- a/xml/en/docs/http/ngx_http_referer_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_referer_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -15,7 +15,7 @@
 <section id="summary">
 
 <para>
-The <literal>ngx_http_referer_module</literal> module allows to block
+The <literal>ngx_http_referer_module</literal> module is used to block
 access to a site for requests with invalid values in the
 <header>Referer</header> header field.
 It should be kept in mind that fabricating a request with an appropriate
@@ -57,7 +57,7 @@
 
 <para>
 Sets the bucket size for the valid referers hash tables.
-Details of setting up hash tables are provided in a separate
+The details of setting up hash tables are provided in a separate
 <link doc="../hash.xml">document</link>.
 </para>
 
@@ -73,7 +73,7 @@
 
 <para>
 Sets the maximum <value>size</value> of the valid referers hash tables.
-Details of setting up hash tables are provided in a separate
+The details of setting up hash tables are provided in a separate
 <link doc="../hash.xml">document</link>.
 </para>
 
@@ -92,8 +92,8 @@
 <context>location</context>
 
 <para>
-Specifies values of the <header>Referer</header> request header field
-that will cause the embedded variable <var>$invalid_referer</var> to
+Specifies the <header>Referer</header> request header field values
+that will cause the embedded <var>$invalid_referer</var> variable to
 be set to an empty string.
 Otherwise, the variable will be set to “<literal>1</literal>”.
 Search for a match is case-insensitive.
@@ -111,8 +111,8 @@
 <tag-name><literal>blocked</literal></tag-name>
 <tag-desc>
 the <header>Referer</header> field is present in the request header,
-but its value was deleted by a firewall or proxy server;
-such values are strings that do not start from
+but its value has been deleted by a firewall or proxy server;
+such values are strings that do not start with
 “<literal>http://</literal>” or “<literal>https://</literal>”;
 </tag-desc>
 
@@ -126,7 +126,7 @@
 <tag-desc>
 defines a server name and an optional URI prefix.
 A server name can have an “<literal>*</literal>” at the beginning or end.
-When checking, the server’s port in the <header>Referer</header> field
+During the checking, the server’s port in the <header>Referer</header> field
 is ignored;
 </tag-desc>
 

--- a/xml/en/docs/http/ngx_http_rewrite_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_rewrite_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -15,7 +15,7 @@
 <section id="summary">
 
 <para>
-The <literal>ngx_http_rewrite_module</literal> module allows to
+The <literal>ngx_http_rewrite_module</literal> module is used to
 change URIs using regular expressions, return redirects, and
 conditionally select configurations.
 </para>
@@ -36,11 +36,11 @@
 
 <listitem>
 the directives of this module specified in the selected
-<link doc="ngx_http_core_module.xml" id="location"/> are processed,
-and if they changed a URI, a new location is searched for the new URI.
+<link doc="ngx_http_core_module.xml" id="location"/> are processed.
+If they have been changing a URI, a new location is searched for the new URI.
 This cycle may be repeated up to
 <link doc="ngx_http_core_module.xml" id="internal">10 times</link>
-after which the error <http-status code="500" text="Internal Server Error"/>
+after which the <http-status code="500" text="Internal Server Error"/> error
 is returned.
 </listitem>
 
@@ -85,8 +85,8 @@
 
 <para>
 The specified <value>condition</value> is evaluated.
-If true, the directives of this module specified inside the braces are
-executed, and a request is assigned the configuration inside the
+If true, this module directives specified inside the braces are
+executed, and the request is assigned the configuration inside the
 <literal>if</literal> directive.
 Configurations inside the <literal>if</literal> directives are
 inherited from the previous configuration level.
@@ -106,40 +106,40 @@
 </listitem>
 
 <listitem>
-comparing a variable with a string using the
+comparison of a variable with a string using the
 “<literal>=</literal>” and “<literal>!=</literal>” operators;
 </listitem>
 
 <listitem>
-matching a variable against a regular expression using the
+matching of a variable against a regular expression using the
 “<literal>~</literal>” (for case-sensitive matching) and
 “<literal>~*</literal>” (for case-insensitive matching) operators.
 Regular expressions can contain captures that are made available for
 later reuse in the <var>$1</var>..<var>$9</var> variables.
 Negative operators “<literal>!~</literal>” and “<literal>!~*</literal>”
 are also available.
-If a regular expression includes the characters “<literal>}</literal>”
-or “<literal>;</literal>”, the whole expression should be enclosed
+If a regular expression includes the “<literal>}</literal>”
+or “<literal>;</literal>” characters, the whole expressions should be enclosed
 in single or double quotes.
 </listitem>
 
 <listitem>
-checking a file existence with the “<literal>-f</literal>” and
+checking of a file existence with the “<literal>-f</literal>” and
 “<literal>!-f</literal>” operators;
 </listitem>
 
 <listitem>
-checking a directory existence with the “<literal>-d</literal>” and
+checking of a directory existence with the “<literal>-d</literal>” and
 “<literal>!-d</literal>” operators;
 </listitem>
 
 <listitem>
-checking a file, directory, or symbolic link existence with the
+checking of a file, directory, or symbolic link existence with the
 “<literal>-e</literal>” and “<literal>!-e</literal>” operators;
 </listitem>
 
 <listitem>
-checking for an executable file with operators “<literal>-x</literal>”
+checking for an executable file with the “<literal>-x</literal>”
 and “<literal>!-x</literal>” operators.
 </listitem>
 
@@ -170,7 +170,7 @@
 }
 </example>
 <note>
-A value of the embedded variable <var>$invalid_referer</var> is set by the
+A value of the <var>$invalid_referer</var> embedded variable is set by the
 <link doc="ngx_http_referer_module.xml" id="valid_referers"/> directive.
 </note>
 </para>
@@ -195,11 +195,11 @@
 
 <para>
 Starting from version 0.8.42, it is possible to specify
-either the URL of redirect (for codes 301, 302, 303, and 307),
-or the <value>text</value> of a response body (for other codes).
-A response body text or URL of redirect can contain variables.
-As a special case, a URL of redirect can be specified as a URI
-local to this server, in which case the full URL of redirect
+either a redirect URL (for codes 301, 302, 303, and 307),
+or the response body <value>text</value> (for other codes).
+A response body text and redirect URL can contain variables.
+As a special case, a redirect URL can be specified as a URI
+local to this server, in which case the full redirect URL
 is formed according to the request scheme (<var>$scheme</var>) and the
 <link doc="ngx_http_core_module.xml" id="server_name_in_redirect"/> and
 <link doc="ngx_http_core_module.xml" id="port_in_redirect"/> directives.
@@ -208,8 +208,8 @@
 <para>
 In addition, a <value>URL</value> for temporary redirect with the code 302
 can be specified as the sole parameter.
-Such a parameter should start with the string “<literal>http://</literal>”,
-“<literal>https://</literal>”, or “<literal>$scheme</literal>”.
+Such a parameter should start with the “<literal>http://</literal>”,
+“<literal>https://</literal>”, or “<literal>$scheme</literal>” string.
 A <value>URL</value> can contain variables.
 </para>
 
@@ -242,9 +242,9 @@
 as specified in the <value>replacement</value> string.
 The <literal>rewrite</literal> directives are executed sequentially
 in order of their appearance in the configuration file.
-Flags make it possible to terminate further processing of directives.
+It is possible to terminate further processing of the directives using flags.
 If a replacement string starts with “<literal>http://</literal>”
-or “<literal>https://</literal>”, the processing stops and a
+or “<literal>https://</literal>”, the processing stops and the
 redirect is returned to a client.
 </para>
 
@@ -255,8 +255,8 @@
 <tag-name><literal>last</literal></tag-name>
 <tag-desc>
 stops processing the current set of
-<literal>ngx_http_rewrite_module</literal> directives
-followed by a search for a new location matching the changed URI;
+<literal>ngx_http_rewrite_module</literal> directives and starts
+a search for a new location matching the changed URI;
 </tag-desc>
 
 <tag-name><literal>break</literal></tag-name>
@@ -267,18 +267,18 @@
 
 <tag-name><literal>redirect</literal></tag-name>
 <tag-desc>
-returns a temporary redirect with the code 302;
+returns a temporary redirect with the 302 code;
 used if a replacement string does not start with
 “<literal>http://</literal>” or “<literal>https://</literal>”;
 </tag-desc>
 
 <tag-name><literal>permanent</literal></tag-name>
 <tag-desc>
-returns a permanent redirect with the code 301.
+returns a permanent redirect with the 301 code.
 </tag-desc>
 
 </list>
-The full URL of redirects is formed according to the
+The full redirect URL is formed according to the
 request scheme (<var>$scheme</var>) and the
 <link doc="ngx_http_core_module.xml" id="server_name_in_redirect"/> and
 <link doc="ngx_http_core_module.xml" id="port_in_redirect"/> directives.
@@ -300,8 +300,8 @@
 <para>
 But if these directives are put inside the “<literal>/download/</literal>”
 location, the <literal>last</literal> flag should be replaced by
-<literal>break</literal>, otherwise nginx will make 10 cycles and
-return the error 500:
+<literal>break</literal>, or otherwise nginx will make 10 cycles and
+return the 500 error:
 <example>
 location /download/ {
     rewrite ^(/download/.*)/media/(.*)\..*$ $1/mp3/$2.mp3 break;
@@ -322,8 +322,8 @@
 </para>
 
 <para>
-If a regular expression includes the characters “<literal>}</literal>”
-or “<literal>;</literal>”, the whole expression should be enclosed
+If a regular expression includes the “<literal>}</literal>”
+or “<literal>;</literal>” characters, the whole expressions should be enclosed
 in single or double quotes.
 </para>
 
@@ -384,7 +384,7 @@
 
 <para>
 The <literal>ngx_http_rewrite_module</literal> module directives
-are compiled during the configuration stage into internal instructions
+are compiled at the configuration stage into internal instructions
 that are interpreted during request processing.
 An interpreter is a simple virtual stack machine.
 </para>

--- a/xml/en/docs/http/ngx_http_secure_link_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_secure_link_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -16,29 +16,29 @@
 
 <para>
 The <literal>ngx_http_secure_link_module</literal> module (0.7.18)
-allows to check authenticity of requested links,
+is used to check authenticity of requested links,
 protect resources from unauthorized access,
-and limit lifetime of links.
+and limit link lifetime.
 </para>
 
 <para>
 The authenticity of a requested link is verified by comparing the
 checksum value passed in a request with the value computed
 for the request.
-If link has a limited lifetime and the time has expired,
+If a link has a limited lifetime and the time has expired,
 the link is considered outdated.
-Status of these checks is made available in the
+The status of these checks is made available in the
 <var>$secure_link</var> variable.
 </para>
 
 <para>
 The module provides two alternative operation modes.
 The first mode is enabled by the <link id="secure_link_secret"/>
-directive and allows to check authenticity of requested links
+directive and is used to check authenticity of requested links
 as well as protect resources from unauthorized access.
 The second mode (0.8.50) is enabled by the
 <link id="secure_link"/> and <link id="secure_link_md5"/>
-directives, and also allows to limit lifetime of links.
+directives and is also used to limit lifetime of links.
 </para>
 
 <para>
@@ -61,7 +61,7 @@
 
 <para>
 Defines a string with variables from which the
-checksum value and lifetime of a link are to be extracted.
+checksum value and lifetime of a link will be extracted.
 </para>
 
 <para>
@@ -70,28 +70,28 @@
 </para>
 
 <para>
-Checksum value extracted from the string is compared with
-MD5 hash value computed for expression defined by the
+The checksum value extracted from the string is compared with
+the MD5 hash value of the expression defined by the
 <link id="secure_link_md5"/> directive.
-If checksums are different, the <var>$secure_link</var> variable
+If the checksums are different, the <var>$secure_link</var> variable
 is set to an empty string.
-If checksums are the same, lifetime of a link is checked.
-If link has a limited lifetime and the time has expired,
+If the checksums are the same, the link lifetime is checked.
+If the link has a limited lifetime and the time has expired,
 the <var>$secure_link</var> variable is set to “<literal>0</literal>”.
 Otherwise, it is set to “<literal>1</literal>”.
-MD5 hash value passed in a request is encoded in
+The MD5 hash value passed in a request is encoded in
 <link url="http://tools.ietf.org/html/rfc4648#section-5">base64url</link>.
 </para>
 
 <para>
-If link has a limited lifetime, an expiration time
+If a link has a limited lifetime, the expiration time
 is set in seconds since Epoch (Thu, 01 Jan 1970 00:00:00 GMT).
-The value is specified in an expression after MD5 hash,
-and is separated by comma.
-An expiration time passed in a request is made available in
-the <var>$secure_link_expires</var> variable for use in
+The value is specified in the expression after the MD5 hash,
+and is separated by a comma.
+The expiration time passed in a request is available through
+the <var>$secure_link_expires</var> variable for a use in
 the <link id="secure_link_md5"/> directive.
-If expiration time is not specified, a link has unlimited
+If the expiration time is not specified, a link has the unlimited
 lifetime.
 </para>
 
@@ -106,21 +106,20 @@
 <context>location</context>
 
 <para>
-Defines an expression for which the MD5 hash value is to
+Defines an expression for which the MD5 hash value will
 be computed and compared with the value passed in a request.
 </para>
 
 <para>
-An expression should contain the secured part of a link (resource)
+The expression should contain the secured part of a link (resource)
 and a secret ingredient.
-If link has a limited lifetime,
-an expression should also contain <var>$secure_link_expires</var>.
+If the link has a limited lifetime,
+the expression should also contain <var>$secure_link_expires</var>.
 </para>
 
 <para>
-To prevent unauthorized access, an expression may contain some
-information about the client, such as its address and version
-of the browser.
+To prevent unauthorized access, the expression may contain some
+information about the client, such as its address and browser version.
 </para>
 
 <para>
@@ -141,11 +140,12 @@
     ...
 }
 </example>
-The link
+The
 “<literal>/s/link?md5=_e4Nc3iduzkWRm01TBBNYw&amp;expires=2147483647</literal>”
-restricts access to “<literal>/s/link</literal>” for the client with IP address
-127.0.0.1.
-The link also has a limited lifetime until January 19, 2038 (GMT).
+link
+restricts access to “<literal>/s/link</literal>” for the client with the
+IP address 127.0.0.1.
+The link also has the limited lifetime until January 19, 2038 (GMT).
 </para>
 
 <para>
@@ -174,13 +174,13 @@
 <example>
 /<value>prefix</value>/<value>hash</value>/<value>link</value>
 </example>
-where <value>hash</value> is a hexadecimal representation of an
-MD5 hash computed for the concatenation of link and secret word,
+where <value>hash</value> is a hexadecimal representation of the
+MD5 hash computed for the concatenation of the link and secret word,
 and <value>prefix</value> is an arbitrary string without slashes.
 </para>
 
 <para>
-If requested link passes the authenticity check,
+If the requested link passes the authenticity check,
 the <var>$secure_link</var> variable is set to the link
 extracted from the request URI.
 Otherwise, the <var>$secure_link</var> variable
@@ -228,13 +228,13 @@
 
 <tag-name><var>$secure_link</var></tag-name>
 <tag-desc>
-Status of a link check.
+The status of a link check.
 The specific value depends on the selected operation mode.
 </tag-desc>
 
 <tag-name><var>$secure_link_expires</var></tag-name>
 <tag-desc>
-Lifetime of a link passed in a request;
+The lifetime of a link passed in a request;
 intended to be used only in the
 <link id="secure_link_md5"/> directive.
 </tag-desc>

--- a/xml/en/docs/http/ngx_http_spdy_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_spdy_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -82,9 +82,9 @@
 <context>server</context>
 
 <para>
-Sets a header compression <value>level</value> of a response in a range from
+Sets the header compression <value>level</value> of a response in a range from
 1 (fastest, less compression) to 9 (slowest, best compression).
-The special value 0 turns off header compression.
+The special value 0 turns off the header compression.
 </para>
 
 </directive>

--- a/xml/en/docs/http/ngx_http_split_clients_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_split_clients_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -62,8 +62,8 @@
 </example>
 The value of the original string is hashed using MurmurHash2.
 In the example given, hash values from 0 to 21474835 (0.5%)
-correspond to the <var>$variant</var> variable taking the
-value <literal>".one"</literal>,
+correspond to the
+value <literal>".one"</literal> of the <var>$variant</var> variable,
 hash values from 21474836 to 107374180 (2%) correspond to
 the value <literal>".two"</literal>,
 and hash values from 107374181 to 4294967295 correspond to

--- a/xml/en/docs/http/ngx_http_ssi_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_ssi_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -64,7 +64,7 @@
 <appeared-in>1.5.1</appeared-in>
 
 <para>
-Allows to preserve the <header>Last-Modified</header> header field
+Allows preserving the <header>Last-Modified</header> header field
 from the original response during SSI processing
 to facilitate response caching.
 </para>
@@ -102,9 +102,9 @@
 <context>location</context>
 
 <para>
-Allows to suppress output of the string
+If enabled, suppresses the output of the
 “<literal>[an error occurred while processing the directive]</literal>”
-if an error occurred during SSI processing.
+string if an error occurred during SSI processing.
 </para>
 
 </directive>
@@ -134,7 +134,7 @@
 <context>location</context>
 
 <para>
-Sets the maximum length for values of parameters in SSI commands.
+Sets the maximum length of parameter values in SSI commands.
 </para>
 
 </directive>
@@ -216,12 +216,12 @@
 <list type="tag">
 <tag-name><literal>var</literal></tag-name>
 <tag-desc>
-variable name.
+the variable name.
 </tag-desc>
 
 <tag-name><literal>encoding</literal></tag-name>
 <tag-desc>
-encoding method.
+the encoding method.
 Possible values include <literal>none</literal>, <literal>url</literal>, and
 <literal>entity</literal>.
 By default, <literal>entity</literal> is used.
@@ -229,7 +229,7 @@
 
 <tag-name><literal>default</literal></tag-name>
 <tag-desc>
-non-standard parameter that sets a string to be output
+a non-standard parameter that sets a string to be output
 if a variable is undefined.
 By default, “<literal>none</literal>” is output.
 The command
@@ -339,9 +339,9 @@
 
 <tag-name><literal>stub</literal></tag-name>
 <tag-desc>
-non-standard parameter that names the block whose
-content will be output if an included request results in an empty
-body or if an error occurs during request processing, for example:
+a non-standard parameter that names the block whose
+content will be output if the included request results in an empty
+body or if an error occurs during the request processing, for example:
 <example>
 &lt;!--# block name="one" --&gt;&amp;nbsp;&lt;!--# endblock --&gt;
 &lt;!--# include virtual="/remote/body.php?argument=value" stub="one" --&gt;
@@ -351,7 +351,7 @@
 
 <tag-name><literal>wait</literal></tag-name>
 <tag-desc>
-non-standard parameter that instructs to wait for a request to fully
+a non-standard parameter that instructs to wait for a request to fully
 complete before continuing with SSI processing, for example:
 <example>
 &lt;!--# include virtual="/remote/body.php?argument=value" wait="yes" --&gt;
@@ -360,7 +360,7 @@
 
 <tag-name><literal>set</literal></tag-name>
 <tag-desc>
-non-standard parameter that instructs to write a successful result
+a non-standard parameter that instructs to write a successful result
 of request processing to the specified variable,
 for example:
 <example>
@@ -385,12 +385,12 @@
 <list type="tag">
 <tag-name><literal>var</literal></tag-name>
 <tag-desc>
-variable name.
+the variable name.
 </tag-desc>
 
 <tag-name><literal>value</literal></tag-name>
 <tag-desc>
-variable value.
+the variable value.
 If an assigned value contains variables,
 their values are substituted.
 </tag-desc>
@@ -413,7 +413,7 @@
 
 <tag-name><var>$date_local</var></tag-name>
 <tag-desc>
-current time in local time zone.
+current time in the local time zone.
 The format is set by the <literal>config</literal> command
 with the <literal>timefmt</literal> parameter.
 </tag-desc>

--- a/xml/en/docs/http/ngx_http_ssl_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_ssl_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -47,11 +47,11 @@
 </listitem>
 
 <listitem>
-enable shared session cache,
+enable the shared session cache,
 </listitem>
 
 <listitem>
-disable built-in session cache,
+disable the built-in session cache,
 </listitem>
 
 <listitem>
@@ -113,7 +113,7 @@
 <context>server</context>
 
 <para>
-Specifies a <value>file</value> with a certificate in the PEM format
+Specifies a <value>file</value> with the certificate in the PEM format
 for the given virtual server.
 If intermediate certificates should be specified in addition
 to a primary certificate, they should be specified in the same file
@@ -156,7 +156,7 @@
 <context>server</context>
 
 <para>
-Specifies a <value>file</value> with a secret key in the PEM format
+Specifies a <value>file</value> with the secret key in the PEM format
 for the given virtual server.
 </para>
 
@@ -271,13 +271,13 @@
 
 <para>
 Enables the specified protocols.
-The parameters <literal>TLSv1.1</literal> and <literal>TLSv1.2</literal> work
-only when using the OpenSSL library version 1.0.1 and higher.
+The <literal>TLSv1.1</literal> and <literal>TLSv1.2</literal> parameters work
+only when the OpenSSL library of version 1.0.1 or higher is used.
 <note>
-The parameters <literal>TLSv1.1</literal> and <literal>TLSv1.2</literal> are
-supported starting from versions 1.1.13 and 1.0.12
-so when using OpenSSL version 1.0.1
-and higher on older nginx versions these protocols will work but could not
+The <literal>TLSv1.1</literal> and <literal>TLSv1.2</literal> parameters are
+supported starting from versions 1.1.13 and 1.0.12,
+so when the OpenSSL version 1.0.1 or higher
+is used on older nginx versions, these protocols work, but cannot
 be disabled.
 </note>
 </para>
@@ -296,21 +296,21 @@
 <context>server</context>
 
 <para>
-Sets types and sizes of caches that store session parameters.
-A cache can be any of the following types:
+Sets the types and sizes of caches that store session parameters.
+A cache can be of any of the following types:
 <list type="tag">
 
 <tag-name><literal>off</literal></tag-name>
 <tag-desc>
-the use of session cache is strictly prohibited:
+the use of a session cache is strictly prohibited:
 nginx explicitly tells a client that sessions may not be reused.
 </tag-desc>
 
 <tag-name><literal>none</literal></tag-name>
 <tag-desc>
-the use of session cache is gently disallowed:
+the use of a session cache is gently disallowed:
 nginx tells a client that sessions may be reused, but does not
-actually do that.
+actually store session parameters in the cache.
 </tag-desc>
 
 <tag-name><literal>builtin</literal></tag-name>
@@ -323,7 +323,7 @@
 
 <tag-name><literal>shared</literal></tag-name>
 <tag-desc>
-shared between all worker processes.
+a cache shared between all worker processes.
 The cache size is specified in bytes; one megabyte can store
 about 4000 sessions.
 Each shared cache should have an arbitrary name.
@@ -378,19 +378,19 @@
 </para>
 
 <para>
-For the OCSP stapling to work, the certificate of the issuer of the server
-certificate should be known.
+For the OCSP stapling to work, the certificate of the server certificate
+issuer should be known.
 If the <link id="ssl_certificate"/> file does
 not contain intermediate certificates,
-the certificate of the issuer of the server certificate should be
+the certificate of the server certificate issuer should be
 present in the
 <link id="ssl_trusted_certificate"/> file.
 </para>
 
 <para>
-The <link doc="ngx_http_core_module.xml" id="resolver"/> directive
-should also be specified to allow for a resolution
-of an OCSP responder hostname.
+For a resolution of the OCSP responder hostname,
+the <link doc="ngx_http_core_module.xml" id="resolver"/> directive
+should also be specified.
 </para>
 
 </directive>
@@ -425,7 +425,7 @@
 <appeared-in>1.3.7</appeared-in>
 
 <para>
-Overrides the URL of OCSP responder specified in the
+Overrides the URL of the OCSP responder specified in the
 “<link url="http://tools.ietf.org/html/rfc5280#section-4.2.2.1">Authority
 Information Access</link>” certificate extension.
 </para>
@@ -452,8 +452,8 @@
 </para>
 
 <para>
-For verification to work, the certificate of the issuer of the server
-certificate, the root certificate, and all intermediate certificates
+For verification to work, the certificate of the server certificate
+issuer, the root certificate, and all intermediate certificates
 should be configured as trusted using the
 <link id="ssl_trusted_certificate"/> directive.
 </para>
@@ -475,8 +475,8 @@
 </para>
 
 <para>
-In contrast to <link id="ssl_client_certificate"/>, the list of these
-certificates will not be sent to clients.
+In contrast to the certificate set by <link id="ssl_client_certificate"/>,
+the list of these certificates will not be sent to clients.
 </para>
 
 </directive>
@@ -492,22 +492,22 @@
 
 <para>
 Enables verification of client certificates.
-The result of verification is stored in the
+The verification result is stored in the
 <var>$ssl_client_verify</var> variable.
 </para>
 
 <para>
 The <literal>optional</literal> parameter (0.8.7+) requests the client
-certificate, and if certificate was present, verifies it.
+certificate and verifies it if the certificate is present.
 </para>
 
 <para>
 The <literal>optional_no_ca</literal> parameter (1.3.8, 1.2.5)
 requests the client
 certificate but does not require it to be signed by a trusted CA certificate.
-This is intended for the use in cases where actual certificate verification
-is performed by a service that is external to nginx.
-The contents of a certificate is made available through the
+This is intended for the use in cases when a service that is external to nginx
+performs the actual certificate verification.
+The contents of the certificate is accessible through the
 <var>$ssl_client_cert</var> variable.
 </para>
 
@@ -521,7 +521,7 @@
 <context>server</context>
 
 <para>
-Sets a verification depth in the client certificates chain.
+Sets the verification depth in the client certificates chain.
 </para>
 
 </directive>
@@ -544,21 +544,21 @@
 
 <tag-name>496</tag-name>
 <tag-desc>
-a client did not present the required certificate;
+a client has not presented the required certificate;
 </tag-desc>
 
 <tag-name>497</tag-name>
 <tag-desc>
-a regular request was sent to the HTTPS port.
+a regular request has been sent to the HTTPS port.
 </tag-desc>
 
 </list>
 </para>
 
 <para>
-A redirection happens after the request was fully parsed and
-variables such as <var>$request_uri</var>,
-<var>$uri</var>, <var>$args</var> and others were made available.
+The redirection happens after the request is fully parsed and
+the variables, such as <var>$request_uri</var>,
+<var>$uri</var>, <var>$args</var> and others, are available.
 </para>
 
 </section>

--- a/xml/en/docs/http/ngx_http_status_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_status_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -14,7 +14,7 @@
 <section id="summary">
 
 <para>
-The module <literal>ngx_http_status_module</literal> provides
+The <literal>ngx_http_status_module</literal> module provides
 access to various status information.
 </para>
 

--- a/xml/en/docs/http/ngx_http_sub_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_sub_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -53,9 +53,9 @@
 <context>location</context>
 
 <para>
-Sets a string that needs to be changed, and a replacement string.
-The string to be replaced is matched ignoring the case.
-A replacement string can contain variables.
+Sets a string to replace and a replacement string.
+The string to replace is matched ignoring the case.
+The replacement string can contain variables.
 </para>
 
 </directive>
@@ -70,7 +70,7 @@
 <appeared-in>1.5.1</appeared-in>
 
 <para>
-Allows to preserve the <header>Last-Modified</header> header field
+Allows preserving the <header>Last-Modified</header> header field
 from the original response during replacement
 to facilitate response caching.
 </para>
@@ -91,8 +91,8 @@
 <context>location</context>
 
 <para>
-Determines how many times to look for a string to be replaced,
-once or several times.
+Indicates whether to look for a string to replace once or
+several times.
 </para>
 
 </directive>

--- a/xml/en/docs/http/ngx_http_upstream_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_upstream_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -16,8 +16,8 @@
 
 <para>
 The <literal>ngx_http_upstream_module</literal> module
-allows to define groups of servers that can be referenced
-from the <link doc="ngx_http_proxy_module.xml" id="proxy_pass"/>,
+is used to define groups of servers that can be referenced
+by the <link doc="ngx_http_proxy_module.xml" id="proxy_pass"/>,
 <link doc="ngx_http_fastcgi_module.xml" id="fastcgi_pass"/>, and
 <link doc="ngx_http_memcached_module.xml" id="memcached_pass"/> directives.
 </para>
@@ -105,16 +105,16 @@
 </para>
 
 <para>
-By default, requests are distributed between servers using a
+By default, requests are distributed between the servers using a
 weighted round-robin balancing method.
 In the above example, each 7 requests will be distributed as follows:
-5 requests to <literal>backend1.example.com</literal>
-and one request to each of second and third servers.
-If an error occurs when communicating with the server, a request will
+5 requests go to <literal>backend1.example.com</literal>
+and one request to each of the second and third servers.
+If an error occurs during communication with a server, the request will
 be passed to the next server, and so on until all of the functioning
 servers will be tried.
 If a successful response could not be obtained from any of the servers,
-the client will be returned the result of contacting the last server.
+the client will receive the result of the communication with the last server.
 </para>
 
 </directive>
@@ -126,14 +126,14 @@
 <context>upstream</context>
 
 <para>
-Defines an <value>address</value> and other <value>parameters</value>
-of the server.
-An address can be specified as a domain name or IP address,
-and an optional port, or as a UNIX-domain socket path
+Defines the <value>address</value> and other <value>parameters</value>
+of a server.
+The address can be specified as a domain name or IP address,
+with an optional port, or as a UNIX-domain socket path
 specified after the “<literal>unix:</literal>” prefix.
-If port is not specified, the port 80 is used.
-A domain name that resolves to several IP addresses essentially defines
-multiple servers.
+If a port is not specified, the port 80 is used.
+A domain name that resolves to several IP addresses defines
+multiple servers at once.
 </para>
 
 <para>
@@ -142,17 +142,17 @@
 
 <tag-name><literal>weight</literal>=<value>number</value></tag-name>
 <tag-desc>
-sets a weight of the server, by default 1.
+sets the weight of the server, by default, 1.
 </tag-desc>
 
 <tag-name><literal>max_fails</literal>=<value>number</value></tag-name>
 <tag-desc>
-sets a number of unsuccessful attempts to communicate with the server
-during a time set by the <literal>fail_timeout</literal> parameter
-after which it will be considered down for a period of time also set
-by the <literal>fail_timeout</literal> parameter.
+sets the number of unsuccessful attempts to communicate with the server
+that should happen in the duration set by the <literal>fail_timeout</literal>
+parameter to consider the server down for a duration also set by the
+<literal>fail_timeout</literal> parameter.
 By default, the number of unsuccessful attempts is set to 1.
-A value of zero disables accounting of attempts.
+The zero value disables the accounting of attempts.
 What is considered an unsuccessful attempt is defined by the
 <link doc="ngx_http_proxy_module.xml" id="proxy_next_upstream"/>,
 <link doc="ngx_http_fastcgi_module.xml" id="fastcgi_next_upstream"/>, and
@@ -166,17 +166,16 @@
 <list type="bullet">
 
 <listitem>
-a time during which the specified number of unsuccessful attempts to
-communicate with the server should happen for the server to be
-considered down;
+the time during which the specified number of unsuccessful attempts to
+communicate with the server should happen to consider the server down;
 </listitem>
 
 <listitem>
-and a period of time the server will be considered down.
+and the period of time the server will be considered down.
 </listitem>
 
 </list>
-By default, timeout is set to 10 seconds.
+By default, the parameter is set to 10 seconds.
 </tag-desc>
 
 <tag-name><literal>slow_start</literal>=<value>time</value></tag-name>
@@ -257,10 +256,10 @@
 are distributed between servers based on client IP addresses.
 The first three octets of the client IPv4 address, or the entire IPv6 address,
 are used as a hashing key.
-The method ensures that requests of the same client will always be
-passed to the same server except when this server is considered down
-in which case client requests will be passed to another server and
-most probably it will also be the same server.
+The method ensures that requests from the same client will always be
+passed to the same server except when this server is considered down.
+In the latter case client requests will be passed to another server.
+Most probably, it will always be the same server as well.
 <note>
 IPv6 addresses are supported starting from versions 1.3.2 and 1.2.2.
 </note>
@@ -288,7 +287,7 @@
 
 <para>
 <note>
-Until versions 1.3.1 and 1.2.2 it was not possible to specify a weight for
+Until versions 1.3.1 and 1.2.2, it was not possible to specify a weight for
 servers using the <literal>ip_hash</literal> load balancing method.
 </note>
 </para>
@@ -303,22 +302,21 @@
 <appeared-in>1.1.4</appeared-in>
 
 <para>
-Activates cache of connections to upstream servers.
+Activates the cache for connections to upstream servers.
 </para>
 
 <para>
 The <value>connections</value> parameter sets the maximum number of
-idle keepalive connections to upstream servers that are retained in
-the cache per one worker process.
+idle keepalive connections to upstream servers that are preserved in
+the cache of each worker process.
 When this number is exceeded, the least recently used connections
 are closed.
 <note>
-It should be particularly noted that <literal>keepalive</literal> directive
-does not limit the total number of connections that nginx worker process
-can open to upstream servers.
-The <value>connections</value> parameter should be set low enough
-to allow upstream servers to process additional new incoming
-connections as well.
+It should be particularly noted that the <literal>keepalive</literal> directive
+does not limit the total number of connections to upstream servers
+that an nginx worker process can open.
+The <value>connections</value> parameter should be set to a number small enough
+to let upstream servers process new incoming connections as well.
 </note>
 </para>
 
@@ -372,7 +370,7 @@
 <note>
 Alternatively, HTTP/1.0 persistent connections can be used by passing the
 <header>Connection: Keep-Alive</header> header field to an upstream server,
-though this is not recommended.
+though this method is not recommended.
 </note>
 </para>
 
@@ -402,7 +400,7 @@
 <para>
 <note>
 When using load balancer methods other than the default
-round-robin, it is necessary to activate them before
+round-robin method, it is necessary to activate them before
 the <literal>keepalive</literal> directive.
 </note>
 
@@ -583,10 +581,10 @@
 <tag-desc>status is neither 301 nor 302</tag-desc>
 
 <tag-name><literal>status 200-399;</literal></tag-name>
-<tag-desc>status is in the 200..399 range</tag-desc>
+<tag-desc>status is in the range from 200 to 399</tag-desc>
 
 <tag-name><literal>status ! 400-599;</literal></tag-name>
-<tag-desc>status is not in the 400..599 range</tag-desc>
+<tag-desc>status is not in the range from 400 to 599</tag-desc>
 
 <tag-name><literal>status 301-303 307;</literal></tag-name>
 <tag-desc>status is either 301, 302, 303, or 307</tag-desc>
@@ -1005,23 +1003,23 @@
 
 <tag-name><var>$upstream_addr</var></tag-name>
 <tag-desc>
-keeps an IP address and port of the server,
-or a path to the UNIX-domain socket.
+keeps the IP address and port of the server,
+or the path to the UNIX-domain socket.
 If several servers were contacted during request processing,
 their addresses are separated by commas, e.g.
 “<literal>192.168.1.1:80, 192.168.1.2:80, unix:/tmp/sock</literal>”.
-If an internal redirect from one server group to another happened
-using
+If an internal redirect from one server group to another happens,
+initiated by
 <header>X-Accel-Redirect</header> or
-<link doc="ngx_http_core_module.xml" id="error_page"/>
-then these server groups are separated by colons, e.g.
+<link doc="ngx_http_core_module.xml" id="error_page"/>,
+then the server addresses from different groups are separated by colons, e.g.
 “<literal>192.168.1.1:80, 192.168.1.2:80, unix:/tmp/sock : 192.168.10.1:80, 192.168.10.2:80</literal>”.
 </tag-desc>
 
 <tag-name><var>$upstream_cache_status</var></tag-name>
 <tag-desc>
-keeps status of accessing a response cache (0.8.3).
-The status can be one of “<literal>MISS</literal>”, 
+keeps the status of accessing a response cache (0.8.3).
+The status can be either “<literal>MISS</literal>”, 
 “<literal>BYPASS</literal>”, “<literal>EXPIRED</literal>”,
 “<literal>STALE</literal>”, “<literal>UPDATING</literal>” or
 “<literal>HIT</literal>”.
@@ -1029,34 +1027,34 @@
 
 <tag-name><var>$upstream_response_length</var></tag-name>
 <tag-desc>
-keeps lengths of responses obtained from upstream servers (0.7.27);
+keeps the lengths of responses obtained from the upstream servers (0.7.27);
 lengths are kept in bytes.
-Several responses are separated by commas and colons
-like in the <var>$upstream_addr</var> variable.
+Several response lengths are separated by commas and colons
+like addresses in the <var>$upstream_addr</var> variable.
 </tag-desc>
 
 <tag-name><var>$upstream_response_time</var></tag-name>
 <tag-desc>
 keeps times of responses obtained from upstream servers;
 times are kept in seconds with a milliseconds resolution.
-Several responses are separated by commas and colons
-like in the <var>$upstream_addr</var> variable.
+Several response times are separated by commas and colons
+like addresses in the <var>$upstream_addr</var> variable.
 </tag-desc>
 
 <tag-name><var>$upstream_status</var></tag-name>
 <tag-desc>
 keeps codes of responses obtained from upstream servers.
-Several responses are separated by commas and colons
-like in the <var>$upstream_addr</var> variable.
+Several response codes are separated by commas and colons
+like addresses in the <var>$upstream_addr</var> variable.
 </tag-desc>
 
 <tag-name><var>$upstream_http_...</var></tag-name>
 <tag-desc>
 keep server response header fields.
 For example, the <header>Server</header> response header field
-is made available through the <var>$upstream_http_server</var> variable.
+is available through the <var>$upstream_http_server</var> variable.
 The rules of converting header field names to variable names are the same
-as for variables starting with the
+as for the variables that start with the
 “<link doc="ngx_http_core_module.xml" id="variables">$http_</link>” prefix.
 Only the last server’s response header fields are saved.
 </tag-desc>

--- a/xml/en/docs/http/ngx_http_userid_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_userid_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -58,30 +58,30 @@
 <context>location</context>
 
 <para>
-Allows or prohibits to set cookies and log the received cookies:
+Enables or disables setting cookies and logging the received cookies:
 <list type="tag">
 
 <tag-name><literal>on</literal></tag-name>
 <tag-desc>
-allows to set version 2 cookies
-and log the received cookies;
+enables the setting of version 2 cookies
+and logging of the received cookies;
 </tag-desc>
 
 <tag-name><literal>v1</literal></tag-name>
 <tag-desc>
-allows to set version 1 cookies
-and log the received cookies;
+enables the setting of version 1 cookies
+and logging of the received cookies;
 </tag-desc>
 
 <tag-name><literal>log</literal></tag-name>
 <tag-desc>
-prohibits to set cookies
-but allows to log the received cookies;
+disables the setting of cookies,
+but enables logging of the received cookies;
 </tag-desc>
 
 <tag-name><literal>off</literal></tag-name>
 <tag-desc>
-prohibits to set cookies and log the received cookies.
+disables the setting of cookies and logging of the received cookies.
 </tag-desc>
 
 </list>
@@ -99,7 +99,8 @@
 
 <para>
 Defines a domain for which the cookie is set.
-The parameter <literal>none</literal> disables setting a domain for a cookie.
+The <literal>none</literal> parameter disables setting of a domain for the
+cookie.
 </para>
 
 </directive>
@@ -136,20 +137,20 @@
 <context>location</context>
 
 <para>
-If parameter is not <literal>off</literal>, enables the cookie marking
-mechanism and sets a character used as a mark.
-This mechanism allows to add or change
-<link id="userid_p3p"/> and/or cookie expiration time while
+If the parameter is not <literal>off</literal>, enables the cookie marking
+mechanism and sets the character used as a mark.
+This mechanism is used to add or change
+<link id="userid_p3p"/> and/or a cookie expiration time while
 preserving the client identifier.
-The mark can be any letter of the English alphabet (case-sensitive),
+A mark can be any letter of the English alphabet (case-sensitive),
 digit, or the “<literal>=</literal>” character.
 </para>
 
 <para>
-If a mark is set, it is compared with the first padding symbol
-in the base64 representation of client identifier passed in a cookie.
-If they do not match, a cookie is resent with the specified mark,
-expiration time and a <header>P3P</header> header.
+If the mark is set, it is compared with the first padding symbol
+in the base64 representation of the client identifier passed in a cookie.
+If they do not match, the cookie is resent with the specified mark,
+expiration time, and <header>P3P</header> header.
 </para>
 
 </directive>
@@ -163,7 +164,7 @@
 <context>location</context>
 
 <para>
-Sets a cookie name.
+Sets the cookie name.
 </para>
 
 </directive>
@@ -178,8 +179,8 @@
 
 <para>
 Sets a value for the <header>P3P</header> header field that will be
-sent along with a cookie.
-If set to the special value <literal>none</literal>,
+sent along with the cookie.
+If the directive is set to the special value <literal>none</literal>,
 the <header>P3P</header> header will not be sent in a response.
 </para>
 
@@ -210,10 +211,10 @@
 <para>
 If identifiers are issued by multiple servers (services),
 each service should be assigned its own <value>number</value>
-in order to ensure that client identifiers are unique.
-For version 1 cookies the default value is zero.
-For version 2 cookies this is the number composed from the last four
-octets of the server’s IP address.
+to ensure that client identifiers are unique.
+For version 1 cookies, the default value is zero.
+For version 2 cookies, the default value is the number composed from the last
+four octets of the server’s IP address.
 </para>
 
 </directive>
@@ -235,10 +236,10 @@
 
 <tag-name id="var_uid_reset"><var>$uid_reset</var></tag-name>
 <tag-desc>
-If set to a non-empty string, and it is not “<literal>0</literal>”,
-client identifiers are reset.
+If the variable is set to a non-empty string that is not “<literal>0</literal>”,
+the client identifiers are reset.
 The special value “<literal>log</literal>” additionally leads to the output of
-messages about reset identifiers to the
+messages about the reset identifiers to the
 <link doc="../ngx_core_module.xml" id="error_log"/>.
 </tag-desc>
 

--- a/xml/en/docs/http/ngx_http_xslt_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/http/ngx_http_xslt_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -59,12 +59,12 @@
 
 <para>
 Specifies the DTD file that declares character entities.
-This file is compiled during the configuration stage.
-For technical reasons the module is unable to use the
+This file is compiled at the configuration stage.
+For technical reasons, the module is unable to use the
 external subset declared in the processed XML, so it is
-ignored and instead a specially defined file is used.
-This file should not describe the XML structure, it is
-enough to only declare the required character entities, for example:
+ignored and a specially defined file is used instead.
+This file should not describe the XML structure.
+It is enough to declare just the required character entities, for example:
 <example>
 &lt;!ENTITY nbsp "&amp;#xa0;"&gt;
 </example>
@@ -82,7 +82,7 @@
 <appeared-in>1.5.1</appeared-in>
 
 <para>
-Allows to preserve the <header>Last-Modified</header> header field
+Allows preserving the <header>Last-Modified</header> header field
 from the original response during XSLT transformations
 to facilitate response caching.
 </para>
@@ -105,7 +105,7 @@
 <appeared-in>1.1.18</appeared-in>
 
 <para>
-Defines parameters for XSLT stylesheets.
+Defines the parameters for XSLT stylesheets.
 The <value>value</value> is treated as an XPath expression.
 The <value>value</value> can contain variables.
 To pass a string value to a stylesheet,
@@ -132,7 +132,7 @@
 <appeared-in>1.1.18</appeared-in>
 
 <para>
-Defines string parameters for XSLT stylesheets.
+Defines the string parameters for XSLT stylesheets.
 XPath expressions in the <value>value</value> are not interpreted.
 The <value>value</value> can contain variables.
 </para>
@@ -157,7 +157,7 @@
 
 <para>
 Defines the XSLT stylesheet and its optional parameters.
-A stylesheet is compiled during the configuration stage.
+A stylesheet is compiled at the configuration stage.
 </para>
 
 <para>
@@ -174,7 +174,7 @@
 </para>
 
 <para>
-The description of parameters can contain variables, for example,
+The parameters description can contain variables, for example,
 the whole line of parameters can be taken from a single variable:
 <example>
 location / {
@@ -187,8 +187,8 @@
 </para>
 
 <para>
-It is possible to specify several stylesheets; in this case they
-will be applied sequentially in the specified order.
+It is possible to specify several stylesheets.
+They will be applied sequentially in the specified order.
 </para>
 
 </directive>
@@ -205,8 +205,8 @@
 Enables transformations in responses with the specified MIME types
 in addition to “<literal>text/xml</literal>”.
 The special value “<literal>*</literal>” matches any MIME type (0.8.29).
-If the result of transformation is an HTML response, its MIME type
-is changes to “<literal>text/html</literal>”.
+If the transformation result is an HTML response, its MIME type
+is changed to “<literal>text/html</literal>”.
 </para>
 
 </directive>