diff --git a/docs/interactions/application-commands.mdx b/docs/interactions/application-commands.mdx
index 02b42f00a7..27ca3796dc 100644
--- a/docs/interactions/application-commands.mdx
+++ b/docs/interactions/application-commands.mdx
@@ -28,7 +28,7 @@ Application commands are native ways to interact with apps in the Discord client
 | default_permission?        | ?boolean                                                                                                                             | Not recommended for use as field will soon be deprecated. Indicates whether the command is enabled by default when the app is added to a guild, defaults to `true`                                                                                             | all                 |
 | nsfw?                      | boolean                                                                                                                              | Indicates whether the command is [age-restricted](/docs/interactions/application-commands#agerestricted-commands), defaults to `false`                                                                                                                         | all                 |
 | integration_types?         | list of [integration types](/docs/resources/application#application-object-application-integration-types)                            | [Installation contexts](/docs/resources/application#installation-context) where the command is available, only for globally-scoped commands. Defaults to your app's [configured contexts](/docs/resources/application#setting-supported-installation-contexts) | all                 |
-| contexts?                  | ?list of [interaction context types](/docs/interactions/receiving-and-responding#interaction-object-interaction-context-types)       | [Interaction context(s)](/docs/interactions/receiving-and-responding#interaction-object-interaction-context-types) where the command can be used, only for globally-scoped commands. By default, all interaction context types included for new commands.      | all                 |
+| contexts?                  | ?list of [interaction context types](/docs/interactions/receiving-and-responding#interaction-object-interaction-context-types)       | [Interaction context(s)](/docs/interactions/receiving-and-responding#interaction-object-interaction-context-types) where the command can be used, only for globally-scoped commands.                                                                           | all                 |
 | version                    | snowflake                                                                                                                            | Autoincrementing version identifier updated during substantial record changes                                                                                                                                                                                  | all                 |
 | handler?                   | one of [command handler types](/docs/interactions/application-commands#application-command-object-entry-point-command-handler-types) | Determines whether the interaction is handled by the app's interactions handler or by Discord                                                                                                                                                                  | PRIMARY_ENTRY_POINT |
 
@@ -291,8 +291,6 @@ The interaction contexts for a command determines where in the Discord client it
 
 There are three [interaction context types](/docs/interactions/receiving-and-responding#interaction-object-interaction-context-types) that correspond to different surfaces: `GUILD` (`0`), `BOT_DM` (`1`), and `PRIVATE_CHANNEL` (`2`). However, the `PRIVATE_CHANNEL` interaction context is only meaningful for commands installed to a user (when the command's `integration_types` includes `USER_INSTALL`).
 
-By default, `contexts` includes all interaction context types.
-
 ## Permissions
 
 Application command permissions allow your app to enable or disable commands for up to 100 users, roles, and channels within a guild. Command permissions can also be updated by users in the client if they have the necessary permissions.