From d42da585e5ad47830c35a397aee2092b4b3ca4f0 Mon Sep 17 00:00:00 2001 From: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> Date: Mon, 9 Nov 2020 12:09:48 +0000 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Matthew Hodgson --- proposals/1772-groups-as-rooms.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/1772-groups-as-rooms.md b/proposals/1772-groups-as-rooms.md index 1f5a1a7f..d4ac126f 100644 --- a/proposals/1772-groups-as-rooms.md +++ b/proposals/1772-groups-as-rooms.md @@ -130,7 +130,7 @@ relationship can be expressed in one of two ways: The `order` key is a string which is used to provide a default ordering of siblings in the room list. (Rooms are sorted based on a lexicographic - ordering of of `order` vales; rooms with no `order` come last. `order`s + ordering of `order` values; rooms with no `order` come last. `order`s which are not strings, or do not consist solely of ascii characters in the range `\x20` (space) to `\x7F` (`~`) are forbidden and should be ignored if received.) @@ -178,7 +178,7 @@ include: * "Secret" rooms: rooms where the admin does not want the room to be advertised as part of a given space, but *does* want the room to form part - of the heirarchy of that space for those in the know. + of the hierarchy of that space for those in the know. ### Sub-spaces