1 files changed, 31 insertions, 168 deletions
diff --git a/docs/en/cowboy/2.4/guide/migrating_from_2.1/index.html b/docs/en/cowboy/2.4/guide/migrating_from_2.1/index.html
index f9afc1c1..5ed0a8f8 100644
--- a/docs/en/cowboy/2.4/guide/migrating_from_2.1/index.html
+++ b/docs/en/cowboy/2.4/guide/migrating_from_2.1/index.html
@@ -62,203 +62,66 @@
 
 <h1 class="lined-header"><span>Migrating from Cowboy 2.1 to 2.2</span></h1>
 
-<div class="paragraph"><p>Cowboy 2.2 focused on adding features required for writing
-gRPC servers and on completing test suites for the core
-HTTP RFCs, fixing many bugs along the way.</p></div>
-<div class="sect1">
+<p>Cowboy 2.2 focused on adding features required for writing gRPC servers and on completing test suites for the core HTTP RFCs, fixing many bugs along the way.</p>
 <h2 id="_features_added">Features added</h2>
-<div class="sectionbody">
-<div class="ulist"><ul>
-<li>
-<p>
-Add support for sending trailers at the end of response bodies.
-  Trailers are additional header fields that may be sent after the
-  body to add more information to the response. Their usage is
-  required in gRPC servers. They are optional and may be discarded
-  in other scenarios (for example if the request goes through an
-  HTTP/1.0 proxy, as HTTP/1.0 does not support trailers).
-</p>
+<ul><li>Add support for sending trailers at the end of response bodies. Trailers are additional header fields that may be sent after the body to add more information to the response. Their usage is required in gRPC servers. They are optional and may be discarded in other scenarios (for example if the request goes through an HTTP/1.0 proxy, as HTTP/1.0 does not support trailers).
 </li>
-<li>
-<p>
-The <code>max_skip_body_length</code> option was added to <code>cowboy_http</code>.
-  It controls how much of a request body Cowboy is willing to skip
-  when the handler did not touch it. If the remaining body size is
-  too large Cowboy instead closes the connection. It defaults to 1MB.
-</p>
+<li>The <code>max_skip_body_length</code> option was added to <code>cowboy_http</code>. It controls how much of a request body Cowboy is willing to skip when the handler did not touch it. If the remaining body size is too large Cowboy instead closes the connection. It defaults to 1MB.
 </li>
-<li>
-<p>
-The CONNECT and TRACE methods are now rejected as they are
-  currently not implemented and must be handled differently than
-  other methods. They will be implemented in a future release.
-</p>
+<li>The CONNECT and TRACE methods are now rejected as they are currently not implemented and must be handled differently than other methods. They will be implemented in a future release.
 </li>
-</ul></div>
-</div>
-</div>
-<div class="sect1">
+</ul>
 <h2 id="_new_functions">New functions</h2>
-<div class="sectionbody">
-<div class="ulist"><ul>
-<li>
-<p>
-The function <code>stream_trailers/2</code> has been added. It terminates
-  a stream and adds trailer fields at the end of the response. A
-  corresponding stream handler command <code>{trailers, Trailers}</code>
-  has also been added.
-</p>
+<ul><li>The function <code>stream_trailers/2</code> has been added. It terminates a stream and adds trailer fields at the end of the response. A corresponding stream handler command <code>{trailers, Trailers}</code> has also been added.
 </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>
-Test suites for the core HTTP RFCs RFC7230, RFC7231 and RFC7540
-  have been completed. Many of the bugs listed here were fixed as
-  a result of this work.
-</p>
+<ul><li>Test suites for the core HTTP RFCs RFC7230, RFC7231 and RFC7540 have been completed. Many of the bugs listed here were fixed as a result of this work.
 </li>
-<li>
-<p>
-Many HTTP/2 edge cases when clients are misbehaving have been
-  corrected. This includes many cases where the request is malformed
-  (for example when a pseudo-header is present twice).
-</p>
+<li>Many HTTP/2 edge cases when clients are misbehaving have been corrected. This includes many cases where the request is malformed (for example when a pseudo-header is present twice).
 </li>
-<li>
-<p>
-When the HTTP/2 SETTINGS_INITIAL_WINDOW_SIZE value changes,
-  Cowboy now properly updates the flow control windows.
-</p>
+<li>When the HTTP/2 SETTINGS_INITIAL_WINDOW_SIZE value changes, Cowboy now properly updates the flow control windows.
 </li>
-<li>
-<p>
-HTTP/2 could mistakenly log stray messages that actually were
-  expected. This is no longer the case.
-</p>
+<li>HTTP/2 could mistakenly log stray messages that actually were expected. This is no longer the case.
 </li>
-<li>
-<p>
-We no longer send a GOAWAY frame when the HTTP/2 preface is invalid.
-</p>
+<li>We no longer send a GOAWAY frame when the HTTP/2 preface is invalid.
 </li>
