Mercurial > hg > nginx-site
changeset 1144:ac131944d349
Changed infinitive to gerund after "allow".
author | Yaroslav Zhuravlev <yar@nginx.com> |
---|---|
date | Mon, 07 Apr 2014 17:14:21 +0400 |
parents | b93422ca9fe7 |
children | e6b28653c406 |
files | xml/en/docs/freebsd_tuning.xml xml/en/docs/hash.xml xml/en/docs/http/configuring_https_servers.xml xml/en/docs/http/ngx_http_limit_req_module.xml xml/en/docs/http/ngx_http_ssl_module.xml xml/en/docs/mail/ngx_mail_ssl_module.xml |
diffstat | 6 files changed, 7 insertions(+), 7 deletions(-) [+] |
line wrap: on
line diff
--- a/xml/en/docs/freebsd_tuning.xml +++ b/xml/en/docs/freebsd_tuning.xml @@ -55,7 +55,7 @@ tcp4 0/0/128 *.22 Here are 192 unaccepted connections and most likely new coming connections are discarding. Although the limit is 128 connections, FreeBSD allows -to receive 1.5 times connections than the limit before it starts to discard +receiving 1.5 times connections than the limit before it starts to discard the new connections. You may increase the limit using <programlisting> @@ -234,7 +234,7 @@ We will discuss the i386 specific tuning <para> There is way not to use the jumbo clusters while serving static files: the <i>sendfile()</i> system call. -The sendfile allows to send a file or its part to a socket directly +The sendfile allows sending a file or its part to a socket directly without reading the parts in an application buffer. It creates the mbufs chain where the mbufs point to the file pages that are already present in FreeBSD cache memory, and passes the chain to
--- a/xml/en/docs/hash.xml +++ b/xml/en/docs/hash.xml @@ -24,7 +24,7 @@ configured parameter (hash bucket size). The size of a table is expressed in buckets. The adjustment is continued until the table size exceeds the hash max size parameter. -Most hashes have the corresponding directives that allow to change +Most hashes have the corresponding directives that allow changing these parameters, for example, for the server names hash they are <link doc="http/ngx_http_core_module.xml" id="server_names_hash_max_size"/> and <link doc="http/ngx_http_core_module.xml" id="server_names_hash_bucket_size"/>.
--- a/xml/en/docs/http/configuring_https_servers.xml +++ b/xml/en/docs/http/configuring_https_servers.xml @@ -311,7 +311,7 @@ server { name="An SSL certificate with several names"> <para> -There are other ways that allow to share a single IP address +There are other ways that allow sharing a single IP address between several HTTPS servers. However, all of them have their drawbacks. One way is to use a certificate with several names in
--- a/xml/en/docs/http/ngx_http_limit_req_module.xml +++ b/xml/en/docs/http/ngx_http_limit_req_module.xml @@ -164,7 +164,7 @@ 1 request per second. 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, -that allows to decrease the state size down to 64 bytes. +that allows decreasing the state size down to 64 bytes. One megabyte zone can keep 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"/>
--- a/xml/en/docs/http/ngx_http_ssl_module.xml +++ b/xml/en/docs/http/ngx_http_ssl_module.xml @@ -402,7 +402,7 @@ By default, a randomly generated key is <para> If several keys are specified, only the first key is used to encrypt TLS session tickets. -This allows to configure key rotation, for example: +This allows configuring key rotation, for example: <example> ssl_session_ticket_key current.key; ssl_session_ticket_key previous.key;
--- a/xml/en/docs/mail/ngx_mail_ssl_module.xml +++ b/xml/en/docs/mail/ngx_mail_ssl_module.xml @@ -199,7 +199,7 @@ By default, a randomly generated key is <para> If several keys are specified, only the first key is used to encrypt TLS session tickets. -This allows to configure key rotation, for example: +This allows configuring key rotation, for example: <example> ssl_session_ticket_key current.key; ssl_session_ticket_key previous.key;