Browse Source

Minor grammatical fixes in Events

pull/826/head
Hsu Still 8 years ago
parent
commit
65b92c667b
1 changed files with 4 additions and 4 deletions
  1. +4
    -4
      docs/guides/concepts/events.md

+ 4
- 4
docs/guides/concepts/events.md View File

@@ -20,7 +20,7 @@ or a named function.


### Safety ### Safety


All events are designed to be thread-safe in that events are executed
All events are designed to be thread-safe; events are executed
synchronously off the gateway task in the same context as the gateway synchronously off the gateway task in the same context as the gateway
task. task.


@@ -33,7 +33,7 @@ offloaded to another task.
This also means that you should not await a task that requests data This also means that you should not await a task that requests data
from Discord's gateway in the same context of an event. Since the from Discord's gateway in the same context of an event. Since the
gateway will wait on all invoked event handlers to finish before gateway will wait on all invoked event handlers to finish before
processing any additional data from the gateway; this will create
processing any additional data from the gateway, this will create
a deadlock that will be impossible to recover from. a deadlock that will be impossible to recover from.


Exceptions in commands will be swallowed by the gateway and logged out Exceptions in commands will be swallowed by the gateway and logged out
@@ -76,8 +76,8 @@ object.


### Tips ### Tips


Many events relating to a Message entity (e.g. `MessageUpdated`)
and `ReactionAdded` rely on the client's message cache, which is
Many events relating to a Message entity (i.e. `MessageUpdated` and
`ReactionAdded`) rely on the client's message cache, which is
**not** enabled by default. Set the `MessageCacheSize` flag in **not** enabled by default. Set the `MessageCacheSize` flag in
[DiscordSocketConfig] to enable it. [DiscordSocketConfig] to enable it.



Loading…
Cancel
Save