--- a/xml/en/docs/mail/ngx_mail_proxy_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/mail/ngx_mail_proxy_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -36,9 +36,9 @@
 <context>server</context>
 
 <para>
-Sets size of the buffer used for proxying.
-The buffer size is equal to one memory page by default.
-Depending on a platform, this is either 4K or 8K.
+Sets the size of the buffer used for proxying.
+By default, the buffer size is equal to one memory page.
+Depending on a platform, it is either 4K or 8K.
 </para>
 
 </directive>
@@ -51,19 +51,20 @@
 <context>server</context>
 
 <para>
-Defines whether to pass the error message obtained during
-an authentication on the backend to the client.
+Indicates whether to pass the error message obtained during
+the authentication on the backend to the client.
 </para>
 
 <para>
-Usually, if the authentication in nginx was successful,
-backend can’t return an error, but if it nonetheless exists,
-this means there is some problem inside.
-In such cases the backend message can contain the information
+Usually, if the authentication in nginx is a success,
+the backend cannot return an error.
+If it nevertheless returns an error,
+it means some internal error has occurred.
+In such case the backend message can contain information
 that should not be shown to the client.
-However responding with an error for the correct password
-is a normal behavior of some POP3 servers.
-For example, CommuniGatePro informs user about
+However, responding with an error for the correct password
+is a normal behavior for some POP3 servers.
+For example, CommuniGatePro informs a user about
 <link url="http://www.stalker.com/CommuniGatePro/Alerts.html#Quota">mailbox
 overflow</link> or other events by periodically outputting the
 <link url="http://www.stalker.com/CommuniGatePro/POP.html#Alerts">authentication
@@ -95,11 +96,11 @@
 
 <para>
 Enables or disables issuing of the <literal>XCLIENT</literal> command
-upon the connection to the SMTP backend.
-For the <literal>XCLIENT</literal> command to work it is required to have
+on connection to the SMTP backend.
+The <literal>XCLIENT</literal> command requires
 Postfix with the
-<link url="http://citrin.ru/nginx:xclient-login-patch">patch</link>,
-which adds the <literal>LOGIN</literal> parameter.
+<link url="http://citrin.ru/nginx:xclient-login-patch">patch</link>
+that adds the <literal>LOGIN</literal> parameter.
 If the <literal>XCLIENT</literal> command is not used, the MTA will be unable
 to write the client’s
 <literal>IP</literal>/<literal>HELO</literal>/<literal>LOGIN</literal>
@@ -107,8 +108,8 @@
 </para>
 
 <para>
-If the <literal>xclient</literal> is enabled,
-then upon a backend connection nginx first issues
+If <literal>xclient</literal> is enabled,
+then on a connection to the backend nginx first issues
 <example>
 EHLO server_name
 </example>
@@ -116,20 +117,19 @@
 <example>
 XCLIENT PROTO=ESMTP HELO=client_hello ADDR=192.168.1.1 LOGIN=good_user NAME=[UNAVAILABLE]
 </example>
-If the client upon a connection to nginx issued the <literal>EHLO</literal>,
-then the <literal>XCLIENT</literal> command will pass
-the <literal>PROTO=ESMTP</literal>.
-Otherwise, <literal>PROTO=SMTP</literal> will be passed.
+If the client issues <literal>EHLO</literal> on a connection to nginx,
+the <literal>XCLIENT</literal> command will pass
+<literal>PROTO=ESMTP</literal>.
+Otherwise, it will pass <literal>PROTO=SMTP</literal>.
 The IP address of a client is specified in the <literal>ADDR</literal>
 parameter, and since nginx does not use DNS to resolve the hostname,
 the <literal>NAME=[UNAVAILABLE]</literal> is specified.
 </para>
 
 <para>
-If the <literal>xclient</literal> is disabled,
-then the <literal>EHLO</literal> is issued upon the connection to the backend
-if the client had passed it and the <literal>HELO</literal>
-otherwise.
+If <literal>xclient</literal> is disabled,
+nginx will issue <literal>EHLO</literal> on a connection to the
+backend if the client has passed it, or <literal>HELO</literal>, otherwise.
 </para>
 
 </directive>