Use direct tags

docs/install.md

@@ -57,26 +57,17 @@ This is the preferred way of testing `mdedup` without polluting your machine. Th
 
 All links above points to the latest released version of `mdedup`.
 
-```{admonition} Older releases
----
-class: seealso
----
+```{seealso} Older releases
 If you need to test previous versions for regression, compatibility or general troubleshooting, you'll find the old binaries attached as assets to [past releases on GitHub](https://github.com/kdeldycke/mail-deduplicate/releases).
 ```
 
-```{admonition} Development builds
----
-class: caution
----
+```{caution} Development builds
 Each commit to the development branch triggers the compilation of binaries. This way you can easily test the bleeding edge version of `mdedup` and report any issue.
 
 Look at the [list of latest binary builds](https://github.com/kdeldycke/mail-deduplicate/actions/workflows/release.yaml?query=branch%3Amain+is%3Asuccess). Then select the latest `Build & release`/`release.yaml` workflow run and download the binary artifact corresponding to your platform and architecture.
 ```
 
-````{admonition} ABI targets
----
-class: note
----
+````{note} ABI targets
 ```{code-block} shell-session
 $ file ./mdedup*
 ./mdedup-linux-x64.bin:   ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=d0a8ae1ffa469465a836c1505504d1b1c75725b0, for GNU/Linux 3.2.0, stripped