Rebuild using Asciideck

1 files changed, 46 insertions, 43 deletions

diff --git a/articles/index.html b/articles/index.html
index 4df97ede..b3128c02 100644
--- a/articles/index.html
+++ b/articles/index.html
@@ -75,9 +75,9 @@
 		</header>
 
 		<p>Gun 1.0.0-rc.1 has been released!
- Gun is an HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP.
- Gun provides an asynchronous interface and will keep the connection open to the server, reconnecting as necessary.
- Gun has existed for many years as the test client for Cowboy and is now mature enough to receive a proper version. Gun is battle tested by customers and other users but is not the most well tested client there is.</p>
+Gun is an HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP.
+Gun provides an asynchronous interface and will keep the connection open to the server, reconnecting as necessary.
+Gun has existed for many years as the test client for Cowboy and is now mature enough to receive a proper version. Gun is battle tested by customers and other users but is not the most well tested client there is.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/gun-1.0.0-rc.1/">Read More</a>
@@ -94,8 +94,8 @@
 		</header>
 
 		<p>Cowboy 2.4.0 has been released!
- Numerous HTTP/2 options have been added to control the HTTP/2 SETTINGS and general behavior of HTTP/2 connections. The options for initial window sizes, maximum frame sizes or compression table sizes might be of interest for optimizing the performance of HTTP/2 connections.
- Experimental support for Websocket over HTTP/2 was added. Note that browsers do not currently support it. The only browser with partial support is Google Chrome 67 (dev build) started with a specific flag.</p>
+Numerous HTTP/2 options have been added to control the HTTP/2 SETTINGS and general behavior of HTTP/2 connections. The options for initial window sizes, maximum frame sizes or compression table sizes might be of interest for optimizing the performance of HTTP/2 connections.
+Experimental support for Websocket over HTTP/2 was added. Note that browsers do not currently support it. The only browser with partial support is Google Chrome 67 (dev build) started with a specific flag.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/cowboy-2.4.0/">Read More</a>
@@ -112,9 +112,10 @@
 		</header>
 
 		<p>Cowboy 2.3.0 has been released!
- This release focused on adding support for the functions from the sys module for introspecting Cowboy processes.
- Many bugs have also been fixed. A more complete list of changes can be found in the migration guide: Migrating from Cowboy 2.2 to 2.3.
- You can donate to this project via BountySource because I need to eat snacks when I write code. Thanks in advance!</p>
+This release focused on adding support for the functions from the sys module for introspecting Cowboy processes.
+Many bugs have also been fixed. A more complete list of changes can be found in the migration guide: Migrating from Cowboy 2.2 to 2.3.
+You can donate to this project via BountySource because I need to eat snacks when I write code. Thanks in advance!
+As usual, feedback is appreciated, and issues should be reported by opening a ticket.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/cowboy-2.3.0/">Read More</a>
@@ -131,8 +132,8 @@
 		</header>
 
 		<p>Cowboy 2.2.0 has been released!
- This release focused on adding features required for writing gRPC servers and on completing test suites for the core HTTP RFCs.
-    The cowboy_req:stream_trailers/2 function has been added. It terminates the streamed response by adding some trailer field values. This feature is required for gRPC.    The max_skip_body_length option was added. It controls how much of the request body we are willing to skip to get to the next request for HTTP/1.</p>
+This release focused on adding features required for writing gRPC servers and on completing test suites for the core HTTP RFCs.
+The cowboy_req:stream_trailers/2 function has been added. It terminates the streamed response by adding some trailer field values. This feature is required for gRPC.  The max_skip_body_length option was added. It controls how much of the request body we are willing to skip to get to the next request for HTTP/1.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/cowboy-2.2.0/">Read More</a>
@@ -149,8 +150,8 @@
 		</header>
 
 		<p>Cowboy 2.1.0 has been released!
