github/Discord.Net
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix some minor typos in docs

Browse Source
This commit is contained in:
Christopher F
2016-10-15 17:35:20 -04:00
parent 77342903bb
commit a35d047333
2 changed files with 9 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/api/index.md
View File

@@ -3,10 +3,11 @@
This is where you will find documentation for all members and objects in Discord.Net This is where you will find documentation for all members and objects in Discord.Net
__Commonly Used Entities__ __Commonly Used Entities__
@Discord.WebSocket
@Discord.WebSocket.DiscordSocketClient * @Discord.WebSocket
@Discord.WebSocket.SocketGuildChannel * @Discord.WebSocket.DiscordSocketClient
@Discord.WebSocket.SocketGuildUser * @Discord.WebSocket.SocketGuildChannel
@Discord.WebSocket.SocketMessage * @Discord.WebSocket.SocketGuildUser
@Discord.WebSocket.SocketRole * @Discord.WebSocket.SocketMessage
* @Discord.WebSocket.SocketRole

2
docs/guides/commands.md
View File

@@ -93,7 +93,7 @@ Command Groups allow you to create a module where commands are prefixed.
To create a group, create a new module and flag it with the To create a group, create a new module and flag it with the
@Discord.Commands.GroupAttribute. @Discord.Commands.GroupAttribute.
>![NOTE] >[!NOTE]
>Groups do not _need_ to be modules. Only classes with commands should >Groups do not _need_ to be modules. Only classes with commands should
>inherit from ModuleBase. If you plan on using a group for strictly >inherit from ModuleBase. If you plan on using a group for strictly
>organizational purposes, there is no reason to make it a module. >organizational purposes, there is no reason to make it a module.