fix title and links about shared map

Author: xfeep

Configuration.md

@@ -91,7 +91,7 @@ Check [this section](configuration.html#24-chose--coroutine-based-socket-or-asyn
 
 These tips are really useful. Most of them are from real users. Thanks [Rickr Nook](https://github.com/rickr-nook) who give us some useful tips.
 
-1. The number of embed JVMs is the same with Nginx `worker_processes`, so if `worker_processes` > 1 we maybe need [nginx-clojure broadcast API][], shared memory (e.g [SharedHashMap/Chronicle-Map][]) or 
+1. The number of embed JVMs is the same with Nginx `worker_processes`, so if `worker_processes` > 1 we maybe need [nginx-clojure broadcast API][], shared memory (e.g nginx-clojure built-in [Shared Map][], OpenHFT [Chronicle Map][]) or 
 even external service(e.g. redis, database) to  coordinate the state or use cookie based session store to manage session information, e.g. [ring.middleware.session.cookie/cookie-store](https://github.com/mmcgrana/ring/wiki/Sessions).
 1. When importing Swing We Must specifiy `jvm_options "-Djava.awt.headless=true"` , otherwise the nginx will hang.
 1. By adding the location of your clojure source files to the classpath,then just issue "nginx -s reload" and changes to the sources get picked up!
@@ -150,7 +150,7 @@ Please Keep these in your mind:
 
 * By default if the initialization failed the nginx won't start successfully and the worker will exit after reporting an error message in error log file but the master keep running and take the port.
 * Because the maybe more than one nginx worker processes, so this code will run everytime per worker starting. 
-* If you use [Shared Map][], [Chronicle-Map][]  to share data 
+* If you use nginx-clojure built-in [Shared Map][] or OpenHFT [Chronicle Map][]  to share data 
 among nginx worker processes, Java file lock can be used to let only one nginx worker process do the initialization.
 * If you [enabled coroutine support][], nginx maybe will start successfully even if your initialization failed after some socket operations. If you case it, you can 
 use `nginx.clojure.core/without-coroutine` to wrap your handler, e.g.
@@ -693,7 +693,8 @@ For Clojure
 ```
 
 [nginx-clojure broadcast API]: https://github.com/nginx-clojure/nginx-clojure/issues/38
-[SharedHashMap/Chronicle-Map]: https://github.com/OpenHFT/Chronicle-Map
+[Shared Map]: https://nginx-clojure.github.io/sharedmap.html
+[Chronicle Map]: https://github.com/OpenHFT/Chronicle-Map
 [Asynchronous Socket/Channel]: more.html#36-asynchronous-channel
 [2.1 JVM Path , Class Path & Other JVM Options]: configuration.html#21-jvm-path--class-path--other-jvm-options
 [enabled coroutine support]: configuration.html#24-chose--coroutine-based-socket-or-asynchronous-socketchannel-or-thread-pool-for-slow-io-operations

Configuration.md.html

@@ -70,7 +70,7 @@ Maven
 
 License
 =================
-Copyright © 2013-2015 Zhang, Yuexiang (xfeep) and released under the BSD 3-Clause license.
+Copyright © 2013-2016 Zhang, Yuexiang (xfeep) and released under the BSD 3-Clause license.
 
 This program uses:
 * Re-rooted ASM bytecode engineering library which is distributed under the BSD 3-Clause license

CoreFeatures.md

@@ -1,5 +1,5 @@
 <h1>
-<a id="user-content-core-features" class="anchor" href="#core-features" aria-hidden="true"><span class="octicon octicon-link"></span></a>Core Features</h1>
+<a id="user-content-core-features" class="anchor" href="#core-features" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Core Features</h1>
 
 <p>The latest release is v0.4.3, more detail changes about it can be found from <a href="//nginx-clojure.github.io/downloads.html">Release History</a>.</p>
 
@@ -39,7 +39,7 @@ <h1>
 <p>By the way it is very fast, the benchmarks can be found <a href="https://github.com/ptaoussanis/clojure-web-server-benchmarks/">HERE(with wrk2)</a>.</p>
 
 <h1>
-<a id="user-content-jar-repository" class="anchor" href="#jar-repository" aria-hidden="true"><span class="octicon octicon-link"></span></a>Jar Repository</h1>
+<a id="user-content-jar-repository" class="anchor" href="#jar-repository" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Jar Repository</h1>
 
 <p>Nginx-Clojure has already been published to <a href="https://clojars.org/">https://clojars.org/</a> whose maven repository is </p>
 
@@ -51,18 +51,18 @@ <h1>
 <p>After adding clojars repository, you can reference nginx-clojure 0.4.3 , e.g.</p>
 
 <h2>
-<a id="user-content--leiningen-clojure-no-need-to-add-clojars-repository-which-is-a-default-repository-for-leiningen-" class="anchor" href="#-leiningen-clojure-no-need-to-add-clojars-repository-which-is-a-default-repository-for-leiningen-" aria-hidden="true"><span class="octicon octicon-link"></span></a> Leiningen (clojure, no need to add clojars repository which is a default repository for Leiningen) </h2>
+<a id="user-content--leiningen-clojure-no-need-to-add-clojars-repository-which-is-a-default-repository-for-leiningen-" class="anchor" href="#-leiningen-clojure-no-need-to-add-clojars-repository-which-is-a-default-repository-for-leiningen-" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a> Leiningen (clojure, no need to add clojars repository which is a default repository for Leiningen) </h2>
 
 <div class="highlight highlight-source-clojure"><pre>[nginx-clojure <span class="pl-s"><span class="pl-pds">"</span>0.4.3<span class="pl-pds">"</span></span>]</pre></div>
 
 <h2>
-<a id="user-content-gradle-groovyjava" class="anchor" href="#gradle-groovyjava" aria-hidden="true"><span class="octicon octicon-link"></span></a>Gradle (groovy/java)</h2>
+<a id="user-content-gradle-groovyjava" class="anchor" href="#gradle-groovyjava" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Gradle (groovy/java)</h2>
 
 <pre><code>compile "nginx-clojure:nginx-clojure:0.4.3"
 </code></pre>
 
 <h2>
-<a id="user-content-maven" class="anchor" href="#maven" aria-hidden="true"><span class="octicon octicon-link"></span></a>Maven</h2>
+<a id="user-content-maven" class="anchor" href="#maven" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Maven</h2>
 
 <div class="highlight highlight-text-xml"><pre>&lt;<span class="pl-ent">dependency</span>&gt;
   &lt;<span class="pl-ent">groupId</span>&gt;nginx-clojure&lt;/<span class="pl-ent">groupId</span>&gt;
@@ -71,9 +71,9 @@ <h2>
 &lt;/<span class="pl-ent">dependency</span>&gt;</pre></div>
 
 <h1>
-<a id="user-content-license" class="anchor" href="#license" aria-hidden="true"><span class="octicon octicon-link"></span></a>License</h1>
+<a id="user-content-license" class="anchor" href="#license" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>License</h1>
 
-<p>Copyright © 2013-2015 Zhang, Yuexiang (xfeep) and released under the BSD 3-Clause license.</p>
+<p>Copyright © 2013-2016 Zhang, Yuexiang (xfeep) and released under the BSD 3-Clause license.</p>
 
 <p>This program uses:</p>
 

CoreFeatures.md.html

@@ -622,9 +622,9 @@ in nginx.conf
 
 If `worker_processes` > 1 there will be more than one jvm instances viz. more tomcat instances so to get synchronized session information we can not use the default tomcat session manger.
 Instead we may consider to use either of
- 
-1. Cookie based Session Store  viz. storing all session attribute information into cookies.
-1. Shared HashMap among processes in the same machine ,e.g. [Chronicle Map](https://github.com/OpenHFT/Chronicle-Map)
+
+1. Cookied based Session Store  viz. storing all session attribute information into cookies.
+1. Shared HashMap among processes in the same machine ,e.g. nginx-clojure built-in [Shared Map][], OpenHFT [Chronicle Map][]
 1. External Session Store,  e.g.  Redis / MySQL / Memcached Session Store
 
 
@@ -673,12 +673,6 @@ location /examples {
 `gzip` can also appear at http, server blocks. More details can be found [HERE](http://nginx.org/en/docs/http/ngx_http_gzip_module.html)
 
 
-[nginx-clojure broadcast API]: https://github.com/nginx-clojure/nginx-clojure/issues/38
-[SharedHashMap/Chronicle-Map]: https://github.com/OpenHFT/Chronicle-Map
-[hijack API]: https://github.com/nginx-clojure/nginx-clojure/issues/41
-[Asynchronous Channel API]: https://github.com/nginx-clojure/nginx-clojure/issues/37
-[2.2 Initialization Handler for nginx worker]: configuration.html#user-content-22-initialization-handler-for-nginx-worker
-
 3.11 More about Nginx Worker Process
 -----------------
 The number of Nginx worker processes can be configured by nginx directive [worker_processes](http://nginx.org/en/docs/ngx_core_module.html#worker_processes).
@@ -692,10 +686,17 @@ Because a JVM instance will be embeded into per Nginx worker process so if there
 So if we want to get synchronized session information we can not use the default tomcat session manger. Instead we may consider to use either of 
 
 1. Cookie based Session Store  viz. storing all session attribute information into cookies.
-1. Shared HashMap among processes in the same machine ,e.g. [Chronicle Map](https://github.com/OpenHFT/Chronicle-Map)
+1. Shared HashMap among processes in the same machine ,e.g. nginx-clojure built-in [Shared Map][], OpenHFT [Chronicle Map][]
 1. External Session Store,  e.g.  Redis / MySQL / Memcached Session Store
 
 When there are more than one Nginx worker prcocesses sub/pub services also need to be taken care of. Subscribers may connect to JVM instances which maybe are different
 with the JVM instance which the publisher send message to. So we need to use [broadcast API](more.html#35-subpub--broadcast-event) from nginx-clojure
 and broadcast message to all Nginx worker prcocesses.
 
+[nginx-clojure broadcast API]: https://github.com/nginx-clojure/nginx-clojure/issues/38
+[Shared Map]: https://nginx-clojure.github.io/sharedmap.html
+[Chronicle Map]: https://github.com/OpenHFT/Chronicle-Map
+[hijack API]: https://github.com/nginx-clojure/nginx-clojure/issues/41
+[Asynchronous Channel API]: https://github.com/nginx-clojure/nginx-clojure/issues/37
+[2.2 Initialization Handler for nginx worker]: configuration.html#user-content-22-initialization-handler-for-nginx-worker
+