- This release focused on adding features that were temporarily removed during the 2.0 release process:
-    The client TLS certificate can now be obtained.    The 100 Continue response is now sent automatically again when necessary.    NEW: It is now possible to send informational responses (1XX) directly from user code via the cowboy_req:inform/2,3 functions.    NEW: cowboy_rest handlers can now switch to any other type of handler from almost any callback.</p>
+This release focused on adding features that were temporarily removed during the 2.0 release process:
+The client TLS certificate can now be obtained.  The 100 Continue response is now sent automatically again when necessary.  NEW: It is now possible to send informational responses (1XX) directly from user code via the cowboy_req:inform/2,3 functions.  NEW: cowboy_rest handlers can now switch to any other type of handler from almost any callback.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/cowboy-2.1.0/">Read More</a>
@@ -167,9 +168,9 @@
 		</header>
 
 		<p>Cowboy 2.0.0 has been released!
- This is the new stable version of Cowboy. There are no new releases planned for the 1.x version of Cowboy.
- The highlights from the release are:
-    HTTP/2 support!    Websocket compression!    Much simpler, cleaner interface. No more weird errors just because you discard the Req object.    A new low-level interface that receives all events from every set of request and response.</p>
+This is the new stable version of Cowboy. There are no new releases planned for the 1.x version of Cowboy.
+The highlights from the release are:
+HTTP/2 support!  Websocket compression!  Much simpler, cleaner interface. No more weird errors just because you discard the Req object.  A new low-level interface that receives all events from every set of request and response. This replaces the awkward hooks from 1.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/cowboy-2.0.0/">Read More</a>
@@ -186,9 +187,9 @@
 		</header>
 
 		<p>Cowboy 2.0.0-rc.2 has been released!
- This is the new recommended version of Cowboy. Its API should not change before release. While you probably should not use it in production yet, many do successfully. Use at your own risk.
- This new version contains fixes for the following issues:
-    HTTP/2 server push was using the wrong header compression context.    HTTP/2 flow control could end up queueing data in the wrong order when resuming the sending of data.</p>
+This is the new recommended version of Cowboy. Its API should not change before release. While you probably should not use it in production yet, many do successfully. Use at your own risk.
+This new version contains fixes for the following issues:
+HTTP/2 server push was using the wrong header compression context.  HTTP/2 flow control could end up queueing data in the wrong order when resuming the sending of data.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/cowboy-2.0.0-rc.2/">Read More</a>
@@ -205,8 +206,8 @@
 		</header>
 
 		<p>Cowboy 2.0.0-rc.1 has been released!
- This is the new recommended version of Cowboy. Its API should not change before release. While you probably should not use it in production yet, many do successfully. Use at your own risk.
- The plan is to have a new RC version every couple weeks until the summer ends or later if there are still blocking issues open. Only issues that can&#8217;t be fixed without making breaking changes to the interface may block the release.</p>
+This is the new recommended version of Cowboy. Its API should not change before release. While you probably should not use it in production yet, many do successfully. Use at your own risk.
+The plan is to have a new RC version every couple weeks until the summer ends or later if there are still blocking issues open. Only issues that can&apos;t be fixed without making breaking changes to the interface may block the release.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/cowboy-2.0.0-rc.1/">Read More</a>
@@ -223,7 +224,7 @@
 		</header>
 
 		<p>Have you ever tried telling someone why they should use Erlang? You boast the smaller code size, the auto healing mechanisms, the distribution and they seem really excited. They wonder why they never heard about Erlang before. And then you show them what the code looks like. All excitement goes away. The smiles disappear. Their face starts becoming really serious.
- You lost them. You know you lost them. They comment on the syntax, or perhaps you do, already admitting defeat.</p>
+You lost them. You know you lost them. They comment on the syntax, or perhaps you do, already admitting defeat.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/the-elephant-in-the-room/">Read More</a>
@@ -239,8 +240,8 @@
 			</p>
 		</header>
 
