Categorize Event Reference events

[pandaninjas]

trafficstars

Summary

This pull requests resolves #455. This classifies events in the documentation. Let me know if you want anything changed

Information

• [ ] This PR fixes an issue.
• [x] This PR adds something new (e.g. new method or parameters).
• [ ] This PR is a breaking change (e.g. methods or parameters removed/renamed).
• [x] This PR is not a code change (e.g. documentation, README, typehinting, examples, ...).

Checklist

• [x] I have searched the open pull requests for duplicates.
• [ ] If code changes were made then they have been tested.
  • [ ] I have updated the documentation to reflect the changes.
• [ ] If type: ignore comments were used, a comment is also left explaining why.

[plun1331]

The diff I'm looking at displays the entire API reference as modified, and as such I can't really see what changes were made.

[pandaninjas]

The diff I'm looking at displays the entire API reference as modified, and as such I can't really see what changes were made.

I'm going to see what I can do about that.

[pandaninjas]

Fixed in latest commit

[baronkobama]

I feel at the very least these categories should be alphabetically sorted as these sections feel kinda messy. Atop of that, I'm not sure if having an "other" section is a great idea and it'd probably be better to just be more specific in each section's title.

[pandaninjas]

I feel at the very least these categories should be alphabetically sorted as these sections feel kinda messy. Atop of that, I'm not sure if having an "other" section is a great idea and it'd probably be better to just be more specific in each section's title.

For the other section, do you want me to create a section for each event in other?

[Lulalaby]

@pandaninjas please resolve conflicts @Pycord-Development/maintainers please review

[pandaninjas]

Oops, I accidentally discarded all my commits

[pandaninjas]

I can't seem to make GitHub recognize the new commits on this branch, I've opened a new PR #1644