From 0d1605283cd685fb52a8628e9d27660b02ac5d41 Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Tue, 2 Aug 2022 12:42:02 -0600 Subject: [PATCH] Minor spelling fixes --- proposals/3818-copy-room-type-on-upgrade.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/3818-copy-room-type-on-upgrade.md b/proposals/3818-copy-room-type-on-upgrade.md index c0c2bd46..6e38abd8 100644 --- a/proposals/3818-copy-room-type-on-upgrade.md +++ b/proposals/3818-copy-room-type-on-upgrade.md @@ -6,12 +6,12 @@ rooms staying the same type leading to trouble. ## Proposal -This MSC proposes that the room upgade API MUST copy the [room type](https://spec.matrix.org/v1.2/client-server-api/#types) +This MSC proposes that the room upgrade API MUST copy the [room type](https://spec.matrix.org/v1.2/client-server-api/#types) over to the new room. Otherwise clients cannot trust that to happen and [Spaces](https://spec.matrix.org/v1.2/client-server-api/#spaces) or [MSC3588](https://github.com/matrix-org/matrix-spec-proposals/pull/3588) Story rooms may incorrectly become normal rooms breaking user-experience. -The Spec currently specfies this in [section 11.32.3. server behaviour](https://spec.matrix.org/v1.2/client-server-api/#server-behaviour-16): +The Spec currently specifies this in [section 11.32.3. server behaviour](https://spec.matrix.org/v1.2/client-server-api/#server-behaviour-16): > 2. Creates a replacement room with a `m.room.create` event containing a `predecessor` field and the applicable `room_version`.