From 7fec48423a313f6405793ab064f56e388ee28868 Mon Sep 17 00:00:00 2001 From: Jade Ellis Date: Wed, 11 Feb 2026 20:49:51 +0000 Subject: [PATCH] chore: Style --- docs/calls.mdx | 2 -- docs/calls/livekit.mdx | 3 +-- 2 files changed, 1 insertion(+), 4 deletions(-) diff --git a/docs/calls.mdx b/docs/calls.mdx index 4631bd00..b005e15d 100644 --- a/docs/calls.mdx +++ b/docs/calls.mdx @@ -13,7 +13,5 @@ For either one to work correctly, you have to do some additional setup. - For MatrixRTC to work, you have to set up the LiveKit backend (foci). LiveKit also uses TURN/STUN to increase reliability, so you might want to configure your TURN server first. [Read the LiveKit guide](./calls/livekit.mdx) :::warning - Element X is known to not be able to do calls on Continwuity. [Track this bug to get updated when the issue is fixed](https://forgejo.ellis.link/continuwuation/continuwuity/issues/1306) - ::: diff --git a/docs/calls/livekit.mdx b/docs/calls/livekit.mdx index 7cd44cb2..7c359b46 100644 --- a/docs/calls/livekit.mdx +++ b/docs/calls/livekit.mdx @@ -10,7 +10,7 @@ This guide assumes that you are using docker compose for deployment. LiveKit onl LiveKit should live on its own domain or subdomain. In this guide we use `livekit.example.com` - this should be replaced with a domain you control. -Make sure the DNS record for the (dub)domain you plan to use is pointed to your server. +Make sure the DNS record for the (sub)domain you plan to use is pointed to your server. ### 2. Services @@ -113,7 +113,6 @@ By default, all routes should be forwarded to Livekit with the exception of the - `/healthz` - `/get_token` - ### 6. Start Everything Start up the services using your usual method - for example `docker compose up -d`.