learn/interactions: review feedback v1

Signed-off-by: Luca Zeuch <[email protected]>

Author: l-zeuch

content/learn/advanced/custom-interactions/creating-interactive-elements.md

@@ -133,9 +133,11 @@ the second field is a text input with a default value, and the third field is a
 least 100 characters. The custom ID is set to `modals-my_first_modal`, which helps us identifying the modal when we use
 a modal submission trigger for a custom command.
 
+![My first modal example](modal_example.png)
+
 ## Multiple Components
 
-You learnt how to create messages with just one component attached to it, but the whole point of components is to have
+You learned how to create messages with just one component attached to it, but the whole point of components is to have
 *a lot* of them available. Let's start with adding some more buttons!
 
 ### More Buttons
@@ -199,7 +201,7 @@ created menu to the `"menu"` key of the complex message builder, and sending sai
 
 ### Ordering Components
 
-Let's say we want to play Tic Tac Toe. If we just add nine buttons into the same slice in our complex message builder,
+Let's say we want to play Tic-Tac-Toe. If we just add nine buttons into the same slice in our complex message builder,
 they will just fill the first row with five buttons, and the second row with four buttons, which is definitely not what
 we are looking for. The solution is to tell YAGPDB precisely how the rows look like and then pass each row to the
 `"button"` or `"menu"` key.
@@ -215,7 +217,7 @@ we are looking for. The solution is to tell YAGPDB precisely how the rows look l
 {{ sendMessage nil $message }}
 ```
 
-![Tic Tac Toe](tictactoe.png)
+![Tic-Tac-Toe](tictactoe.png)
 
 #### Action Rows
 
@@ -250,10 +252,10 @@ formula like reactions do. Emojis in components follow the [partial emoji
 object](https://discord.com/developers/docs/resources/emoji#emoji-object) structure, however only the ID *or* the Name
 fields are required, depending on if you are using a custom emoji or not.
 
-| Field | Description                                                                                          |
-| ----- | ---------------------------------------------------------------------------------------------------- |
-| ID    | ID of the emoji, only necessary when using Custom Emoji.                                             |
-| Name  | Name of the emoji, use the unicode character here. Only necessary when using builtin unicode emojis. |
+| Field | Description                                                                                           |
+| ----- | ----------------------------------------------------------------------------------------------------- |
+| ID    | ID of the emoji, only necessary when using Custom Emoji.                                              |
+| Name  | Name of the emoji, use the unicode character here. Only necessary when using built-in unicode emojis. |
 
 ```yag
 {{ $unicodeEmojiButton := cbutton "emoji" (sdict "name" "😀") }}

content/learn/advanced/custom-interactions/introduction.md

@@ -12,7 +12,7 @@ language before learning interactions.
 {{< /callout >}}
 
 Interactions within Discord allow server members to use alternative, built-in features to trigger bots to take action
-other than messages or reactions. These features include builtin buttons, dropdown selection menus, or submitting a
+other than messages or reactions. These features include built-in buttons, dropdown selection menus, or submitting a
 modal (basically a pop-up form). Within custom commands it is possible to not only create and customize these new
 interactive features, but respond to them as well, opening up new possibilities for ephemeral message responses, modals,
 and more within custom commands.
@@ -47,13 +47,14 @@ On the following pages, we will use the listed terms with their respective defin
 the Discord API.
 
 Interaction
-: A user engaging with YAGPDB through one of Discord's builtin features: Clicking a button, Making a
+: A user engaging with YAGPDB through one of Discord's built-in features: Clicking a button, Making a
 selection with a select menu, or Submitting a modal.
 
 Response
-: YAGPDB is required to respond promptly after receiving an interaction by either sending a message or modal, or by
-updating the message on which the interaction was triggered. If it does not do this, the user triggering the interaction
-will see a "This application did not respond" error. The bot cannot respond to an interaction more than once.
+: YAGPDB is required to respond promptly -- that is, within three (3) seconds -- after receiving an interaction by
+either sending a message or modal, or by updating the message on which the interaction was triggered. If it does not do
+this, the user triggering the interaction will see a "This application did not respond" error. The bot cannot respond to
+an interaction more than once.
 
 Followup
 : Since YAGPDB may only *respond* to an *interaction* once, it is subsequently required to send an interaction

content/learn/advanced/custom-interactions/parsing-an-interaction.md

@@ -31,7 +31,6 @@ parse out arguments in your custom ID, and use them in your response.
 menu and defining the options, the `"value"` field for each option defines which values will show up in this slice if
 chosen. A modal's values are simply the values of each field in order.
 
-
 ## Parsing Buttons
 
 As buttons do not provide any `.Values` data, we have to rely on the custom ID to pass around any data that a button may