From 117b99d967530281b7ed99dfbe5b37f760ddd9b2 Mon Sep 17 00:00:00 2001
From: fkwp <github-fkwp@w4ve.de>
Date: Tue, 25 Mar 2025 17:14:18 +0100
Subject: [PATCH] prettier

---
 docs/self-hosting.md | 11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/docs/self-hosting.md b/docs/self-hosting.md
index 04374935..7aa0dbaa 100644
--- a/docs/self-hosting.md
+++ b/docs/self-hosting.md
@@ -76,13 +76,13 @@ to implement
 In the context of MatrixRTC, we suggest using a single hostname for backend
 communication by implementing endpoint routing within a reverse proxy setup. For
 the example above, this results in:
-| Service    | Endpoint | Example |
+| Service | Endpoint | Example |
 | -------- | ------- | ------- |
-| [Livekit SFU](https://github.com/livekit/livekit) WebSocket signalling connection  |  `/livekit/sfu` | `matrix-rtc.example.com/livekit/sfu` |
+| [Livekit SFU](https://github.com/livekit/livekit) WebSocket signalling connection | `/livekit/sfu` | `matrix-rtc.example.com/livekit/sfu` |
 | [Matrix Livekit JWT auth service](https://github.com/element-hq/lk-jwt-service) | `/livekit/jwt` | `matrix-rtc.example.com/livekit/jwt` |
 
-
 Using Nginx, you can achieve this by:
+
 ```jsonc
 server {
     ...
@@ -114,8 +114,7 @@ server {
       proxy_pass http://localhost:7880/;
     }
 }
-````
-
+```
 
 #### MatrixRTC backend announcement
 
@@ -148,8 +147,6 @@ server {
 > Most `org.matrix.msc4143.rtc_foci` configurations will only have one entry in
 > the array
 
-
-
 ## Building Element Call
 
 > [!NOTE]