From bd5e2f9b6736621461160362a2bd079b4ac709d2 Mon Sep 17 00:00:00 2001 From: Ilay Nahman Date: Thu, 17 Feb 2022 19:39:21 +0200 Subject: [PATCH] Fixed typos Changed frist to first and dont to don't --- .../slash-commands/creating-slash-commands.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/guides/int_basics/application-commands/slash-commands/creating-slash-commands.md b/docs/guides/int_basics/application-commands/slash-commands/creating-slash-commands.md index 9e35de285..a0a7d6fe3 100644 --- a/docs/guides/int_basics/application-commands/slash-commands/creating-slash-commands.md +++ b/docs/guides/int_basics/application-commands/slash-commands/creating-slash-commands.md @@ -70,14 +70,14 @@ public async Task Client_Ready() // Let's do our global command var globalCommand = new SlashCommandBuilder(); globalCommand.WithName("first-global-command"); - globalCommand.WithDescription("This is my frist global slash command"); + globalCommand.WithDescription("This is my first global slash command"); try { // Now that we have our builder, we can call the CreateApplicationCommandAsync method to make our slash command. await guild.CreateApplicationCommandAsync(guildCommand.Build()); - // With global commands we dont need the guild. + // With global commands we don't need the guild. await client.CreateGlobalApplicationCommandAsync(globalCommand.Build()); // Using the ready event is a simple implementation for the sake of the example. Suitable for testing and development. // For a production bot, it is recommended to only run the CreateGlobalApplicationCommandAsync() once for each command.