fixed typos in docs. thanks 王斌.

Author: agentzh

README

@@ -1524,8 +1524,8 @@ Nginx API for Lua
     ("-") and the header names will be matched case-insensitively. If the
     response header is not present at all, "nil" will be returned.
 
-    This is particularly useful in the context of filter_header_by_lua and
-    filter_header_by_lua_file, for example,
+    This is particularly useful in the context of header_filter_by_lua and
+    header_filter_by_lua_file, for example,
 
         location /test {
             set $footer '';
@@ -3564,7 +3564,7 @@ Nginx API for Lua
     to make room for the current connection.
 
     Note that the cosocket connection pool is per Nginx worker process
-    rather than per Nginx server instance, so so size limit specified here
+    rather than per Nginx server instance, so the size limit specified here
     also applies to every single Nginx worker process.
 
     Idle connections in the pool will be monitored for any exceptional

README.markdown

@@ -1471,7 +1471,7 @@ Reading `ngx.header.HEADER` will return the value of the response header named `
 
 Underscores (`_`) in the header names will also be replaced by dashes (`-`) and the header names will be matched case-insensitively. If the response header is not present at all, `nil` will be returned.
 
-This is particularly useful in the context of [filter_header_by_lua](http://wiki.nginx.org/HttpLuaModule#filter_header_by_lua) and [filter_header_by_lua_file](http://wiki.nginx.org/HttpLuaModule#filter_header_by_lua_file), for example,
+This is particularly useful in the context of [header_filter_by_lua](http://wiki.nginx.org/HttpLuaModule#header_filter_by_lua) and [header_filter_by_lua_file](http://wiki.nginx.org/HttpLuaModule#header_filter_by_lua_file), for example,
 
 
     location /test {
@@ -3315,7 +3315,7 @@ The second optional argument, `size`, can be used to specify the maximal number
 
 When the connection pool is exceeding the size limit, the least recently used (idle) connection already in the pool will be closed automatically to make room for the current connection.
 
-Note that the cosocket connection pool is per Nginx worker process rather than per Nginx server instance, so so size limit specified here also applies to every single Nginx worker process.
+Note that the cosocket connection pool is per Nginx worker process rather than per Nginx server instance, so the size limit specified here also applies to every single Nginx worker process.
 
 Idle connections in the pool will be monitored for any exceptional events like connection abortion or unexpected incoming data on the line, in which cases the connection in question will be closed and removed from the pool.
 

doc/HttpLuaModule.wiki

@@ -1428,7 +1428,7 @@ Reading <code>ngx.header.HEADER</code> will return the value of the response hea
 
 Underscores (<code>_</code>) in the header names will also be replaced by dashes (<code>-</code>) and the header names will be matched case-insensitively. If the response header is not present at all, <code>nil</code> will be returned.
 
-This is particularly useful in the context of [[#filter_header_by_lua|filter_header_by_lua]] and [[#filter_header_by_lua_file|filter_header_by_lua_file]], for example,
+This is particularly useful in the context of [[#header_filter_by_lua|header_filter_by_lua]] and [[#header_filter_by_lua_file|header_filter_by_lua_file]], for example,
 
 <geshi lang="nginx">
     location /test {
@@ -3207,7 +3207,7 @@ The second optional argument, <code>size</code>, can be used to specify the maxi
 
 When the connection pool is exceeding the size limit, the least recently used (idle) connection already in the pool will be closed automatically to make room for the current connection.
 
-Note that the cosocket connection pool is per Nginx worker process rather than per Nginx server instance, so so size limit specified here also applies to every single Nginx worker process.
+Note that the cosocket connection pool is per Nginx worker process rather than per Nginx server instance, so the size limit specified here also applies to every single Nginx worker process.
 
 Idle connections in the pool will be monitored for any exceptional events like connection abortion or unexpected incoming data on the line, in which cases the connection in question will be closed and removed from the pool.