docs(readme): fix wrong titles

Author: soywod

README.md

@@ -6,7 +6,7 @@
     <a href="https://github.com/pimalaya/himalaya/releases/latest"><img alt="Release" src="https://img.shields.io/github/v/release/pimalaya/himalaya?color=success"/></a>
     <a href="https://repology.org/project/himalaya/versions"><img alt="Repology" src="https://img.shields.io/repology/repositories/himalaya?color=success"></a>
     <a href="https://matrix.to/#/#pimalaya:matrix.org"><img alt="Matrix" src="https://img.shields.io/badge/chat-%23pimalaya-blue?style=flat&logo=matrix&logoColor=white"/></a>
-    <a href="https://fosstodon.org/@pimalaya"><img alt="Mastodon" src="https://img.shields.io/badge/social-%40pimalaya-blue?style=flat&logo=mastodon&logoColor=white"/></a>
+    <a href="https://fosstodon.org/@pimalaya"><img alt="Mastodon" src="https://img.shields.io/badge/news-%40pimalaya-blue?style=flat&logo=mastodon&logoColor=white"/></a>
   </p>
 </div>
 
@@ -229,68 +229,64 @@ You can also manually edit your own configuration, from scratch:
 
 ### Proton Mail
 
-<details>
-  <summary>Instructions</summary>
+When using Proton Bridge, emails are synchronized locally and exposed via a local IMAP/SMTP server. This implies 2 things:
 
-  When using Proton Bridge, emails are synchronized locally and exposed via a local IMAP/SMTP server. This implies 2 things:
+- Id order may be reversed or shuffled, but envelopes will still be sorted by date.
+- SSL/TLS needs to be deactivated manually.
+- The password to use is the one generated by Proton Bridge, not the one from your Proton Mail account.
 
-  - Id order may be reversed or shuffled, but envelopes will still be sorted by date.
-  - SSL/TLS needs to be deactivated manually.
-  - The password to use is the one generated by Proton Bridge, not the one from your Proton Mail account.
+```toml
+[accounts.proton]
+email = "example@proton.me"
 
-  ```toml
-  [accounts.proton]
-  email = "example@proton.me"
-
-  backend.type = "imap"
-  backend.host = "127.0.0.1"
-  backend.port = 1143
-  backend.encryption.type = "none"
-  backend.login = "example@proton.me"
-  backend.auth.type = "password"
-  backend.auth.raw = "*****"
-
-  message.send.backend.type = "smtp"
-  message.send.backend.host = "127.0.0.1"
-  message.send.backend.port = 1025
-  message.send.backend.encryption.type = "none"
-  message.send.backend.login = "example@proton.me"
-  message.send.backend.auth.type = "password"
-  message.send.backend.auth.raw = "*****"
-  ```
+backend.type = "imap"
+backend.host = "127.0.0.1"
+backend.port = 1143
+backend.encryption.type = "none"
+backend.login = "example@proton.me"
+backend.auth.type = "password"
+backend.auth.raw = "*****"
 
-  If you still want to use TLS, you need to export the certificate generated by Proton Bridge, then give it to Himalaya:
+message.send.backend.type = "smtp"
+message.send.backend.host = "127.0.0.1"
+message.send.backend.port = 1025
+message.send.backend.encryption.type = "none"
+message.send.backend.login = "example@proton.me"
+message.send.backend.auth.type = "password"
+message.send.backend.auth.raw = "*****"
+```
 
-  ```toml
-  backend.encryption.type = "start-tls"
-  backend.encryption.cert = "/path/to/exported/cert.pem"
-  
-  message.send.backend.encryption.type = "start-tls"
-  message.send.backend.encryption.cert = "/path/to/exported/cert.pem"
-  ```
+If you still want to use TLS, you need to export the certificate generated by Proton Bridge, then give it to Himalaya:
 
-  Keeping your password inside the configuration file is good for testing purpose, but it is not safe. You have 2 better alternatives:
+```toml
+backend.encryption.type = "start-tls"
+backend.encryption.cert = "/path/to/exported/cert.pem"
 
-  - Save your password in any password manager that can be queried via the CLI:
+message.send.backend.encryption.type = "start-tls"
+message.send.backend.encryption.cert = "/path/to/exported/cert.pem"
+```
 
-    ```toml
-    backend.auth.cmd = "pass show proton"
-    ```
+Keeping your password inside the configuration file is good for testing purpose, but it is not safe. You have 2 better alternatives:
 
-  - Use the global keyring of your system (requires the `keyring` cargo feature):
+- Save your password in any password manager that can be queried via the CLI:
 
-    ```toml
-    backend.auth.keyring = "proton-example"
-    ```
+  ```toml
+  backend.auth.cmd = "pass show proton"
+  ```
 
-    Running `himalaya account configure proton` will ask for your IMAP password, just paste the one generated previously.
-</details>
+- Use the global keyring of your system (requires the `keyring` cargo feature):
+
+  ```toml
+  backend.auth.keyring = "proton-example"
+  ```
+
+  Running `himalaya account configure proton` will ask for your IMAP password, just paste the one generated previously.
 
 ### Gmail
 
 Google passwords cannot be used directly. There is two ways to authenticate yourself:
 
-### Using [App Passwords](https://support.google.com/mail/answer/185833)
+#### Using [App Passwords](https://support.google.com/mail/answer/185833)
 
 This option is the simplest and the fastest. First, be sure that:
 
@@ -426,7 +422,7 @@ Keeping your password inside the configuration file is good for testing purpose,
 
   Running `himalaya account configure outlook` will ask for your IMAP password, just paste the one generated previously.
 
-### Using OAuth 2.0
+#### Using OAuth 2.0
 
 This option is the most secure but the hardest to configure. First, you need to get your OAuth 2.0 credentials by following [this guide](https://learn.microsoft.com/en-us/exchange/client-developer/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth). Once you get your client id and your client secret, you can configure your Himalaya account this way: