diff --git a/docs/calls/livekit.mdx b/docs/calls/livekit.mdx
index bb45a8a3c..a0525b2a2 100644
--- a/docs/calls/livekit.mdx
+++ b/docs/calls/livekit.mdx
@@ -513,7 +513,7 @@ ports:
 
 Recreate the LiveKit container (with `docker compose up -d livekit`) to apply these changes. Remember to allow the new `50300:50400/udp` ports through your firewall.
 
-Then, configure a route from port 443 on the host back to the `livekit-turn.example.com` service on port 5349. To multiplex the service and LiveKit's websocket on the same port, use a layer 4 reverse proxy with SNI routing capabilities, such as [caddy-l4], on the host system.
+Then, configure a route from port 443 on the host back to the `livekit-turn.example.com` service on port 5349. To multiplex the service and LiveKit's websocket on the same port, use a layer 4 reverse proxy with SNI routing capabilities, such as [Caddy-L4][caddy-l4], on the host system.
 
 ```
 ## in your Caddyfile ##
@@ -577,7 +577,7 @@ rtc:
       secret: "COTURN_SECRET"
 ```
 
-Restart LiveKit, coturn, and Caddy-l4 to apply these changes.
+Restart LiveKit, coturn, and Caddy-L4 to apply these changes.
 
 </details>
 
diff --git a/docs/calls/turn.mdx b/docs/calls/turn.mdx
index 87c6f8957..db7099a8c 100644
--- a/docs/calls/turn.mdx
+++ b/docs/calls/turn.mdx
@@ -229,7 +229,7 @@ TURN servers are generally reachable on their default ports, as configured above
 
 However, port 443 is usually used by other HTTPS services. Therefore, one would need to multiplex both TURNS and HTTPS on these ports, and filter packets to them via SNI routing.
 
-Below are examples to multiplex Coturn and [LiveKit](./livekit.mdx) on port 443, using [caddy-l4][caddy-l4] on the host system.
+Below are examples to multiplex Coturn and [LiveKit](./livekit.mdx) on port 443, using [Caddy-L4][caddy-l4] on the host system.
 
 <details>
 
@@ -240,7 +240,7 @@ This Caddyfile:
 - Route `turn.example.com` to the TURNS port for Coturn without TLS termination, and
 - Route `livekit.example.com` to the [LiveKit services](./livekit.mdx) with TLS termination by Caddy
 
-Please note that all traffic from Coturn's perspective will be coming from caddy-l4's IP now.
+Please note that all traffic from Coturn's perspective will be coming from Caddy-L4's IP now.
 
 ```
 {