From dd8aaa0d66aa6947f883f8c7e9df8fec9450e98c Mon Sep 17 00:00:00 2001 From: Johannes Marbach Date: Wed, 21 May 2025 22:57:43 +0200 Subject: [PATCH] Update content/client-server-api/modules/spaces.md --- content/client-server-api/modules/spaces.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/client-server-api/modules/spaces.md b/content/client-server-api/modules/spaces.md index 0c81c61e..a565baed 100644 --- a/content/client-server-api/modules/spaces.md +++ b/content/client-server-api/modules/spaces.md @@ -19,9 +19,9 @@ 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), -and [`m.room.join_rules`](#mroomjoin_rules). Canonical aliases and invites, including +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](#room-directory) to make them +spaces can also be published in the [room directory](/client-server-api#published-room-directory) to make them discoverable. All other aspects of regular rooms are additionally carried over, such as the