From f8fc5d33464af8e702cbe7423580a2a0e8cfa43d Mon Sep 17 00:00:00 2001
From: Tesseract <92125893+Tesseract-arch@users.noreply.github.com>
Date: Mon, 30 May 2022 18:14:02 +0200
Subject: [PATCH] Update responding-to-buttons.md

Change event name from InteractionCreated to ButtonExecuted
---
 .../int_basics/message-components/responding-to-buttons.md    | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/guides/int_basics/message-components/responding-to-buttons.md b/docs/guides/int_basics/message-components/responding-to-buttons.md
index 7546c6fe2..f11c09039 100644
--- a/docs/guides/int_basics/message-components/responding-to-buttons.md
+++ b/docs/guides/int_basics/message-components/responding-to-buttons.md
@@ -7,7 +7,7 @@ title: Responding to Components
 
 Responding to buttons is pretty simple, there are a couple ways of doing it and we can cover both.
 
-### Method 1: Hooking the InteractionCreated Event
+### Method 1: Hooking the ButtonExecuted Event
 
 We can hook the `ButtonExecuted` event for button type interactions:
 
@@ -34,4 +34,4 @@ public async Task MyButtonHandler(SocketMessageComponent component)
 
 Running it and clicking the button:
 
-![](images/image2.png)
\ No newline at end of file
+![](images/image2.png)