diff --git a/docs/calls.mdx b/docs/calls.mdx
index 0f1fea978..a4bba12d6 100644
--- a/docs/calls.mdx
+++ b/docs/calls.mdx
@@ -2,12 +2,15 @@
 
 Matrix supports two types of calls:
 
-- Element Call powered by [MatrixRTC](https://half-shot.github.io/msc-crafter/#msc/4143) and [LiveKit](https://github.com/livekit/livekit)
+- Element Call powered by [MatrixRTC][MSC4143] and [LiveKit][livekit-server-github]
 - Legacy calls, supported by a STUN/TURN server.
 
+[MSC4143]: https://github.com/matrix-org/matrix-spec-proposals/pull/4143
+[livekit-server-github]: https://github.com/livekit/livekit
+
 Both types of calls are supported by different sets of clients, but most clients are moving towards MatrixRTC / Element Call.
 
 For either one to work correctly, you have to do some additional setup:
 
-- For legacy calls to work, you need to set up a TURN/STUN server. [Read the TURN guide for tips on how to set up coturn](./calls/turn.mdx)
-- For MatrixRTC / Element Call to work, you have to set up the LiveKit backend. LiveKit also uses TURN/STUN to increase reliability - you can set up its built-in TURN server, or integrate with an existing one. [Read the LiveKit guide](./calls/livekit.mdx)
+- For legacy calls to work, you need to set up a TURN/STUN server. [Read the TURN guide for instructions on how to set up coturn](./calls/turn.mdx)
+- For MatrixRTC / Element Call to work, you have to set up the LiveKit backend, and optionally configure a TURN server for increased reliability. [Read the LiveKit guide](./calls/livekit.mdx)