From d060142a8df05bae77786e61c7f9bde76b0e5e19 Mon Sep 17 00:00:00 2001 From: Johannes Marbach Date: Thu, 20 Mar 2025 10:36:27 +0100 Subject: [PATCH] Line-wrap first paragraph, update link and parameters --- data/event-schemas/schema/m.room.topic.yaml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/data/event-schemas/schema/m.room.topic.yaml b/data/event-schemas/schema/m.room.topic.yaml index 4b4c5000..c37ecf03 100644 --- a/data/event-schemas/schema/m.room.topic.yaml +++ b/data/event-schemas/schema/m.room.topic.yaml @@ -2,7 +2,12 @@ allOf: - $ref: core-event-schema/state_event.yaml description: |- - A topic is a short message detailing what is currently being discussed in the room. It can also be used as a way to display extra information about the room, which may not be suitable for the room name. The room topic can also be set when creating a room using `/createRoom` with the `topic` key. + A topic is a short message detailing what is currently being discussed + in the room. It can also be used as a way to display extra information + about the room, which may not be suitable for the room name. The room + topic can be set when creating a room using + [`/createRoom`](client-server-api/#post_matrixclientv3createroom), either + with the `topic` key or by specifying a full event in `initial_state`. In order to prevent formatting abuse in room topics, clients SHOULD limit the length of topics during both entry and display, for instance,