Hi! As discussed in [#matrix-ops:ubuntu.com](https://matrix.to/#/%23matrix-ops%3Aubuntu.com/%24V2El3HbGblfoiT8Ayl5YKHlMIl4qU4H2StlLjBzuSJI?via=ubuntu.com&via=matrix.org&via=xentonix.net), here's my follow up post with feedback around the documentation.

General formatting:
- Make room references URLs, so they can be clicked: #matrix-ops:ubuntu.com -> \[#matrix-ops:ubuntu.com\](https://matrix.to/#/#matrix-ops:ubuntu.com)
- Anchors (titles) don't appear to have a hyperlink to copy their location

Some details I've noticed:
- [Guide to deleting a room](https://ubuntu.com/community/communications/matrix/room-maintenance#how-to-delete-a-room-2) omits making the room private, this allows people to join back via room ID after being kicked, or even never having been in the room
 This can be solved by adding an extra step, assuming users use Element:
  - Open room settings
  - Go to Security & Privacy
  - Under Access, select "Private (invite only)"

- [Guide to configure mjolnir](https://ubuntu.com/community/communications/matrix/rooms-spaces-process#invite-moderator-bot-5) mentions incorrect command `!mjolnir check status`, the correct command is `!mjolnir status`.

- [Explanation of admin permissions for mjolnir](https://ubuntu.com/community/communications/matrix/moderator-bot#why-do-we-need-to-grant-admin-permissions-to-the-moderator-bot-3) gives incorrect reasoning, the given reasons refer to the bot being a Synapse Administrator user, *not* a room administrator.
  Administrator permissions in a room are required to configure certain properties, such as what servers aren't allowed to interact with the room (`m.room.server_acls`) and who is administrator, moderator or muted (`m.room.power_levels`), according to a room's default power levels.

- [General hints section on creating rooms](https://ubuntu.com/community/communications/matrix/room-properties#security-privacy-2) would probably be a good fit in the guide on creating rooms.
It's important that room administrators are aware of the defederation and encryption options before they create the room, given that configuring them is irreversible.
Also worth noting that encryption for public rooms has a large known performance impact on sending messages. For most servers, sending a message in a 500 member encrypted room can take up to 30 seconds assuming low network latency.


There may be more things I missed, though I think these are some important details to be clarified.

Regards,
Emma [it/its] (Matrix: [rory.gay](https://matrix.to/#/@emma:rory.gay), [conduit.rory.gay](https://matrix.to/#/@emma:conduit.rory.gay)), member of the Rory& System