From 8339e9e1ca2ba3e35126269e551cc972f6543a4d Mon Sep 17 00:00:00 2001
From: Keerthana <grittypuffy@riseup.net>
Date: Tue, 10 Jun 2025 09:38:16 +0530
Subject: [PATCH] [docs] fix caddy configuration

---
 docs/docs/self-hosting/guides/from-source.md |  3 ++-
 docs/docs/self-hosting/reverse-proxy.md      | 13 ++++++++++---
 2 files changed, 12 insertions(+), 4 deletions(-)

diff --git a/docs/docs/self-hosting/guides/from-source.md b/docs/docs/self-hosting/guides/from-source.md
index 4284124487..557c5b5adc 100644
--- a/docs/docs/self-hosting/guides/from-source.md
+++ b/docs/docs/self-hosting/guides/from-source.md
@@ -197,7 +197,7 @@ ports). The web server of choice in this guide is
 [Caddy](https://caddyserver.com) because with caddy you don't have to manually
 configure/setup SSL ceritifcates as caddy will take care of that.
 
-```sh
+``` groovy
 photos.yourdomain.com {
 	reverse_proxy http://localhost:3001
     # for logging
@@ -219,6 +219,7 @@ Next, start the caddy server :).
 sudo systemctl enable caddy
 
 sudo systemctl daemon-reload
+
 sudo systemctl start caddy
 ```
 
diff --git a/docs/docs/self-hosting/reverse-proxy.md b/docs/docs/self-hosting/reverse-proxy.md
index 5ee0ca97fd..97ef7da570 100644
--- a/docs/docs/self-hosting/reverse-proxy.md
+++ b/docs/docs/self-hosting/reverse-proxy.md
@@ -32,10 +32,17 @@ After the installation is complete, a `Caddyfile` is created on the path
 `/etc/caddy/`. This file is used to configure reverse proxies among other
 things.
 
-```yaml
+```groovy
 # Caddyfile - myente.xyz is just an example.
-api.myente.xyz { reverse_proxy http://localhost:8080 } ente.myente.xyz {
-reverse_proxy http://localhost:3000 }
+
+api.myente.xyz {
+    reverse_proxy http://localhost:8080
+}
+
+ente.myente.xyz {
+    reverse_proxy http://localhost:3000
+}
+
 #...and so on for other endpoints
 ```