Text change

Author: nramin

Directives.md

@@ -559,7 +559,7 @@ Access handler has the same form with rewrite handle. When it returns `phase-don
 , Nginx will continue the next phase otherwise nginx will response directly typically with some error information, 
 such as `401 Unauthorized`, `403 Forbidden`, etc.
 
-Here 's an example to implement a simple HTTP Basic Authentication.
+Here's an example to implement a simple HTTP Basic Authentication.
 
 ```nginx
 

Directives.md.html

@@ -556,7 +556,7 @@ <h2>
 Access handler has the same form with rewrite handle. When it returns <code>phase-done</code> (Clojure) or  <code>PHASE_DONE</code> (Groovy/Java)
 , Nginx will continue the next phase otherwise nginx will response directly typically with some error information,
 such as <code>401 Unauthorized</code>, <code>403 Forbidden</code>, etc.</p>
-<p>Here 's an example to implement a simple HTTP Basic Authentication.</p>
+<p>Here's an example to implement a simple HTTP Basic Authentication.</p>
 <div class="highlight highlight-source-nginx"><pre>
           <span class="pl-k">location</span> <span class="pl-en">/basicAuth </span>{
                <span class="pl-k">access_handler_type</span> <span class="pl-s">'java'</span>;

HISTORY.md

@@ -127,7 +127,7 @@ comments there would not be such example project. (issue #91)
 1. New Directives: rewrite_handler_type, access_handler_type, header_filter_type, body_filter_type
 1. New Feature: Supports nested locations (issue #56)
 1. Bug Fix : uppercase letters in nginx variable name can not work (issue #54)
-1. Bug Fix: The first registered handler will not work if there 's a asynchronous reading of request body (issue #51)
+1. Bug Fix: The first registered handler will not work if there's a asynchronous reading of request body (issue #51)
 1. Enhancement: `handlers_lazy_init` can be used to make handler initialized lazily or eagerly  (issue #52)
 
 

HISTORY.md.html

@@ -135,7 +135,7 @@ <h2>
 <li>New Directives: rewrite_handler_type, access_handler_type, header_filter_type, body_filter_type</li>
 <li>New Feature: Supports nested locations (issue #56)</li>
 <li>Bug Fix : uppercase letters in nginx variable name can not work (issue #54)</li>
-<li>Bug Fix: The first registered handler will not work if there 's a asynchronous reading of request body (issue #51)</li>
+<li>Bug Fix: The first registered handler will not work if there's a asynchronous reading of request body (issue #51)</li>
 <li>Enhancement: <code>handlers_lazy_init</code> can be used to make handler initialized lazily or eagerly  (issue #52)</li>
 </ol>
 <h2>

More.md

@@ -72,7 +72,7 @@
 current thread  and will flush data on the background asynchronously and later close the channel safely</pre></div></div><div class="public anchor" id="var-closed.3F"><h3>closed?</h3><div class="usage"><code>(closed? ch)</code></div><div class="doc"><pre class="plaintext"></pre></div></div><div class="public anchor" id="var-get-context"><h3>get-context</h3><div class="usage"><code>(get-context ch)</code></div><div class="doc"><pre class="plaintext"></pre></div></div><div class="public anchor" id="var-on-close.21"><h3>on-close!</h3><div class="usage"><code>(on-close! ch attachment listener)</code></div><div class="doc"><pre class="plaintext">Add a close event listener.
 `attachement is a  object which will be passed to listener when close event happens
 `listener is a function like (fn[attachement] ... )
-A close event will happen immediately when channel is closed by either of these three cases:
+A close event will happen immediately when a channel is closed by either of these three cases:
 (1) channel close function/method is invoked on this channel, e.g. (close! ch)
 (2) inner unrecoverable error happens with this channel, e.g. not enough memory to read/write
 (3) remote client connection is closed or broken.</pre></div></div><div class="public anchor" id="var-send.21"><h3>send!</h3><div class="usage"><code>(send! ch data flush? last?)</code></div><div class="doc"><pre class="plaintext">Asynchronously send data to channel without blocking current thread. 

More.md.html

@@ -658,7 +658,7 @@ <h2>
 Access handler has the same form with rewrite handle. When it returns <code>phase-done</code> (Clojure) or  <code>PHASE_DONE</code> (Groovy/Java)
 , Nginx will continue the next phase otherwise nginx will response directly typically with some error information,
 such as <code>401 Unauthorized</code>, <code>403 Forbidden</code>, etc.</p>
-<p>Here 's an example to implement a simple HTTP Basic Authentication.</p>
+<p>Here's an example to implement a simple HTTP Basic Authentication.</p>
 <div class="highlight highlight-source-nginx"><pre>
           <span class="pl-k">location</span> <span class="pl-en">/basicAuth </span>{
                <span class="pl-k">access_handler_type</span> <span class="pl-s">'java'</span>;

api/nginx.clojure.core.html

@@ -237,7 +237,7 @@ <h2>
 <li>New Directives: rewrite_handler_type, access_handler_type, header_filter_type, body_filter_type</li>
 <li>New Feature: Supports nested locations (issue #56)</li>
 <li>Bug Fix : uppercase letters in nginx variable name can not work (issue #54)</li>
-<li>Bug Fix: The first registered handler will not work if there 's a asynchronous reading of request body (issue #51)</li>
+<li>Bug Fix: The first registered handler will not work if there's a asynchronous reading of request body (issue #51)</li>
 <li>Enhancement: <code>handlers_lazy_init</code> can be used to make handler initialized lazily or eagerly  (issue #52)</li>
 </ol>
 <h2>