docs(calls): Various sweepfixes #2118
2026-08-14
docs(livekit): Link file for nginx conf and do UI codeblock folding
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 8s
Checks / Prek / Check changed files (pull_request) Successful in 6s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m12s
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been skipped
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m21s
docs(livekit): Fix wordings according to PR comments
- Use proper capitalization to match software brandings - websocket -> WebSocket - resolve other wording issues
docs(livekit): Use "official" Docker method of host loopbacking
As lk-jwt-service is hosted in a bridge network, the previous `extra_hosts` using 127.0.0.1 would just loop back to the container itself. Using `network_mode: host` is unnecessary, and the `host-gateway` approach works well for both Podman and Docker Host loopback issues are prevalent in non-Livekit scenarios too: push gateways is another example. Considering moving these to a dedicated Docker section of the troubleshooting page.