diff --git a/data/core.telegram.org/mtproto/mtproto-transports.html b/data/core.telegram.org/mtproto/mtproto-transports.html
index 3fb835b41e..b5f2ff139e 100644
--- a/data/core.telegram.org/mtproto/mtproto-transports.html
+++ b/data/core.telegram.org/mtproto/mtproto-transports.html
@@ -47,22 +47,21 @@ Padded…">
   
   <div id="dev_page_content"><!-- scroll_nav -->
 
-<p>Here's a list of MTProto transport protocols (<a href="/mtproto#recap">see the ISO/OSI recap for a full explanation</a>):</p>
+<p>Here&#39;s a list of MTProto transport protocols (<a href="/mtproto#recap">see the ISO/OSI recap for a full explanation</a>):</p>
 <ul>
 <li><a href="#abridged">Abridged</a></li>
 <li><a href="#intermediate">Intermediate</a></li>
 <li><a href="#padded-intermediate">Padded intermediate</a></li>
 <li><a href="#full">Full</a></li>
 </ul>
-<p>The server recognizes these different protocols (and distinguishes them from HTTP, too) by the header.
-Additionally, the following transport features can be used: </p>
+<p>The server recognizes these different protocols (and distinguishes them from HTTP, too) by the header.<br>Additionally, the following transport features can be used: </p>
 <ul>
 <li><a href="#quick-ack">Quick ack</a></li>
 <li><a href="#transport-errors">Transport errors</a></li>
 <li><a href="#transport-obfuscation">Transport obfuscation</a></li>
 </ul>
 <p>Example implementations for these protocols can be seen in <a href="https://github.com/tdlib/td/blob/master/td/mtproto/TcpTransport.cpp">tdlib</a> and <a href="https://github.com/danog/MadelineProto/tree/master/src/danog/MadelineProto/Stream/MTProtoTransport">MadelineProto</a>.</p>
-<h3><a class="anchor" href="#abridged" id="abridged" name="abridged"><i class="anchor-icon"></i></a>Abridged</h3>
+<h3><a class="anchor" name="abridged" href="#abridged"><i class="anchor-icon"></i></a>Abridged</h3>
 <p>The lightest protocol available.</p>
 <ul>
 <li>Overhead: Very small </li>
@@ -78,8 +77,7 @@ OR
 +-+---+----...----+
 |h|len|  payload  +
 +-+---+----...----+</code></pre>
-<p>Before sending <em>anything</em> into the underlying socket (see <a href="transports">transports</a>), the client must first send <code>0xef</code> as the first byte (the server <strong>will not</strong> send <code>0xef</code> as the first byte in the first reply).<br>
-Then, payloads are wrapped in the following envelope:</p>
+<p>Before sending <em>anything</em> into the underlying socket (see <a href="transports">transports</a>), the client must first send <code>0xef</code> as the first byte (the server <strong>will not</strong> send <code>0xef</code> as the first byte in the first reply).<br>Then, payloads are wrapped in the following envelope:</p>
 <ul>
 <li>Length: payload length, divided by four, and encoded as a single byte, only if the resulting packet length is a value between <code>0x01..0x7e</code>.</li>
 <li>Payload: the MTProto payload</li>
@@ -90,7 +88,7 @@ Then, payloads are wrapped in the following envelope:</p>
 <li>Length: payload length, divided by four, and encoded as 3 length bytes (little endian)</li>
 <li>Payload: the MTProto payload</li>
 </ul>
-<h3><a class="anchor" href="#intermediate" id="intermediate" name="intermediate"><i class="anchor-icon"></i></a>Intermediate</h3>
+<h3><a class="anchor" name="intermediate" href="#intermediate"><i class="anchor-icon"></i></a>Intermediate</h3>
 <p>In case 4-byte data alignment is needed, an <em>intermediate</em> version of the original protocol may be used.</p>
 <ul>
 <li>Overhead: small</li>
@@ -101,21 +99,19 @@ Then, payloads are wrapped in the following envelope:</p>
 <pre><code>+----+----...----+
 +len.+  payload  +
 +----+----...----+</code></pre>