-		<p>We have a specific mindset when writing Erlang programs. We focus on the normal execution of the program and don&#8217;t handle most of the errors that may occur. We sometimes call this normal execution the happy path.
- The general pattern behind writing only for the happy path, letting the VM catch errors (writing them to a log for future consumption) and then having a supervisor restart the processes that failed from a clean state, has a name.</p>
+		<p>We have a specific mindset when writing Erlang programs. We focus on the normal execution of the program and don&apos;t handle most of the errors that may occur. We sometimes call this normal execution the happy path.
+The general pattern behind writing only for the happy path, letting the VM catch errors (writing them to a log for future consumption) and then having a supervisor restart the processes that failed from a clean state, has a name.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/dont-let-it-crash/">Read More</a>
@@ -257,9 +258,9 @@
 		</header>
 
 		<p>Cowboy 2.0.0-pre.4 has been released!
- This is the new recommended version of Cowboy. While I would not recommend putting it in production just yet, I do recommend you start writing new applications with this Cowboy version.
- The most significant changes in the pre-release are:
-    A new architecture: there now is one process per connection and one process per request. This was done because HTTP/2 allows running requests concurrently.</p>
+This is the new recommended version of Cowboy. While I would not recommend putting it in production just yet, I do recommend you start writing new applications with this Cowboy version.
+The most significant changes in the pre-release are:
+A new architecture: there now is one process per connection and one process per request. This was done because HTTP/2 allows running requests concurrently.  Stream handlers.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Read More</a>
@@ -276,8 +277,9 @@
 		</header>
 
 		<p>Ranch 1.3.0 has been released!
- This release fixes a number of long standing issues and adds a small number of features:
- The ssl 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>
+This release fixes a number of long standing issues and adds a small number of features:
+The ssl 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.
+The ranch:info/0 and ranch:procs/2 can be used to retrieve information about Ranch&apos;s state.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/ranch-1.3/">Read More</a>
@@ -294,9 +296,9 @@
 		</header>
 
 		<p>The old mailing list archives have been added to the site, mainly for referencing purposes.
