Text change

Author: nramin

More.md

@@ -101,7 +101,7 @@ Since v0.2.5, nginx-clojure provides a union form of [hijack API][] to work with
 
 ### Hijack the Request
 
-We can hijack the request to get a http server channel to send some messages later. After hijacking the return result from ring handler, will be ignored so we can finely control when & what to be sent to the client.
+We can hijack the request to get a http server channel to send some messages later. After hijacking the return result from ring handler, it will be ignored so we can finely control when & what to be sent to the client.
 
 For Clojure
 
@@ -274,7 +274,7 @@ Here's an example which is retrieving content from mirror.bit.edu.cn:8080 and se
 3.7  About Logging
 -----------------
 
-For logging with nginx-clojure there are several ways
+For logging with nginx-clojure there are several ways:
 
 1. Using System.err.print/println will write a log to nginx error.log. This way is simplest but logging information will be mixed if you have more than one nginx worker.
 2. Using clojure tools.logging + logback or slf4j +  logback, we can get one log file per nginx worker.
@@ -308,7 +308,7 @@ in logback.xml
   </appender>
  ```
 
-Then we'll get log files whose name is just like myapp.2014-09-12-1.log, myapp.2014-09-12-2.log and so on.
+Then we'll generate log files named in this convention: myapp.2014-09-12-1.log, myapp.2014-09-12-2.log and so on.
 
 3.8  Sever Side WebSocket
 -----------------

More.md.html

@@ -258,7 +258,7 @@ <h2>
 <h2>
 <a id="user-content-37--about-logging" class="anchor" href="#37--about-logging" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>3.7  About Logging</h2>
 
-<p>For logging with nginx-clojure there are several ways</p>
+<p>For logging with nginx-clojure there are several ways:</p>
 
 <ol>
 <li>Using System.err.print/println will write a log to nginx error.log. This way is simplest but logging information will be mixed if you have more than one nginx worker.</li>
@@ -288,7 +288,7 @@ <h2>
     &lt;/<span class="pl-ent">encoder</span>&gt;
   &lt;/<span class="pl-ent">appender</span>&gt;</pre></div>
 
-<p>Then we'll get log files whose name is just like myapp.2014-09-12-1.log, myapp.2014-09-12-2.log and so on.</p>
+<p>Then we'll generate log files named in this convention: myapp.2014-09-12-1.log, myapp.2014-09-12-2.log and so on.</p>
 
 <h2>
 <a id="user-content-38--sever-side-websocket" class="anchor" href="#38--sever-side-websocket" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>3.8  Sever Side WebSocket</h2>
@@ -665,7 +665,7 @@ <h2>
 <div class="highlight highlight-source-nginx"><pre><span class="pl-k">worker_processes</span> <span class="pl-s">8</span>;</pre></div>
 
 <p>Because a JVM instance will be embeded into every Nginx worker process, if there are more than one Nginx worker prcocesses then there will be more than one JVM instances.
-  So if we want to have synchronized session information we cannot use the default tomcat session manger. Instead we may consider using one of the following: </p>
+So if we want to have synchronized session information we cannot use the default tomcat session manger. Instead we may consider using one of the following: </p>
 
 <ol>
 <li>Cookie based Session Store  viz. storing all session attribute information into cookies.</li>

more.html

@@ -360,7 +360,7 @@ <h2>
 <h2>
 <a id="user-content-37--about-logging" class="anchor" href="#37--about-logging" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>3.7  About Logging</h2>
 
-<p>For logging with nginx-clojure there are several ways</p>
+<p>For logging with nginx-clojure there are several ways:</p>
 
 <ol>
 <li>Using System.err.print/println will write a log to nginx error.log. This way is simplest but logging information will be mixed if you have more than one nginx worker.</li>
@@ -390,7 +390,7 @@ <h2>
     &lt;/<span class="pl-ent">encoder</span>&gt;
   &lt;/<span class="pl-ent">appender</span>&gt;</pre></div>
 
-<p>Then we'll get log files whose name is just like myapp.2014-09-12-1.log, myapp.2014-09-12-2.log and so on.</p>
+<p>Then we'll generate log files named in this convention: myapp.2014-09-12-1.log, myapp.2014-09-12-2.log and so on.</p>
 
 <h2>
 <a id="user-content-38--sever-side-websocket" class="anchor" href="#38--sever-side-websocket" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>3.8  Sever Side WebSocket</h2>