From 4507d5134a7ac1be286d89dbfb5b1d460631775f Mon Sep 17 00:00:00 2001 From: dayton4352 <148722815+dayton4352@users.noreply.github.com> Date: Fri, 27 Feb 2026 20:30:11 -0800 Subject: [PATCH] Fix link to Matrix RTC configuration document --- docs/configuring-playbook-turn.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuring-playbook-turn.md b/docs/configuring-playbook-turn.md index d9d0c3be0..82eb32642 100644 --- a/docs/configuring-playbook-turn.md +++ b/docs/configuring-playbook-turn.md @@ -25,7 +25,7 @@ and configure its IP-related settings in the section below. If you'd like coturn to stay disabled even when Jitsi is enabled, or if you prefer to use an external TURN provider, see [disabling coturn](#disabling-coturn) section below. -When Coturn is not enabled, homeservers (like Synapse) would not point to TURN servers and *legacy* audio/video call functionality may fail. If you're using [Matrix RTC](configuring-playbook-rtc.md) (for [Element Call](configuring-playbook-element-call.md)), you likely don't have a need to enable coturn. +When Coturn is not enabled, homeservers (like Synapse) would not point to TURN servers and *legacy* audio/video call functionality may fail. If you're using [Matrix RTC](configuring-playbook-matrix-rtc.md) (for [Element Call](configuring-playbook-element-call.md)), you likely don't have a need to enable coturn. ## Adjusting firewall rules