Rebuild using Asciideck

1 files changed, 37 insertions, 72 deletions

diff --git a/articles/ranch-1.3/index.html b/articles/ranch-1.3/index.html
index 914259e4..43d90a8c 100644
--- a/articles/ranch-1.3/index.html
+++ b/articles/ranch-1.3/index.html
@@ -69,88 +69,53 @@
 	</p>
 </header>
 
-<div class="paragraph"><p>Ranch <code>1.3.0</code> has been released!</p></div>
-<div class="paragraph"><p>This release fixes a number of long standing issues and adds
-a small number of features:</p></div>
-<div class="paragraph"><p>The <code>ssl</code> application has been added to the list of dependencies.
-If you don&#8217;t need it, you can remove it automatically when fetching
-Ranch or when building the release. If you do need it, you will no
-longer have issues shutting down a node because of Ranch.</p></div>
-<div class="paragraph"><p>The <code>ranch:info/0</code> and <code>ranch:procs/2</code> can be used to retrieve
-information about Ranch&#8217;s state. Use it for diagnostic and
-discovery purposes.</p></div>
-<div class="paragraph"><p>SSL listeners can now be configured without a certificate, for setups
-that make use of the SNI extension.</p></div>
-<div class="paragraph"><p>Transport options are now a blacklist, meaning all unknown options
-will be accepted. However Dialyzer will warn if said option is not
-defined in Ranch&#8217;s type specifications. Please send a patch when that
-happens!</p></div>
-<div class="paragraph"><p>Various bugs have been fixed, including the bug where the
-number of active connections could become negative. Common
-errors at listener startup should be easier to read (for
-example when the port is already in use).</p></div>
-<div class="paragraph"><p>See the <a href="https://git.ninenines.eu/ranch.git/plain/CHANGELOG.asciidoc">CHANGELOG</a>
-for more details.</p></div>
-<div class="paragraph"><p>Ranch is now tested and supported with Erlang/OTP R16B or above
-on Arch Linux, FreeBSD, OSX, Ubuntu and Windows 7. Contact me
-if you can provide permanent access to another platform for the
-purposes of testing.</p></div>
-<div class="paragraph"><p>Ranch is now available from four locations:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<a href="https://git.ninenines.eu/ranch.git">https://git.ninenines.eu/ranch.git</a>
-</p>
+<p>Ranch <code>1.3.0</code> has been released!</p>
+<p>This release fixes a number of long standing issues and adds a small number of features:</p>
+<p>The <code>ssl</code> application has been added to the list of dependencies. If you don&apos;t need it, you can remove it automatically when fetching Ranch or when building the release. If you do need it, you will no longer have issues shutting down a node because of Ranch.</p>
+<p>The <code>ranch:info/0</code> and <code>ranch:procs/2</code> can be used to retrieve information about Ranch&apos;s state. Use it for diagnostic and discovery purposes.</p>
+<p>SSL listeners can now be configured without a certificate, for setups that make use of the SNI extension.</p>
+<p>Transport options are now a blacklist, meaning all unknown options will be accepted. However Dialyzer will warn if said option is not defined in Ranch&apos;s type specifications. Please send a patch when that happens!</p>
+<p>Various bugs have been fixed, including the bug where the number of active connections could become negative. Common errors at listener startup should be easier to read (for example when the port is already in use).</p>
+<p>See the <a href="https://git.ninenines.eu/ranch.git/plain/CHANGELOG.asciidoc">CHANGELOG</a> for more details.</p>
+<p>Ranch is now tested and supported with Erlang/OTP R16B or above on Arch Linux, FreeBSD, OSX, Ubuntu and Windows 7. Contact me if you can provide permanent access to another platform for the purposes of testing.</p>
+<p>Ranch is now available from four locations:</p>
+<ul><li><a href="https://git.ninenines.eu/ranch.git">https://git.ninenines.eu/ranch.git</a>
 </li>
-<li>
-<p>
-<a href="https://github.com/ninenines/ranch.git">https://github.com/ninenines/ranch.git</a>
-</p>
+<li><a href="https://github.com/ninenines/ranch.git">https://github.com/ninenines/ranch.git</a>
 </li>
-<li>
-<p>
-<a href="https://bitbucket.org/ninenines/ranch.git">https://bitbucket.org/ninenines/ranch.git</a>
-</p>
+<li><a href="https://bitbucket.org/ninenines/ranch.git">https://bitbucket.org/ninenines/ranch.git</a>
 </li>
-<li>
-<p>
-<a href="https://gitlab.com/ninenines/ranch.git">https://gitlab.com/ninenines/ranch.git</a>
-</p>
+<li><a href="https://gitlab.com/ninenines/ranch.git">https://gitlab.com/ninenines/ranch.git</a>
 </li>
-</ul></div>
-<div class="paragraph"><p>They are updated at the same time so there is no real difference.</p></div>
-<div class="paragraph"><p>The most recent Ranch commit is now always signed. You can import the
-<a href="https://pgp.mit.edu/pks/lookup?op=vindex&amp;fingerprint=on&amp;exact=on&amp;search=0xF19F189CECC7439699CEDD7A6EF7A77066CCCC8A">signing key for Loïc Hoguin</a> with:</p></div>
-<div class="listingblock">
-<div class="content"><!-- Generator: GNU source-highlight
+</ul>
+<p>They are updated at the same time so there is no real difference.</p>
+<p>The most recent Ranch commit is now always signed. You can import the <a href="https://pgp.mit.edu/pks/lookup?op=vindex&amp;fingerprint=on&amp;exact=on&amp;search=0xF19F189CECC7439699CEDD7A6EF7A77066CCCC8A">signing key for Loïc Hoguin</a> with:</p>
+<div class="listingblock"><div class="content"><!-- Generator: GNU source-highlight 3.1.8
 by Lorenzo Bettini
 http://www.lorenzobettini.it
 http://www.gnu.org/software/src-highlite -->
