Fix event handling documentation (#587)

* Fix broken link to event handling documentation * Add missing space to the event handling documentation
Kraigie · May 8, 2024 · ced832c · ced832c
1 parent dbab163
commit ced832c
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git 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
@@ -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