diff --git a/src/content/docs/channels/discord.md b/src/content/docs/channels/discord.md
index d9d0226..574baff 100644
--- a/src/content/docs/channels/discord.md
+++ b/src/content/docs/channels/discord.md
@@ -39,10 +39,7 @@ Scroll down on the Bot page to **Privileged Gateway Intents** and enable **Messa
 
 ### 4. Set up OAuth2 scopes and permissions
 
-Go to **OAuth2 > URL Generator**. Check these scopes:
-
-- `bot`
-- `applications.commands`
+Go to **OAuth2 > URL Generator**. Check the `bot` scope.
 
 ![OAuth2 scopes selection](/screenshots/output/discord-setup-oauth-scopes.png)
 
diff --git a/src/content/docs/channels/troubleshooting.md b/src/content/docs/channels/troubleshooting.md
index 21b8f9c..5301424 100644
--- a/src/content/docs/channels/troubleshooting.md
+++ b/src/content/docs/channels/troubleshooting.md
@@ -81,7 +81,7 @@ netclaw daemon stop && netclaw daemon start
 
 Daemon start hangs, then Discord shows `disconnected`. Logs show a 30-second timeout waiting for the gateway READY event.
 
-The bot token may be valid but the bot hasn't been invited to any server, so Discord has nothing to initialize. Verify the bot has been added to your server with the correct OAuth2 scopes. Use Discord's [URL Generator](https://discord.com/developers/docs/topics/oauth2#bot-authorization-flow) to create an invite link with `bot` and `applications.commands` scopes.
+The bot token may be valid but the bot hasn't been invited to any server, so Discord has nothing to initialize. Verify the bot has been added to your server. Use Discord's [URL Generator](https://discord.com/developers/docs/topics/oauth2#bot-authorization-flow) to create an invite link with the `bot` scope.
 
 ## ACL and Permissions