docs: use mkdocs admonitions

Replaces the github-style admonitions with ones rendering nicely in mkdocs.

Signed-off-by: Moritz Wanzenböck <[email protected]>

Author: WanzenBug

docs/how-to/drbd-tls.md

@@ -134,12 +134,12 @@ Handshake with node3.example.com (10.125.97.42) was successful
 ...
 ```
 
-> [!NOTE]
-> The following messages are expected when running `ktls-utils` in a container and can be safely ignored:
-> ```
-> File /etc/tlshd.d/tls.key: expected mode 600
-> add_key: Bad message
-> ```
+!!! note
+
+    The following messages are expected when running `ktls-utils` in a container and can be safely ignored:
+
+        File /etc/tlshd.d/tls.key: expected mode 600
+        add_key: Bad message
 
 Next, check the statistics on TLS sessions controlled by the kernel on each node. You should see an equal, nonzero
 number of `TlsRxSw` and `TlsRxSw`.
@@ -160,5 +160,6 @@ TlsDecryptRetry                 	0
 TlsRxNoPadViolation             	0
 ```
 
-> [!NOTE]
-> If your network card supports TLS offloading, you might see `TlsTxDevice` and `TlsRxDevice` being nonzero instead.
+!!! note
+
+    If your network card supports TLS offloading, you might see `TlsTxDevice` and `TlsRxDevice` being nonzero instead.

docs/how-to/restore-linstor-db.md

@@ -3,9 +3,10 @@
 This guide shows you how to restore a LINSTOR® Controller from a database backup. A backup is created automatically
 on every database migration of the default `k8s` database.
 
-> [!CAUTION]
-> Restoring from a backup means all changes made to the Cluster state after the backup was taken are lost.
-> This includes information about Persistent Volumes and Volume Snapshots that where created after the backup.
+!!! danger
+
+    Restoring from a backup means all changes made to the Cluster state after the backup was taken are lost.
+    Persistent Volumes and Volume Snapshots that were created after the backup are lost.
 
 To complete this guide, you should be familiar with: