--- a/xml/en/docs/mail/ngx_mail_ssl_module.xml	Wed Aug 14 17:21:19 2013 +0400
+++ b/xml/en/docs/mail/ngx_mail_ssl_module.xml	Wed Aug 14 12:03:41 2013 +0400
@@ -15,8 +15,8 @@
 <section id="summary">
 
 <para>
-The <literal>ngx_mail_ssl_module</literal> provides the necessary
-support for mail proxy server for the SSL/TLS protocol.
+The <literal>ngx_mail_ssl_module</literal> module provides the necessary
+support for a mail proxy server to work with the SSL/TLS protocol.
 </para>
 
 <para>
@@ -54,7 +54,7 @@
 <context>server</context>
 
 <para>
-Specifies a file with a certificate in the PEM format for the given
+Specifies a file with the certificate in the PEM format for the given
 server.
 If intermediate certificates should be specified in addition to a primary
 certificate, they should be specified in the same file in the following
@@ -72,7 +72,7 @@
 <context>server</context>
 
 <para>
-Specifies a file with a secret key in the PEM format for the given
+Specifies a file with the secret key in the PEM format for the given
 server.
 </para>
 
@@ -87,7 +87,7 @@
 
 <para>
 Specifies that server ciphers should be preferred over client ciphers
-when using the SSLv3 and TLS protocols.
+when the SSLv3 and TLS protocols are used.
 </para>
 
 </directive>
@@ -106,13 +106,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
+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 using OpenSSL version 1.0.1
-and higher on older nginx versions these protocols will work but could not
+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>
@@ -131,21 +131,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>
@@ -158,7 +158,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.
@@ -209,13 +209,13 @@
 
 <tag-name><literal>on</literal></tag-name>
 <tag-desc>
-Allow usage of <literal>STLS</literal> command for the POP3
-and <literal>STARTTLS</literal> command for the IMAP;
+allow usage of the <literal>STLS</literal> command for the POP3
+and the <literal>STARTTLS</literal> command for the IMAP;
 </tag-desc>
 
 <tag-name><literal>off</literal></tag-name>
 <tag-desc>
-Deny usage of <literal>STLS</literal>
+deny usage of the <literal>STLS</literal>
 and <literal>STARTTLS</literal> commands;
 </tag-desc>