Rebuild using Asciideck

1 files changed, 17 insertions, 87 deletions

diff --git a/docs/en/cowboy/2.4/guide/migrating_from_2.2/index.html b/docs/en/cowboy/2.4/guide/migrating_from_2.2/index.html
index 5bc480c7..e21d669b 100644
--- a/docs/en/cowboy/2.4/guide/migrating_from_2.2/index.html
+++ b/docs/en/cowboy/2.4/guide/migrating_from_2.2/index.html
@@ -62,108 +62,38 @@
 
 <h1 class="lined-header"><span>Migrating from Cowboy 2.2 to 2.3</span></h1>
 
-<div class="paragraph"><p>Cowboy 2.3 focused on making the Cowboy processes behave
-properly according to OTP principles. This version is a
-very good milestone toward that goal and most of everything
-should now work. Release upgrades and a few details will
-be improved in future versions.</p></div>
-<div class="sect1">
+<p>Cowboy 2.3 focused on making the Cowboy processes behave properly according to OTP principles. This version is a very good milestone toward that goal and most of everything should now work. Release upgrades and a few details will be improved in future versions.</p>
 <h2 id="_features_added">Features added</h2>
-<div class="sectionbody">
-<div class="ulist"><ul>
-<li>
-<p>
-Add support for all functions from the module <code>sys</code>. Note
-  that Cowboy currently does not implement the <code>sys</code> debugging
-  mechanisms as tracing is recommended instead.
-</p>
+<ul><li>Add support for all functions from the module <code>sys</code>. Note that Cowboy currently does not implement the <code>sys</code> debugging mechanisms as tracing is recommended instead.
 </li>
-<li>
-<p>
-Add a <code>max_frame_size</code> option for Websocket handlers
-  to close the connection when the client attempts to
-  send a frame that&#8217;s too large. It currently defaults
-  to <code>infinity</code> to avoid breaking existing code but will
-  be changed in a future version.
-</p>
+<li>Add a <code>max_frame_size</code> option for Websocket handlers to close the connection when the client attempts to send a frame that&apos;s too large. It currently defaults to <code>infinity</code> to avoid breaking existing code but will be changed in a future version.
 </li>
-<li>
-<p>
-Update Cowlib to 2.2.1.
-</p>
+<li>Update Cowlib to 2.2.1.
 </li>
-<li>
-<p>
-Add support for the 308 status code and a test suite
-  for RFC7538 where it is defined.
-</p>
+<li>Add support for the 308 status code and a test suite for RFC7538 where it is defined.
 </li>
-</ul></div>
-</div>
-</div>
-<div class="sect1">
+</ul>
 <h2 id="_bugs_fixed">Bugs fixed</h2>
-<div class="sectionbody">
-<div class="ulist"><ul>
-<li>
-<p>
-Ensure timeout options accept the value <code>infinity</code> as
-  documented.
-</p>
+<ul><li>Ensure timeout options accept the value <code>infinity</code> as documented.
 </li>
-<li>
-<p>
-Properly reject HTTP/2 requests with an invalid content-length
-  header instead of simply crashing.
-</p>
+<li>Properly reject HTTP/2 requests with an invalid content-length header instead of simply crashing.
 </li>
-<li>
-<p>
-When switching from HTTP/1.1 to Websocket or user protocols
-  all the messages in the mailbox were flushed. Only messages
-  specific to <code>cowboy_http</code> should now be flushed.
-</p>
+<li>When switching from HTTP/1.1 to Websocket or user protocols all the messages in the mailbox were flushed. Only messages specific to <code>cowboy_http</code> should now be flushed.
 </li>
-<li>
-<p>
-Parsing of the x-forwarded-for header has been corrected.
-  It now supports IPv6 addresses both with and without port.
-</p>
+<li>Parsing of the x-forwarded-for header has been corrected. It now supports IPv6 addresses both with and without port.
 </li>
-<li>
-<p>
-Websocket subprotocol tokens are now parsed in a case
-  insensitive manner, according to the spec.
-</p>
+<li>Websocket subprotocol tokens are now parsed in a case insensitive manner, according to the spec.
 </li>
-<li>
-<p>
-Cookies without values are now allowed. For example <code>Cookie: foo</code>.
-</p>
+<li>Cookies without values are now allowed. For example <code>Cookie: foo</code>.
 </li>
-<li>
-<p>
-Colons are now allowed within path segments in routes provided
-  to <code>cowboy_router:compile/1</code> as long as they are not the first
-  character of the path segment.
-</p>
+<li>Colons are now allowed within path segments in routes provided to <code>cowboy_router:compile/1</code> as long as they are not the first character of the path segment.
 </li>
-<li>
-<p>
-The <code>cowboy_req:delete_resp_header/2</code> function will no longer
-  crash when no response header was set before calling it.
-</p>
+<li>The <code>cowboy_req:delete_resp_header/2</code> function will no longer crash when no response header was set before calling it.
 </li>
-<li>
-<p>
-A miscount of the output HTTP/2 flow control window has been
-  fixed. It prevented sending the response body fully to some
-  clients. The issue only affected response bodies sent as iolists.
-</p>
+<li>A miscount of the output HTTP/2 flow control window has been fixed. It prevented sending the response body fully to some clients. The issue only affected response bodies sent as iolists.
 </li>
-</ul></div>
-</div>
-</div>
+</ul>
+