From 20828ee3543bf902a4c5152191c76e5d3ad9555c Mon Sep 17 00:00:00 2001 From: Johannes Marbach Date: Wed, 21 May 2025 22:58:24 +0200 Subject: [PATCH] Update content/client-server-api/modules/spaces.md --- content/client-server-api/modules/spaces.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/client-server-api/modules/spaces.md b/content/client-server-api/modules/spaces.md index a565baed..611f0a6a 100644 --- a/content/client-server-api/modules/spaces.md +++ b/content/client-server-api/modules/spaces.md @@ -18,7 +18,7 @@ In the default power level structure, this would be `100`. Clients might wish to go a step further and explicitly ignore notification counts on space-rooms. Membership of a space is defined and controlled by the existing mechanisms which -govern a room: [`m.room.member`](#mroommember), [`m.room.history_visibility`](#mroomhistory_visibility), +govern a room: [`m.room.member`](/client-server-api#mroommember), [`m.room.history_visibility`](/client-server-api#mroomhistory_visibility), and [`m.room.join_rules`](/client-server-api##mroomjoin_rules). Canonical aliases and invites, including third-party invites, still work just as they do in normal rooms as well. Furthermore, spaces can also be published in the [room directory](/client-server-api#published-room-directory) to make them