diff --git a/docs/configuring-playbook-appservice-draupnir-for-all.md b/docs/configuring-playbook-appservice-draupnir-for-all.md
index 4743977eb..36e85eafd 100644
--- a/docs/configuring-playbook-appservice-draupnir-for-all.md
+++ b/docs/configuring-playbook-appservice-draupnir-for-all.md
@@ -48,13 +48,13 @@ matrix_appservice_draupnir_for_all_enabled: true
 matrix_appservice_draupnir_for_all_config_adminRoom: "MANAGEMENT_ROOM_ALIAS_HERE"
 ```
 
-### Running Both Bot Mode and Appservice Mode
+### Running both bot mode and appservice mode
 
-When running both [Bot mode](./configuring-playbook-bot-draupnir.md) and appservice mode the playbook will force restart
-the bot if running a non release tag like `latest` or `main` or development builds.
-This is due to the conditional restart logic not being able to tell when a update happened correctly.
+When running both [bot mode](./configuring-playbook-bot-draupnir.md) and appservice mode, the playbook will force-restart
+the bot if running a non-release tag like `latest` or `main` or a development build.
+This is due to the conditional restart logic not being able to reliably tell when an update happened.
 
-Conditional restarts work perfectly for all tags when running only one of these two operating modes.
+Conditional restarts work correctly for all tags when running only one of these two operating modes.
 
 ### Extending the configuration
 
diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md
index eeee41641..28806adf0 100644
--- a/docs/configuring-playbook-bot-draupnir.md
+++ b/docs/configuring-playbook-bot-draupnir.md
@@ -82,13 +82,13 @@ matrix_bot_draupnir_login_native: true
 matrix_bot_draupnir_config_managementRoom: "MANAGEMENT_ROOM_ID_HERE"
 ```
 
-### Running Both Bot Mode and Appservice Mode
+### Running both bot mode and appservice mode
 
-When running both Bot mode and [appservice mode](./configuring-playbook-appservice-draupnir-for-all.md)(Draupnir for all) the
-playbook will force restart the bot if running a non release tag like `latest` or `main` or development builds.
-This is due to the conditional restart logic not being able to tell when a update happened correctly.
+When running both bot mode and [appservice mode (Draupnir for all)](./configuring-playbook-appservice-draupnir-for-all.md), the
+playbook will force-restart the bot if running a non-release tag like `latest` or `main` or a development build.
+This is due to the conditional restart logic not being able to reliably tell when an update happened.
 
-Conditional restarts work perfectly for all tags when running only one of these two operating modes.
+Conditional restarts work correctly for all tags when running only one of these two operating modes.
 
 ### Create and invite the bot to the management room