From ee8ba5a3219e95647c38cbba066f4acd811f38c4 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Thu, 12 Dec 2024 22:25:24 +0900 Subject: [PATCH] Update docs/configuring-playbook-appservice-draupnir-for-all.md: edit instruction of setting an alias to the management room Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-appservice-draupnir-for-all.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-appservice-draupnir-for-all.md b/docs/configuring-playbook-appservice-draupnir-for-all.md index 997a4cc47..29a0129ab 100644 --- a/docs/configuring-playbook-appservice-draupnir-for-all.md +++ b/docs/configuring-playbook-appservice-draupnir-for-all.md @@ -32,9 +32,11 @@ As noted in the Draupnir install instructions the control room is sensitive. The -### Give your main management room an alias +### Set an alias to the management room -Give the room from step 1 an alias. This alias can be anything you want and its recommended for increased security during the setup phase of the bot that you make this alias be a random string. You can give your room a secondary human readable alias when it has been locked down after setup phase. +Next, set an alias to the management room. + +This alias can be anything you want. However, for increased security during the setup phase, it is recommended to make this alias be a random string. When it has been locked down after setup phase, you can give your room a secondary human readable alias. ## Adjusting the playbook configuration