- The mailing list has been shut down and all personal information has been deleted.
- If you need help with a project, consider either opening a ticket on that project&#8217;s issues tracker or going through the community channels (erlang-questions, #ninenines or #erlang on Freenode).
- Prefer tickets; often when people have issues it highlights an underlying problem in the project or its documentation.</p>
+The mailing list has been shut down and all personal information has been deleted.
+If you need help with a project, consider either opening a ticket on that project&apos;s issues tracker or going through the community channels (erlang-questions, #ninenines or #erlang on Freenode).
+Prefer tickets; often when people have issues it highlights an underlying problem in the project or its documentation.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/ml-archives/">Read More</a>
@@ -313,8 +315,8 @@
 		</header>
 
 		<p>Last week-end I updated the Nine Nines website.
- I switched to Hugo. The site is now built from Asciidoc documents. You probably saw me switch to Asciidoc for documentation this past year. This is the natural conclusion to that story. The great thing is that with a little bit of Makefile magic I can just copy the documentation files into Hugo and poof, they appear on the website.
- I am very happy with that new setup.</p>
+I switched to Hugo. The site is now built from Asciidoc documents. You probably saw me switch to Asciidoc for documentation this past year. This is the natural conclusion to that story. The great thing is that with a little bit of Makefile magic I can just copy the documentation files into Hugo and poof, they appear on the website.
+I am very happy with that new setup.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/website-update/">Read More</a>
@@ -331,9 +333,9 @@
 		</header>
 
 		<p>An update to The Erlanger Playbook is now available!
- The Erlanger Playbook is a book about software development using Erlang. It currently covers all areas from the conception, design, the writing of code, documentation and tests.
- The book is still a work in progress. Future topics will include refactoring, debugging and tracing, benchmarking, releases, community management (for open source projects).
- This update fixes a number of things and adds two chapters: IOlists and Erlang building blocks.</p>
+The Erlanger Playbook is a book about software development using Erlang. It currently covers all areas from the conception, design, the writing of code, documentation and tests.
+The book is still a work in progress. Future topics will include refactoring, debugging and tracing, benchmarking, releases, community management (for open source projects).
+This update fixes a number of things and adds two chapters: IOlists and Erlang building blocks.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/erlanger-playbook-september-2015-update/">Read More</a>
@@ -350,9 +352,10 @@
 		</header>
 
 		<p>I am proud to announce the pre-release of The Erlanger Playbook.
- The Erlanger Playbook is a book about software development using Erlang. It currently covers all areas from the conception, design, the writing of code, documentation and tests.
- The book is still a work in progress. Future topics will include refactoring, debugging and tracing, benchmarking, releases, community management (for open source projects).
- The following sections are currently available:</p>
+The Erlanger Playbook is a book about software development using Erlang. It currently covers all areas from the conception, design, the writing of code, documentation and tests.
+The book is still a work in progress. Future topics will include refactoring, debugging and tracing, benchmarking, releases, community management (for open source projects).
+The following sections are currently available:
+About this book; Changelog; Future additions  Erlang: Building blocks; Patterns  Workflow: Think; Write; Stay productive  Documentation: On documentation; Tutorials; User guide; Manual; README files  Design: RESTful APIs; Lessons learned  Code: Starting a project; Version control; Project structure; Code style; Best practices; Special processes; IOLists; The process dictionary  Tests: On testing; Success typing analysis; Manual testing; Unit testing; Functional testing  Selling Erlang: On persuasion; Don&apos;t let it crash   Read a preview: Special processes</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/erlanger-playbook/">Read More</a>
@@ -369,8 +372,8 @@
 		</header>
 
 		<p>Yesterday I pushed Websocket permessage-deflate to Cowboy master. I also pushed a change in the way the code validates UTF-8 data (required for text and close frames as per the spec).
- When looking into why the permessage-deflate tests in autobahntestsuite were taking such a long time, I found that autobahn is using an adaptation of the algorithm named Flexible and Economical UTF-8 Decoder. This is the C99 implementation:
- // Copyright (c) 2008-2009 Bjoern Hoehrmann &lt;bjoern@hoehrmann.</p>
+When looking into why the permessage-deflate tests in autobahntestsuite were taking such a long time, I found that autobahn is using an adaptation of the algorithm named Flexible and Economical UTF-8 Decoder. This is the C99 implementation:
+// Copyright (c) 2008-2009 Bjoern Hoehrmann &lt;bjoern@hoehrmann.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/erlang-validate-utf8/">Read More</a>
@@ -402,7 +405,7 @@
 			</p>
 		</header>
 
-		<p>As I am away from home with little to do (some call this a vacation) I wanted to reflect a little on the story so far, or how I arrived to Erlang and got to where I am now. The raw personal experience. It&#8217;ll be an article that&#8217;s more about social aspect, communities and marketing a project than technical considerations. As a period piece, it will also allow me to reflect on the evolution of Erlang in recent years.</p>
+		<p>As I am away from home with little to do (some call this a vacation) I wanted to reflect a little on the story so far, or how I arrived to Erlang and got to where I am now. The raw personal experience. It&apos;ll be an article that&apos;s more about social aspect, communities and marketing a project than technical considerations. As a period piece, it will also allow me to reflect on the evolution of Erlang in recent years.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/the-story-so-far/">Read More</a>
@@ -419,7 +422,7 @@
 		</header>
 
 		<p>Now that Cowboy 1.0 is out, I can spend some of my time thinking about Cowboy 2.0 that will be released soon after Erlang/OTP 18.0. This entry discusses the proposed changes to query string handling in Cowboy.
- Cowboy 2.0 will respond to user wishes by simplifying the interface of the cowboy_req module. Users want two things: less juggling with the Req variable, and more maps. Maps is the only dynamic key/value data structure in Erlang that we can match directly to extract values, allowing users to greatly simplify their code as they don&#8217;t need to call functions to do everything anymore.</p>
+Cowboy 2.0 will respond to user wishes by simplifying the interface of the cowboy_req module. Users want two things: less juggling with the Req variable, and more maps. Maps is the only dynamic key/value data structure in Erlang that we can match directly to extract values, allowing users to greatly simplify their code as they don&apos;t need to call functions to do everything anymore.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/cowboy2-qs/">Read More</a>