From 97d1a64a6e673b47fad2b6bcb1eeb3914a6c2ba1 Mon Sep 17 00:00:00 2001 From: Luca Zeuch Date: Sun, 17 Nov 2024 13:05:41 +0100 Subject: [PATCH] reference: be consistent with example code Signed-off-by: Luca Zeuch --- content/docs/reference/custom-interactions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/reference/custom-interactions.md b/content/docs/reference/custom-interactions.md index 7a3d108..37053c3 100644 --- a/content/docs/reference/custom-interactions.md +++ b/content/docs/reference/custom-interactions.md @@ -183,8 +183,8 @@ We have also set the `max_values` to 3, and we haven't set a `min_values` argume server member could select anywhere between 1 and 3 of these options. If the member selected all three options and submitted it (which would send an interaction to YAGPDB), while [parsing -that interaction](#parsing-an-interaction) the `.Values` context data would be `["opt-1" "duck-option" "opt-3"]`. This is -because in our code defining the select menu, we defined the `"value"` args of our menu options as `opt-1`, +that interaction](#parsing-an-interaction) the `.Values` context data would be `["opt-1" "duck-option" "third-option"]`. +This is because in our code defining the select menu, we defined the `"value"` args of our menu options as `opt-1`, `duck-option`, and `third-option`. If the member only selected the "Half a Duck" option, `.Values` would be `["third-option"]`.