-<p>Before sending <em>anything</em> into the underlying socket (see <a href="transports">transports</a>), the client must first send <code>0xeeeeeeee</code> as the first int (four bytes, the server <strong>will not</strong> send <code>0xeeeeeeee</code> as the first int in the first reply).<br>
-Then, payloads are wrapped in the following envelope:</p>
+<p>Before sending <em>anything</em> into the underlying socket (see <a href="transports">transports</a>), the client must first send <code>0xeeeeeeee</code> as the first int (four bytes, the server <strong>will not</strong> send <code>0xeeeeeeee</code> as the first int in the first reply).<br>Then, payloads are wrapped in the following envelope:</p>
 <ul>
 <li>Length: payload length encoded as 4 length bytes (little endian)</li>
 <li>Payload: the MTProto payload</li>
 </ul>
-<h3><a class="anchor" href="#padded-intermediate" id="padded-intermediate" name="padded-intermediate"><i class="anchor-icon"></i></a>Padded intermediate</h3>
-<p>Padded version of the <a href="#intermediate">intermediate protocol</a>, to use with <a href="#transport-obfsucation">obfuscation enabled</a> to <strong>bypass ISP blocks</strong>.</p>
+<h3><a class="anchor" name="padded-intermediate" href="#padded-intermediate"><i class="anchor-icon"></i></a>Padded intermediate</h3>
+<p>Padded version of the <a href="#intermediate">intermediate protocol</a>, to use with <a href="#transport-obfuscation">obfuscation enabled</a> to <strong>bypass ISP blocks</strong>.</p>
 <ul>
 <li>Overhead: small-medium</li>
 <li>Minimum envelope length: random</li>
 <li>Maximum envelope length: random</li>
 </ul>
-<p>Before sending <em>anything</em> into the underlying socket (see <a href="transports">transports</a>), the client must first send <code>0xdddddddd</code> as the first int (four bytes, the server <strong>will not</strong> send <code>0xdddddddd</code> as the first int in the first reply).<br>
-Then, payloads are wrapped in the following envelope:</p>
+<p>Before sending <em>anything</em> into the underlying socket (see <a href="transports">transports</a>), the client must first send <code>0xdddddddd</code> as the first int (four bytes, the server <strong>will not</strong> send <code>0xdddddddd</code> as the first int in the first reply).<br>Then, payloads are wrapped in the following envelope:</p>
 <pre><code>+----+----...----+----...----+
 |tlen|  payload  |  padding  |
 +----+----...----+----...----+</code></pre>
@@ -125,7 +121,7 @@ Then, payloads are wrapped in the following envelope:</p>
 <li>Payload: the MTProto payload</li>
 <li>Padding: A random padding string of length <code>0-15</code></li>
 </ul>
-<h3><a class="anchor" href="#full" id="full" name="full"><i class="anchor-icon"></i></a>Full</h3>
+<h3><a class="anchor" name="full" href="#full"><i class="anchor-icon"></i></a>Full</h3>
 <p>The basic MTProto transport protocol</p>
 <ul>
 <li>Overhead: medium</li>
@@ -143,41 +139,31 @@ Then, payloads are wrapped in the following envelope:</p>
 <li>payload: MTProto payload</li>
 <li>crc: 4 CRC32 bytes computed using length, sequence number, and payload together.</li>
 </ul>
-<h3><a class="anchor" href="#transport-features" id="transport-features" name="transport-features"><i class="anchor-icon"></i></a>Transport features</h3>
+<h3><a class="anchor" name="transport-features" href="#transport-features"><i class="anchor-icon"></i></a>Transport features</h3>
 <p>Additionally, the following transport features can be used: </p>
