# HG changeset patch
# User Ruslan Ermilov <ru@nginx.com>
# Date 1318493212 0
# Node ID e8ed74d3fa0ed14cd1c3e9b5df14274b8e0a570c
# Parent  89c31b453d40daf72d6133de93c23bc641f8839c
Sorted variables alphabetically.

diff --git a/xml/en/docs/http/ngx_http_core_module.xml b/xml/en/docs/http/ngx_http_core_module.xml
--- a/xml/en/docs/http/ngx_http_core_module.xml
+++ b/xml/en/docs/http/ngx_http_core_module.xml
@@ -2141,16 +2141,16 @@ and so on.
 It also supports other variables:
 <list type="tag">
 
+<tag-name><var>$arg_</var><argument>name</argument></tag-name>
+<tag-desc>
+argument <argument>name</argument> in the request line
+</tag-desc>
+
 <tag-name><var>$args</var></tag-name>
 <tag-desc>
 arguments in the request line
 </tag-desc>
 
-<tag-name><var>$arg_</var><argument>name</argument></tag-name>
-<tag-desc>
-argument <argument>name</argument> in the request line
-</tag-desc>
-
 <tag-name><var>$binary_remote_addr</var></tag-name>
 <tag-desc>
 client address in a binary form, value's length is always 4 bytes
@@ -2213,10 +2213,15 @@ allows for connection rate limiting
 PID of the worker process
 </tag-desc>
 
-<tag-name><var>$request_method</var></tag-name>
+<tag-name><var>$query_string</var></tag-name>
 <tag-desc>
-request method, usually
-<dq><code>GET</code></dq> or <dq><code>POST</code></dq>
+same as <var>$args</var>
+</tag-desc>
+
+<tag-name><var>$realpath_root</var></tag-name>
+<tag-desc>
+<link id="root">root</link> directive's value
+for the current request, with all symbolic links resolved to real paths
 </tag-desc>
 
 <tag-name><var>$remote_addr</var></tag-name>
@@ -2234,19 +2239,6 @@ client port
 user name supplied with the Basic authentication
 </tag-desc>
 
-<tag-name><var>$realpath_root</var></tag-name>
-<tag-desc>
-<link id="root">root</link> directive's value
-for the current request, with all symbolic links resolved to real paths
-</tag-desc>
-
-<tag-name><var>$request_filename</var></tag-name>
-<tag-desc>
-file path for the current query, based on the
-<link id="root">root</link> and <link id="alias">alias</link>
-directives, and the request URI
-</tag-desc>
-
 <tag-name><var>$request_body</var></tag-name>
 <tag-desc>
 request body
@@ -2280,29 +2272,29 @@ directives, respectively.
 </para>
 </tag-desc>
 
+<tag-name><var>$request_filename</var></tag-name>
+<tag-desc>
+file path for the current query, based on the
+<link id="root">root</link> and <link id="alias">alias</link>
+directives, and the request URI
+</tag-desc>
+
+<tag-name><var>$request_method</var></tag-name>
+<tag-desc>
+request method, usually
+<dq><code>GET</code></dq> or <dq><code>POST</code></dq>
+</tag-desc>
+
 <tag-name><var>$request_uri</var></tag-name>
 <tag-desc>
 full original request URI (with arguments)
 </tag-desc>
 
-<tag-name><var>$query_string</var></tag-name>
-<tag-desc>
-same as <var>$args</var>
-</tag-desc>
-
 <tag-name><var>$scheme</var></tag-name>
 <tag-desc>
 request scheme, <dq><code>http</code></dq> or <dq><code>https</code></dq>
 </tag-desc>
 
-<tag-name><var>$server_protocol</var></tag-name>
-<tag-desc>
-request protocol, usually
-<dq><code>HTTP/1.0</code></dq>
-or
-<dq><code>HTTP/1.1</code></dq>
-</tag-desc>
-
 <tag-name><var>$server_addr</var></tag-name>
 <tag-desc>
 an address of the server which accepted a request
@@ -2323,6 +2315,14 @@ name of the server which accepted a requ
 port of the server which accepted a request
 </tag-desc>
 
+<tag-name><var>$server_protocol</var></tag-name>
+<tag-desc>
+request protocol, usually
+<dq><code>HTTP/1.0</code></dq>
+or
+<dq><code>HTTP/1.1</code></dq>
+</tag-desc>
+
 <tag-name><var>$uri</var></tag-name>
 <tag-desc>
 current URI in request