Merge pull request openresty#7 from kaiwangchen/master

various typo fixes.

Author: agentzh

en/01-NginxVariables06.tut

@@ -212,8 +212,8 @@ construct such a horrible example:
 Here we use our old friend, the L<ngx_map/map> directive, to map the value of
 the built-in variable L<ngx_core/$uri> to our user variable C<$tag>. When
 L<ngx_core/$uri> takes the value C</main>, the value C<1> is assigned to
-C<$tags>; when L<ngx_core/$uri> takes the value C</sub>, the value C<2> is
-assigned instead to C<$tags>; under all the other conditions, C<0> is assigned.
+C<$tag>; when L<ngx_core/$uri> takes the value C</sub>, the value C<2> is
+assigned instead to C<$tag>; under all the other conditions, C<0> is assigned.
 Next, in C</main>, we first initiate a subrequest to C</sub> by using the
 L<ngx_auth_request/auth_request> directive, and then output the value of
 C<$tag>. And within C</sub>, we directly output the value of C<$tag>. Guess

en/02-NginxDirectiveExecOrder01.tut

@@ -36,7 +36,7 @@ There ain't any Nginx bug here, or we'd rather rephrase it as a
 feature, and it's a long story. When Nginx handles every request,
 the execution follows a few predefined phases.
 
-There can be altogehter 11 phases when Nginx handles a request, let's
+There can be altogether 11 phases when Nginx handles a request, let's
 start with three most common ones: C<rewrite>, C<access> and C<content>
 (later on the other phases will be addressed)
 

en/02-NginxDirectiveExecOrder07.tut

@@ -120,7 +120,7 @@ is F</home/agentzh/test/html/>.
 Many newbies might take it for granted that error C<404> is caused when
 the needed C<location> does not exist. The former example tells us,
 C<404> error could be returned even if the needed C<location> is configured
-and matched. This is because error C<404> means the non-existence of a
+and matched. This is because error C<404> means the non-existence of an
 abstract "resource", not the specific C<location>.
 
 Another frequent mistake is missing the command for phase C<content>,

en/02-NginxDirectiveExecOrder08.tut

@@ -106,7 +106,7 @@ from its original address and the proxies in between are transparent. For
 this exact purpose, module L<ngx_realip> needs hook handlers in the first
 phase, the C<post-read> phase, so the rewriting occurs as early as possible.
 
-Behind C<post-phase> is the C<server-rewrite> phase. We briefly mentioned
+Behind C<post-read> is the C<server-rewrite> phase. We briefly mentioned
 in L<ordertut/ (02)>, when module L<ngx_rewrite> and its commands are configured
 in C<server> directive, they basically execute in C<server-rewrite> phase.
 We have an example below: