Update Hugo, docs

1 files changed, 51 insertions, 51 deletions

diff --git a/articles/index.html b/articles/index.html
index dc52f5d1..ebc2bff4 100644
--- a/articles/index.html
+++ b/articles/index.html
@@ -7,7 +7,7 @@
     <meta name="description" content="">
     <meta name="author" content="Loïc Hoguin based on a design from (Soft10) Pol Cámara">
 
-    <meta name="generator" content="Hugo 0.17" />
+    <meta name="generator" content="Hugo 0.26" />
 
     <title>Nine Nines: Articles</title>
 
@@ -80,9 +80,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>
@@ -99,8 +99,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&#8217;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>
@@ -116,8 +116,8 @@
 			</p>
 		</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>
+		<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>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/the-elephant-in-the-room/">Read More</a>
@@ -133,8 +133,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&#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 style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/dont-let-it-crash/">Read More</a>
@@ -151,9 +151,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.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Read More</a>
@@ -170,8 +170,8 @@
 		</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&#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>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/ranch-1.3/">Read More</a>
@@ -187,10 +187,10 @@
 			</p>
 		</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>
+		<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>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/ml-archives/">Read More</a>
@@ -207,8 +207,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>
@@ -225,9 +225,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>
@@ -244,9 +244,9 @@
 		</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:</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/erlanger-playbook/">Read More</a>
@@ -262,9 +262,9 @@
 			</p>
 		</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>
+		<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>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/erlang-validate-utf8/">Read More</a>
@@ -280,7 +280,7 @@
 			</p>
 		</header>
 
-		<p>Last week I read a great article
on
contributing to open source by Alvaro Videla. He makes
many great points and I am in agreement with most of it.
This made me want to properly explain my point of view with
regard to open source and contributions. Unlike most open
source evangelism articles I will not talk about ideals or
any of that crap, but rather my personal feelings and
experience.</p>
+		<p>Last week I read a great article on contributing to open source by Alvaro Videla. He makes many great points and I am in agreement with most of it. This made me want to properly explain my point of view with regard to open source and contributions. Unlike most open source evangelism articles I will not talk about ideals or any of that crap, but rather my personal feelings and experience.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/on-open-source/">Read More</a>
@@ -296,7 +296,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&#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 style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/the-story-so-far/">Read More</a>
@@ -312,8 +312,8 @@
 			</p>
 		</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>
+		<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>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/cowboy2-qs/">Read More</a>
@@ -329,9 +329,9 @@
 			</p>
 		</header>
 
-		<p>I will now be regularly writing posts about project status, plans
and hopes for the future.
-
Before that though, there&#8217;s one important news to share.
-
Until a year ago all development was financed through consulting
and development services. This worked alright but too much time was
spent doing things that didn&#8217;t benefit the open source projects.
And that didn&#8217;t make me happy at all. Because I like being happy
I stopped that for the most part and spent the year figuring things
out, experimenting and discussing with people about it.</p>
+		<p>I will now be regularly writing posts about project status, plans and hopes for the future.
+ Before that though, there&#8217;s one important news to share.
+ Until a year ago all development was financed through consulting and development services. This worked alright but too much time was spent doing things that didn&#8217;t benefit the open source projects. And that didn&#8217;t make me happy at all. Because I like being happy I stopped that for the most part and spent the year figuring things out, experimenting and discussing with people about it.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/january-2014-status/">Read More</a>
@@ -348,9 +348,9 @@
 		</header>
 
 		<p>This was a triumph! I&#8217;m making a note here: HUGE SUCCESS!!
-