-<h4><a class="anchor" href="#quick-ack" id="quick-ack" name="quick-ack"><i class="anchor-icon"></i></a>Quick ack</h4>
-<p>These MTProto transport protocols have support for quick acknowledgment.
-In this case, the client sets the highest-order length bit in the query packet, and the server responds with a special 4 bytes as a separate packet. 
-They are the 32 higher-order bits of SHA256 of the encrypted portion of the packet prepended by 32 bytes from the authorization key (the same hash as computed for verifying the message key), with the most significant bit set to make clear that this is not the length of a regular server response packet; if the abridged version is used, bswap is applied to these four bytes.</p>
-<h4><a class="anchor" href="#transport-errors" id="transport-errors" name="transport-errors"><i class="anchor-icon"></i></a>Transport errors</h4>
+<h4><a class="anchor" name="quick-ack" href="#quick-ack"><i class="anchor-icon"></i></a>Quick ack</h4>
+<p>These MTProto transport protocols have support for quick acknowledgment.<br>In this case, the client sets the highest-order length bit in the query packet, and the server responds with a special 4 bytes as a separate packet.<br>They are the 32 higher-order bits of SHA256 of the encrypted portion of the packet prepended by 32 bytes from the authorization key (the same hash as computed for verifying the message key), with the most significant bit set to make clear that this is not the length of a regular server response packet; if the abridged version is used, bswap is applied to these four bytes.</p>
+<h4><a class="anchor" name="transport-errors" href="#transport-errors"><i class="anchor-icon"></i></a>Transport errors</h4>
 <p>In the event of a transport error (missing auth key, transport flood, etc.), the server may send a packet with a signed little-endian number of 4 bytes, whose <strong>absolute value</strong> contains the error code (the error itself is actually negative).  </p>
 <p>For example, error Code 403 corresponds to situations where the corresponding HTTP error would have been returned by the HTTP protocol.</p>
 <p>Error 404 (auth key not found) is returned when the specified auth key ID cannot be found by the DC.</p>
 <p>Error 429 (transport flood) is returned when too many transport connections are established to the same IP in a too short lapse of time, or if any of the <a href="/mtproto/service_messages#simple-container">container</a>/<a href="/mtproto/service_messages_about_messages#acknowledgment-of-receipt">service message limits</a> are reached.</p>
-<h4><a class="anchor" href="#transport-obfuscation" id="transport-obfuscation" name="transport-obfuscation"><i class="anchor-icon"></i></a>Transport obfuscation</h4>
+<h4><a class="anchor" name="transport-obfuscation" href="#transport-obfuscation"><i class="anchor-icon"></i></a>Transport obfuscation</h4>
 <p>Transport obfuscation is required to use the <a href="transports#websocket">websocket transports</a>.</p>
 <p>Transport obfuscation to <strong>prevent ISP blocks</strong> is implemented using the following protocol, situated under the MTProto transport in the ISO/OSI stack, see the <a href="/mtproto#recap">recap</a>; this means that the payload is first wrapped in the <a href="/mtproto/mtproto-transports">MTProto transport envelope</a> (all transports are supported), and then obfuscated: </p>
-<p>Prior to establishing the connection (and eventually sending the protocol header of a specific <a href="/mtproto/mtproto-transports">MTProto transport</a>), a 64-byte (512-bit) <strong>random</strong> initialization payload is generated.
-During the generation process, special care must be taken in order to avoid a situation where that the first int (first four bytes) of the random string are equal to one of the known protocol identifiers (see above).<br>
-In particular, the first four bytes must not be equal to <code>0xdddddddd</code> (padded intermediate), <code>0xeeeeeeee</code> (intermediate), <code>POST</code>, <code>GET</code>, <code>HEAD</code>, or any of the HTTP methods that are accepted by the MTProto servers.<br>
-The first byte must also not be equal to <code>0xef</code> (abridged).
-Bytes <code>4-8</code> must also not be equal to <code>0x00000000</code>, since that would indicate use of the full transport with the initial TCP sequence number (0).</p>
+<p>Prior to establishing the connection (and eventually sending the protocol header of a specific <a href="/mtproto/mtproto-transports">MTProto transport</a>), a 64-byte (512-bit) <strong>random</strong> initialization payload is generated.<br>During the generation process, special care must be taken in order to avoid a situation where that the first int (first four bytes) of the random string are equal to one of the known protocol identifiers (see above).<br>In particular, the first four bytes must not be equal to <code>0xdddddddd</code> (padded intermediate), <code>0xeeeeeeee</code> (intermediate), <code>POST</code>, <code>GET</code>, <code>HEAD</code>, or any of the HTTP methods that are accepted by the MTProto servers.<br>The first byte must also not be equal to <code>0xef</code> (abridged).<br>Bytes <code>4-8</code> must also not be equal to <code>0x00000000</code>, since that would indicate use of the full transport with the initial TCP sequence number (0).</p>
 <p>The protocol identifier, if present, must be inserted in the initialization payload at byte offset <code>56</code>: if its length is less than 4, it must be padded using the protocol identifier itself, to make its length 4 (<code>0xef</code> =&gt; <code>0xefefefef</code>): the standalone protocol identifier must be not be sent aftwerwards.</p>
