Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix broken link in documentation #587

Merged
merged 2 commits into from
May 8, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion guides/functionality/event_handling.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion guides/intro/intro.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down