aboutsummaryrefslogtreecommitdiff
path: root/examples/05_command_framework/src
diff options
context:
space:
mode:
Diffstat (limited to 'examples/05_command_framework/src')
-rw-r--r--examples/05_command_framework/src/main.rs6
1 files changed, 2 insertions, 4 deletions
diff --git a/examples/05_command_framework/src/main.rs b/examples/05_command_framework/src/main.rs
index d79f6ab..ca16f23 100644
--- a/examples/05_command_framework/src/main.rs
+++ b/examples/05_command_framework/src/main.rs
@@ -148,9 +148,7 @@ fn main() {
If you want more information about a specific command, just pass the command as argument.")
// Some arguments require a `{}` in order to replace it with contextual information.
// In this case our `{}` refers to a command's name.
- .command_not_found_text("Could not {}, I'm sorry : (")
- // Another argument requiring `{}`, again replaced with the command's name.
- .suggestion_text("How about this command: {}, it's numero uno on the market...!")
+ .command_not_found_text("Could not find: `{}`.")
// On another note, you can set up the help-menu-filter-behaviour.
// Here are all possible settings shown on all possible options.
// First case is if a user lacks permissions for a command, we can hide the command.
@@ -160,7 +158,7 @@ fn main() {
// The last `enum`-variant is `Strike`, which ~~strikes~~ a command.
.wrong_channel(HelpBehaviour::Strike)
// Serenity will automatically analyse and generate a hint/tip explaining the possible
- // cases of a command being ~~striked~~, but only if
+ // cases of ~~strikethrough-commands~~, but only if
// `striked_commands_tip(Some(""))` keeps `Some()` wrapping an empty `String`, which is the default value.
// If the `String` is not empty, your given `String` will be used instead.
// If you pass in a `None`, no hint will be displayed at all.