It&#8217;s hard to overstate my satisfaction. Thanks to everyone who
made this possible.
-
If you have backed this fundraiser, and haven&#8217;t provided your
personal details yet, please do so quickly so that your rewards
can be sent!
-
I am hoping that we will be able to make good use of all that
money. The details of the expenses will be published regularly
on the 2013 Fundraiser wiki page,
giving you full disclosure as to how your money is used.</p>
+  It&#8217;s hard to overstate my satisfaction. Thanks to everyone who made this possible.
+ If you have backed this fundraiser, and haven&#8217;t provided your personal details yet, please do so quickly so that your rewards can be sent!
+ I am hoping that we will be able to make good use of all that money. The details of the expenses will be published regularly on the 2013 Fundraiser wiki page, giving you full disclosure as to how your money is used.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/farwest-funded/">Read More</a>
@@ -366,8 +366,8 @@
 			</p>
 		</header>
 
-		<p>Building OTP releases has always been a difficult task. Tools like
Reltool or Rebar have made this simpler, but
it&#8217;s no panacea. This article will show you an alternative and
hopefully much simpler solution.
-
There is two steps to building a release. First you need to build
the various OTP applications you want to include in the release. Once
done, you need to create the release itself, by including the Erlang
runtime system alongside the applications, a boot script to start the
node and all its applications, and some configuration files.</p>
+		<p>Building OTP releases has always been a difficult task. Tools like Reltool or Rebar have made this simpler, but it&#8217;s no panacea. This article will show you an alternative and hopefully much simpler solution.
+ There is two steps to building a release. First you need to build the various OTP applications you want to include in the release. Once done, you need to create the release itself, by including the Erlang runtime system alongside the applications, a boot script to start the node and all its applications, and some configuration files.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/erlang.mk-and-relx/">Read More</a>
@@ -383,9 +383,9 @@
 			</p>
 		</header>
 
-		<p>Today we will start the work on the intermediate module
that will be used to run the code for the expressions found
in our file&#8217;s body, replacing our interpreter.
-
This is what we want to have when all the work is done:
-
xerl -&gt; tokens -&gt; AST -&gt; intermediate -&gt; cerl

Today we will perform this work only on the atomic integer
expression however, so we will not build any module at the end.</p>
+		<p>Today we will start the work on the intermediate module that will be used to run the code for the expressions found in our file&#8217;s body, replacing our interpreter.
+ This is what we want to have when all the work is done:
+ xerl -&gt; tokens -&gt; AST -&gt; intermediate -&gt; cerl  Today we will perform this work only on the atomic integer expression however, so we will not build any module at the end.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/xerl-0.5-intermediate-module/">Read More</a>
@@ -401,10 +401,10 @@
 			</p>
 		</header>
 
-		<p>As promised we are adding an expression separator this time.
This will be short and easy.
-
In the tokenizer we only need to add a line recognizing the
comma as a valid token.
-
, : {token, {',', TokenLine}}.
Then we need to change the following lines in the parser:
-
exprs -&gt; expr : ['$1'].
exprs -&gt; expr exprs : ['$1' | '$2'].
And add a comma between the expressions on the second line:</p>
+		<p>As promised we are adding an expression separator this time. This will be short and easy.
+ In the tokenizer we only need to add a line recognizing the comma as a valid token.
+ , : {token, {',', TokenLine}}. Then we need to change the following lines in the parser:
+ exprs -&gt; expr : ['$1']. exprs -&gt; expr exprs : ['$1' | '$2']. And add a comma between the expressions on the second line:</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/xerl-0.4-expression-separator/">Read More</a>
@@ -420,8 +420,8 @@
 			</p>
 		</header>
 
-		<p>I would like to share some experience and theories on
Erlang scalability.
-
This will be in the form of a series of hints, which
may or may not be accompanied with explanations as to why
things are this way, or how they improve or reduce the scalability
of a system. I will try to do my best to avoid giving falsehoods,
even if that means a few things won&#8217;t be explained.</p>
+		<p>I would like to share some experience and theories on Erlang scalability.
+ This will be in the form of a series of hints, which may or may not be accompanied with explanations as to why things are this way, or how they improve or reduce the scalability of a system. I will try to do my best to avoid giving falsehoods, even if that means a few things won&#8217;t be explained.</p>
 
 		<p style="text-align:right">
 			<a class="read_more" href="https://ninenines.eu/articles/erlang-scalability/">Read More</a>