fix markdown callouts

Author: topi314

CHANGELOG.md

@@ -104,10 +104,11 @@ The most noteworthy of these, as well as any features and breaking changes, are
 * Update to the [Protocol Module](protocol) to support Kotlin/JS
 * Removal of all `/v3` endpoints except `/version`. All other endpoints are now under `/v4`
 
-> **Warning**
-> This is a beta release, and as such, may contain bugs. Please report any bugs you find to the [issue tracker](https://github.com/lavalink-devs/Lavalink/issues/new/choose).
-> For more info on the changes in this release, see [here](https://lavalink.dev/changelog/index.html#significant-changes)
-> If you have any question regarding the changes in this release, please ask in the [support server](https://discord.gg/ZW4s47Ppw4) or [GitHub discussions](https://github.com/lavalink-devs/Lavalink/discussions/categories/q-a)
+!!! warning
+
+    This is a beta release, and as such, may contain bugs. Please report any bugs you find to the [issue tracker](https://github.com/lavalink-devs/Lavalink/issues/new/choose).
+    For more info on the changes in this release, see [here](https://lavalink.dev/changelog/index.html#significant-changes)
+    If you have any question regarding the changes in this release, please ask in the [support server](https://discord.gg/ZW4s47Ppw4) or [GitHub discussions](https://github.com/lavalink-devs/Lavalink/discussions/categories/q-a)
 
 Contributors:
 [@topi314](https://github.com/topi314), [@freyacodes](https://github.com/freyacodes), [@DRSchlaubi](https://github.com/DRSchlaubi) and [@melike2d](https://github.com/melike2d)
@@ -151,8 +152,9 @@ Contributors:
 * Fix errors when doing multiple session resumes
 * Update lavaplayer to `1.4.0` see [here](https://github.com/Walkyst/lavaplayer-fork/releases/tag/1.4.0) for more info
 
-> **Note**
-> Lavalink Docker images are now found in the GitHub Container Registry instead of DockerHub
+!!! note
+
+    Lavalink Docker images are now found in the GitHub Container Registry instead of DockerHub
 
 ## 3.7.4
 * Fix an issue where Lavalink would not destroy a session when a client disconnects

docs/configuration/index.md

@@ -13,7 +13,9 @@ See the [application.yml](config/application-yml.md) documentation for more info
 
 ## Config Server
 
-> **WARNING:** This is an advanced feature geared towards big deployments.
+!!! warning
+
+    This is an advanced feature geared towards big deployments.
 
 You can run the [Lavalink Config Server](https://github.com/lavalink-devs/Lavalink-Config-Server) to manage the configuration of multiple Lavalink servers at one place.
 See the [Config Server](config/config-server.md) documentation for more information.

docs/getting-started/index.md

@@ -16,20 +16,26 @@ Generally there are a few different ways to run Lavalink:
 
 ### Standalone Binary
 
-> **Note:** This is the easiest way to run Lavalink.
+!!! note
+
+    This is the easiest way to run Lavalink.
 
 To run Lavalink as a standalone binary, follow the steps [here](binary.md).
 
 ### Systemd
 
-> **Note:** This is the recommended way to run Lavalink on Linux.
+!!! note
+
+    This is the recommended way to run Lavalink on Linux.
 
 Running Lavalink as a systemd service makes sure that Lavalink is always running and restarts it if it crashes.
 You can find the instructions [here](systemd.md).
 
 ### Docker
 
-> **Note:** This is the recommended way for experienced users to run Lavalink.
+!!! note
+
+    This is the recommended way for experienced users to run Lavalink.
 
 Running applications in Docker containers is a great way to isolate them from the host system and make them portable.
 You can find the instructions [here](docker.md).