Fixed markup

FAQ.md

@@ -1669,7 +1669,7 @@ This might be caused by a not updated Exchange server, see [here](https://blogs.
 The errors *... Read error ...* (sometimes combined with *BAD_DECRYPT* / *DECRYPTION_FAILED_OR_BAD_RECORD_MAC*),
 *... Write error ...*, *... Read timed out ...*, *... Broken pipe ...* mean that the email server is not responding anymore or that the internet connection is bad.
 
-The error *...ENETUNREACH (Network is unreachable)...*" means that no route to the target network exists.
+The error *...ENETUNREACH (Network is unreachable) ...*" means that no route to the target network exists.
 The local network the email server (the target network) is using might be offline, for example, due to a power cut,
 or the local network your device is using (the source network) might have internet connectivity issues.
 
@@ -2323,7 +2323,7 @@ The error '*Handshake failed ... UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VE
 might be caused by enabling **hardening connections** or **Bouncy Castle** in the connection settings tab page,
 or by Android not supporting older protocols anymore, like SSLv3 and TLSv1.
 
-The error '*Handshake failed ... UNSUPPORTED_PROTOCOL' means that the email server and Android do not have a common SSL/TLS protocol or a common cipher.
+The error '*Handshake failed ... UNSUPPORTED_PROTOCOL ...*' means that the email server and Android do not have a common SSL/TLS protocol or a common cipher.
 The cipher set the server offers might be limited or the server might support the old (and insecure) SSL protocols only.
 
 The error '*javax.net.ssl.SSLHandshakeException: Read error: ... CERT_LENGTH_MISMATCH*' means that there is something wrong with the email server setup.

index.html

@@ -1039,7 +1039,7 @@ Visit https://aka.ms/smtp_auth_disabled for more information.</code></pre>
 <p>The errors <em>… BYE Logging out …</em>, <em>… Connection reset …</em> mean that the email server or something between the email server and the app, for example a router or a firewall (app), actively terminated an existing connection.</p>
 <p>The error <em>… Connection closed by peer …</em> means that the email server actively closed the connection. This might be caused by a not updated Exchange server, see <a href="https://blogs.technet.microsoft.com/pki/2010/09/30/sha2-and-windows/">here</a> for more information.</p>
 <p>The errors <em>… Read error …</em> (sometimes combined with <em>BAD_DECRYPT</em> / <em>DECRYPTION_FAILED_OR_BAD_RECORD_MAC</em>), <em>… Write error …</em>, <em>… Read timed out …</em>, <em>… Broken pipe …</em> mean that the email server is not responding anymore or that the internet connection is bad.</p>
-<p>The error <em>…ENETUNREACH (Network is unreachable)…</em>” means that no route to the target network exists. The local network the email server (the target network) is using might be offline, for example, due to a power cut, or the local network your device is using (the source network) might have internet connectivity issues.</p>
+<p>The error <em>…ENETUNREACH (Network is unreachable) …</em>” means that no route to the target network exists. The local network the email server (the target network) is using might be offline, for example, due to a power cut, or the local network your device is using (the source network) might have internet connectivity issues.</p>
 <p><a name="connectiondropped"></a> The error <em>… Connection dropped by server? …</em> means that the email server unexpectedly terminated the connection. This sometimes happen when there were too many (simultaneous) connections in a too short time or when a wrong password was used too often. In this case, please make sure your password is correct and disable receiving in the receive settings for about 30 minutes and try again. If needed, see <a href="#faq23">this FAQ</a> about how you can reduce the number of connections.</p>
 <p>The error <em>… Unexpected end of zlib input stream …</em> means that not all data was received, possibly due to a bad or interrupted connection.</p>
 <p>The error <em>… connection failure …</em> could indicate <a href="#faq23">Too many simultaneous connections</a>.</p>
@@ -1326,7 +1326,7 @@ X-Google-Original-From: Somebody &lt;somebody+extra@example.org&gt;</code></pre>
 <p>The error ‘<em>Handshake failed … HANDSHAKE_FAILURE_ON_CLIENT_HELLO …</em>’ might be caused by the provider still using RC4, which isn’t supported since <a href="https://developer.android.com/about/versions/nougat/android-7.0-changes.html#tls-ssl">Android 7</a> anymore.</p>
 <p>The error ‘<em>Handshake failed SSL handshake terminated … SSLV3_ALERT_HANDSHAKE_FAILURE … HANDSHAKE_FAILURE_ON_CLIENT_HELLO</em>’ can be caused by <a href="https://issuetracker.google.com/issues/37122132">this Android 7.0 bug</a>. This can unfortunately not be fixed by FairEmail.</p>
 <p>The error ‘<em>Handshake failed … UNSUPPORTED_PROTOCOL or TLSV1_ALERT_PROTOCOL_VERSION or SSLV3_ALERT_HANDSHAKE_FAILURE …</em>’ might be caused by enabling <strong>hardening connections</strong> or <strong>Bouncy Castle</strong> in the connection settings tab page, or by Android not supporting older protocols anymore, like SSLv3 and TLSv1.</p>
-<p>The error ’*Handshake failed … UNSUPPORTED_PROTOCOL’ means that the email server and Android do not have a common SSL/TLS protocol or a common cipher. The cipher set the server offers might be limited or the server might support the old (and insecure) SSL protocols only.</p>
+<p>The error ‘<em>Handshake failed … UNSUPPORTED_PROTOCOL …</em>’ means that the email server and Android do not have a common SSL/TLS protocol or a common cipher. The cipher set the server offers might be limited or the server might support the old (and insecure) SSL protocols only.</p>
 <p>The error ‘<em>javax.net.ssl.SSLHandshakeException: Read error: … CERT_LENGTH_MISMATCH</em>’ means that there is something wrong with the email server setup. Try to switch to port 993 (IMAP) or 465 (SMTP) with SSL/TLS.</p>
 <p>Android 8 Oreo and later <a href="https://developer.android.com/about/versions/oreo/android-8.0-changes#security-all">do not support</a> SSLv3 anymore. There is no way to workaround lacking RC4 and SSLv3 support because it has completely been removed from Android (which should say something). Since version 1.2121 the Bouncy Castle secure socket provider (<a href="https://en.wikipedia.org/wiki/Java_Secure_Socket_Extension">JSSE</a>) is bundled. Enabling this socket provider in the connection-settings tab and enabling ‘<em>Allow insecure connections</em>’ in the account/identity settings <em>might</em> solve this problem.</p>
 <p>The error ‘<em>javax.net.ssl.SSLHandshakeException: Read error: … TLSV1_ALERT_INTERNAL_ERROR</em>’ means that Android and the email server share no common protocol versions and/or common ciphers.</p>