-<pre><tt>$ gpg --keyserver hkp<span style="color: #990000">:</span>//keys<span style="color: #990000">.</span>gnupg<span style="color: #990000">.</span>net --recv-key 66CCCC8A</tt></pre></div></div>
-<div class="paragraph"><p>The primary key fingerprint is <code>F19F 189C ECC7 4396 99CE  DD7A 6EF7 A770 66CC CC8A</code>.</p></div>
-<div class="paragraph"><p>When verifying signatures in git, the following should appear:</p></div>
-<div class="listingblock">
-<div class="content"><!-- Generator: GNU source-highlight
+<pre><tt>$ gpg --keyserver hkp<font color="#990000">:</font>//keys<font color="#990000">.</font>gnupg<font color="#990000">.</font>net --recv-key 66CCCC8A</tt></pre>
+</div></div>
+<p>The primary key fingerprint is <code>F19F 189C ECC7 4396 99CE  DD7A 6EF7 A770 66CC CC8A</code>.</p>
+<p>When verifying signatures in git, the following should appear:</p>
+<div class="listingblock"><div class="content"><!-- Generator: GNU source-highlight 3.1.8
 by Lorenzo Bettini
 http://www.lorenzobettini.it
 http://www.gnu.org/software/src-highlite -->
-<pre><tt>gpg<span style="color: #990000">:</span> Signature made Sat <span style="color: #993399">26</span> Nov <span style="color: #993399">2016</span> <span style="color: #993399">12</span><span style="color: #990000">:</span><span style="color: #993399">58</span><span style="color: #990000">:</span><span style="color: #993399">35</span> PM CET
-gpg<span style="color: #990000">:</span>                using RSA key 71366FF21851DF03
-gpg<span style="color: #990000">:</span> Good signature from <span style="color: #FF0000">"Loïc Hoguin &lt;[email protected]&gt;"</span> <span style="color: #990000">[</span>unknown<span style="color: #990000">]</span>
-gpg<span style="color: #990000">:</span> WARNING<span style="color: #990000">:</span> This key is not certified with a trusted signature<span style="color: #990000">!</span>
-gpg<span style="color: #990000">:</span>          There is no indication that the signature belongs to the owner<span style="color: #990000">.</span>
-Primary key fingerprint<span style="color: #990000">:</span> F19F 189C ECC7 <span style="color: #993399">4396</span> 99CE  DD7A 6EF7 A770 66CC CC8A
-     Subkey fingerprint<span style="color: #990000">:</span> FEDA <span style="color: #993399">6E41</span> B390 F745 A385  5CDC <span style="color: #993399">7136</span> 6FF2 <span style="color: #993399">1851</span> DF03</tt></pre></div></div>
-<div class="paragraph"><p>You can safely ignore the warning if you don&#8217;t know what it
-means, as long as everything else is correct.</p></div>
-<div class="paragraph"><p>Mirrors and signature verification will soon be implemented
-directly in Erlang.mk. In the meantime, you will need to
-set them up manually.</p></div>
-<div class="paragraph"><p>Most of this work was done to fix issues in RabbitMQ. Paid
-customers get priority; contact me if you have some issues
-that need fixing sooner rather than later.</p></div>
-<div class="paragraph"><p>Expect future releases to be announced in this space.</p></div>
-<div class="paragraph"><p>Thanks for reading!</p></div>
+<pre><tt>gpg<font color="#990000">:</font> Signature made Sat <font color="#993399">26</font> Nov <font color="#993399">2016</font> <font color="#993399">12</font><font color="#990000">:</font><font color="#993399">58</font><font color="#990000">:</font><font color="#993399">35</font> PM CET
+gpg<font color="#990000">:</font>                using RSA key 71366FF21851DF03
+gpg<font color="#990000">:</font> Good signature from <font color="#FF0000">"Loïc Hoguin &lt;[email protected]&gt;"</font> <font color="#990000">[</font>unknown<font color="#990000">]</font>
+gpg<font color="#990000">:</font> WARNING<font color="#990000">:</font> This key is not certified with a trusted signature<font color="#990000">!</font>
+gpg<font color="#990000">:</font>          There is no indication that the signature belongs to the owner<font color="#990000">.</font>
+Primary key fingerprint<font color="#990000">:</font> F19F 189C ECC7 <font color="#993399">4396</font> 99CE  DD7A 6EF7 A770 66CC CC8A
+     Subkey fingerprint<font color="#990000">:</font> FEDA <font color="#993399">6E41</font> B390 F745 A385  5CDC <font color="#993399">7136</font> 6FF2 <font color="#993399">1851</font> DF03</tt></pre>
+</div></div>
+<p>You can safely ignore the warning if you don&apos;t know what it means, as long as everything else is correct.</p>
+<p>Mirrors and signature verification will soon be implemented directly in Erlang.mk. In the meantime, you will need to set them up manually.</p>
+<p>Most of this work was done to fix issues in RabbitMQ. Paid customers get priority; contact me if you have some issues that need fixing sooner rather than later.</p>
+<p>Expect future releases to be announced in this space.</p>
+<p>Thanks for reading!</p>
+
 
 </article>
 </div>