From ced832c6b31973717ba6b99db62184e21c945139 Mon Sep 17 00:00:00 2001
From: Olivia Palmu <35444188+RocketRace@users.noreply.github.com>
Date: Wed, 8 May 2024 16:27:58 +0300
Subject: [PATCH] Fix event handling documentation (#587)

* Fix broken link to event handling documentation

* Add missing space to the event handling documentation
---
 guides/functionality/event_handling.md | 2 +-
 guides/intro/intro.md                  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/guides/functionality/event_handling.md b/guides/functionality/event_handling.md
index 16d30049f..422c4ea24 100644
--- a/guides/functionality/event_handling.md
+++ b/guides/functionality/event_handling.md
@@ -8,7 +8,7 @@ application can perform an action as a result of that event.
 Nostrum uses [Erlang's `:pg` module](https://www.erlang.org/doc/man/pg.html) to
 determine which consumers are interested in events, via
 `Nostrum.ConsumerGroup`. This allows dynamic subscriptions at runtime, even
-across nodes. Events are dispatched to group members as they appear fromthe
+across nodes. Events are dispatched to group members as they appear from the
 Discord Gateway after ingestion into the cache.
 
 To see the documentation on handling events of provided consumers, please see
diff --git a/guides/intro/intro.md b/guides/intro/intro.md
index 9b4b0abd6..e6d121b29 100644
--- a/guides/intro/intro.md
+++ b/guides/intro/intro.md
@@ -7,7 +7,7 @@ the following:
 
 * [API](api.html) - Methods to interact with the RESTful API (and some other goodies).
 * [State](state.html) - Caches that keep information from Discord fresh at your disposal.
-* [Events](events.html) - Handling events from Discord as they come in.
+* [Events](event_handling.html) - Handling events from Discord as they come in.
 * [Voice](voice.html) - Playing audio through Discord voice channels.
 
 ## Setup