-<p>This protocol is also (but not exclusively) used when connecting to MTProxies: <strong>only in this case</strong>, the DC ID in a specially encoded form must also be inserted in the initialization payload at offset <code>60</code>.
-The encoding simply consist of the DC ID in two-byte signed little-endian form; <code>10000</code> has to be added to the DC ID to connect to the test servers; it has to be made negative if the DC we're connecting to is a media (not CDN) DC.  </p>
+<p>This protocol is also (but not exclusively) used when connecting to MTProxies: <strong>only in this case</strong>, the DC ID in a specially encoded form must also be inserted in the initialization payload at offset <code>60</code>.<br>The encoding simply consist of the DC ID in two-byte signed little-endian form; <code>10000</code> has to be added to the DC ID to connect to the test servers; it has to be made negative if the DC we&#39;re connecting to is a media (not CDN) DC.  </p>
 <p>Next, a secondary initialization payload is generated by reversing the primary initialization payload.  </p>
 <p>Two keys are extracted from both initialization payloads, using bytes at offsets <code>8-40</code>: the key extracted from the primary payload is used as encryption key, the key extracted from the secondary payload is used as decryption key.</p>
 <p>Two IVs are extracted from both initialization payloads, using bytes at offsets <code>40-56</code>: the IV extracted from the primary payload is used as encryption IV, the IV extracted from the secondary payload is used as decryption IV.</p>
-<p><strong>Only if using MTProxy</strong>, the secret is used to provide connection with the MTProxy server.
-The secret is a 16-byte string, usually distributed in its hexadecimal form along with the MTProxy host and port.</p>
-<p>Often, a 17-byte version of the secret can be found: this simply indicates that the client should use a specific MTProto transport (based on the first byte, usually it's <code>0xdd</code>, to indicate that the padded intermediate protocol should be used <code>0xdddddddd</code>; however, clients should default to the padded intermediate transport whenever an additional byte in the secret is encountered).</p>
-<p>The extracted encryption and decryption keys must be concatenated with the secret (the first byte of which should be ignored if it's the 17-byte version), and the SHA256 hash of such string should be used as encryption/decryption key.</p>
+<p><strong>Only if using MTProxy</strong>, the secret is used to provide connection with the MTProxy server.<br>The secret is a 16-byte string, usually distributed in its hexadecimal form along with the MTProxy host and port.</p>
+<p>Often, a 17-byte version of the secret can be found: this simply indicates that the client should use a specific MTProto transport (based on the first byte, usually it&#39;s <code>0xdd</code>, to indicate that the padded intermediate protocol should be used <code>0xdddddddd</code>; however, clients should default to the padded intermediate transport whenever an additional byte in the secret is encountered).</p>
+<p>The extracted encryption and decryption keys must be concatenated with the secret (the first byte of which should be ignored if it&#39;s the 17-byte version), and the SHA256 hash of such string should be used as encryption/decryption key.</p>
 <p>The obtained encryption and decryption key/IV pairs must then be used with <strong>AES-256-CTR</strong> to encrypt and decrypt all outgoing and incoming payloads.</p>
-<p>The first thing that must be encrypted using the encryption key is the initialization payload itself.
-Then bytes <code>56-64</code> of the encrypted initialization payload are substituted in the original initialization payload: this is the part that contains the constant MTProto transport protocol identifier and the DC ID (<strong>only for MTProxies</strong>).</p>
+<p>The first thing that must be encrypted using the encryption key is the initialization payload itself.<br>Then bytes <code>56-64</code> of the encrypted initialization payload are substituted in the original initialization payload: this is the part that contains the constant MTProto transport protocol identifier and the DC ID (<strong>only for MTProxies</strong>).</p>
 <p>The final initialization payload must then be sent in the socket as <strong>first 64 bytes</strong> after the TCP handshake.</p>
-<p>Example pseudocode for the generation of an MTProxy connection payload (media DC 4) using the obfuscated <a href="#padded-intermediate">padded intermediate</a> transport.
-<strong>Warning</strong>: do not use the specified proxy secret in any MTProxy exposed on the internet.</p>
+<p>Example pseudocode for the generation of an MTProxy connection payload (media DC 4) using the obfuscated <a href="#padded-intermediate">padded intermediate</a> transport.<br><strong>Warning</strong>: do not use the specified proxy secret in any MTProxy exposed on the internet.</p>
 <pre><code>protocol := 0xdddddddd
 dc := 0xfcff
 
@@ -214,7 +200,8 @@ encryptedInit := CTR(encryptKey, encryptIV, init)
 
 finalInit := substr(init, 0, 56) + substr(encryptedInit, 56, 8)
 
-write(finalInit)</code></pre></div>
+write(finalInit)</code></pre>
+</div>
   
 </div>