-<li>
-<p>
-Some values in the Req object of pushed requests were in the
-  wrong type. They are now the expected binary instead of iolist.
-</p>
+<li>Some values in the Req object of pushed requests were in the wrong type. They are now the expected binary instead of iolist.
 </li>
-<li>
-<p>
-A response body was sometimes sent in response to HEAD requests
-  when using HTTP/2. The body is now ignored.
-</p>
+<li>A response body was sometimes sent in response to HEAD requests when using HTTP/2. The body is now ignored.
 </li>
-<li>
-<p>
-The <code>max_headers</code> option for <code>cowboy_http</code> was not always respected
-  depending on the contents of the buffer. The limit is now strict.
-</p>
+<li>The <code>max_headers</code> option for <code>cowboy_http</code> was not always respected depending on the contents of the buffer. The limit is now strict.
 </li>
-<li>
-<p>
-When an early error occurred on the HTTP/1.1 request line, the
-  partial Req given to stream handlers was missing the <code>ref</code> and
-  <code>peer</code> information. This has been corrected.
-</p>
+<li>When an early error occurred on the HTTP/1.1 request line, the partial Req given to stream handlers was missing the <code>ref</code> and <code>peer</code> information. This has been corrected.
 </li>
-<li>
-<p>
-Absolute URIs with a userinfo component, or without an authority
-  component, are now properly rejected for HTTP/1.0 and HTTP/1.1.
-</p>
+<li>Absolute URIs with a userinfo component, or without an authority component, are now properly rejected for HTTP/1.0 and HTTP/1.1.
 </li>
-<li>
-<p>
-Whitespace is no longer allowed in header lines before the colon.
-</p>
+<li>Whitespace is no longer allowed in header lines before the colon.
 </li>
-<li>
-<p>
-408 responses to HTTP/1.1 requests now properly include a
-  connection: close header indicating that we are going to
-  close the connection. This header will also be sent for
-  other early errors resulting in the closing of the connection.
-</p>
+<li>408 responses to HTTP/1.1 requests now properly include a connection: close header indicating that we are going to close the connection. This header will also be sent for other early errors resulting in the closing of the connection.
 </li>
-<li>
-<p>
-When both the transfer-encoding and content-length headers are
-  sent in an HTTP/1.1 request, the transfer-encoding now takes
-  precedence over the content-length header and the latter is
-  removed from the Req object.
-</p>
+<li>When both the transfer-encoding and content-length headers are sent in an HTTP/1.1 request, the transfer-encoding now takes precedence over the content-length header and the latter is removed from the Req object.
 </li>
-<li>
-<p>
-A 400 response is now returned when the transfer-encoding
-  header is invalid or contains any transfer-coding other
-  than chunked.
-</p>
+<li>A 400 response is now returned when the transfer-encoding header is invalid or contains any transfer-coding other than chunked.
 </li>
-<li>
-<p>
-Invalid chunk sizes are now rejected immediately.
-</p>
+<li>Invalid chunk sizes are now rejected immediately.
 </li>
-<li>
-<p>
-Chunk extensions are now limited to 129 characters. They are
-  not used in practice and are still ignored by Cowboy. The limit
-  is not configurable.
-</p>
+<li>Chunk extensions are now limited to 129 characters. They are not used in practice and are still ignored by Cowboy. The limit is not configurable.
 </li>
-<li>
-<p>
-The final chunk was mistakenly sent in responses to HEAD
-  requests. This is now corrected.
-</p>
+<li>The final chunk was mistakenly sent in responses to HEAD requests. This is now corrected.
 </li>
-<li>
-<p>
-<code>OPTIONS *</code> requests were broken in Cowboy 2.0. They are now
-  working again. Both the routing and <code>cowboy_req:uri/1,2</code> have
-  been corrected.
-</p>
+<li><code>OPTIONS *</code> requests were broken in Cowboy 2.0. They are now working again. Both the routing and <code>cowboy_req:uri/1,2</code> have been corrected.
 </li>
-<li>
-<p>
-204 responses no longer include a content-length header.
-</p>
+<li>204 responses no longer include a content-length header.
 </li>
-<li>
-<p>
-A packet could be lost when switching to Websocket or any
-  other protocol via the <code>switch_protocol</code> command. This is
-  now fixed.
-</p>
+<li>A packet could be lost when switching to Websocket or any other protocol via the <code>switch_protocol</code> command. This is now fixed.
 </li>
-<li>
-<p>
-A 426 response will now be sent when a handler requires
-  the client to upgrade to Websocket and the request did not
-  include the required headers.
-</p>
+<li>A 426 response will now be sent when a handler requires the client to upgrade to Websocket and the request did not include the required headers.
 </li>
-<li>
-<p>
-Both experimental stream handlers <code>cowboy_metrics_h</code> and
-  <code>cowboy_tracer_h</code> received a number of fixes and improvements.
-</p>
+<li>Both experimental stream handlers <code>cowboy_metrics_h</code> and <code>cowboy_tracer_h</code> received a number of fixes and improvements.
 </li>
-</ul></div>
-</div>
-</div>
+</ul>
+