docs: update event dir docs + fix commandkit references

Author: notunderctrl

apps/website/docs/guide/01-getting-started/02-setup-commandkit.mdx

@@ -33,7 +33,7 @@ By using the CLI to create a base project, you should get a project structure th
 ```
 
 :::info
-The `src/app.ts` file is the main entry point for your application. This file default exports the discord.js client which commandkit loads at runtime. For example, the `src/app.ts` file looks like this:
+The `src/app.ts` file is the main entry point for your application. This file default exports the discord.js client which CommandKit loads at runtime. For example, the `src/app.ts` file looks like this:
 
 ```ts
 import { Client } from 'discord.js';
@@ -50,13 +50,13 @@ client.token = process.env.MY_BOT_TOKEN;
 export default client;
 ```
 
-Notice how we are not calling `client.login()` in this file. This is because commandkit will automatically call `client.login()` for you when the application starts.
+Notice how we are not calling `client.login()` in this file. This is because CommandKit will automatically call `client.login()` for you when the application starts.
 
-Also, you might have noticed that we are not using anything from commandkit in this file. This is because commandkit is designed to reduce boilerplate code and make it easier to build discord bot applications.
+Also, you might have noticed that we are not using anything from CommandKit in this file. This is because CommandKit is designed to reduce boilerplate code and make it easier to build discord bot applications.
 :::
 
 :::info
-The `src/app` directory is a special directory that commandkit understands. All the commands and events in this directory will be automatically registered when the application starts.
+The `src/app` directory is a special directory that CommandKit understands. All the commands and events in this directory will be automatically registered when the application starts.
 :::
 
 ## Development version

apps/website/docs/guide/01-getting-started/06-onApplicationBootstrap-function.mdx

@@ -3,7 +3,7 @@ title: onApplicationBootstrap function
 description: The onApplicationBootstrap function is called when the application is ready.
 ---
 
-The `onApplicationBootstrap` is a lifecycle hook in CommandKit that allows you to execute code when the application is fully initialized and ready to run. This is particularly useful for setting up things like commandkit cache providers, message command prefix resolvers, and other application-wide settings.
+The `onApplicationBootstrap` is a lifecycle hook in CommandKit that allows you to execute code when the application is fully initialized and ready to run. This is particularly useful for setting up things like CommandKit cache providers, message command prefix resolvers, and other application-wide settings.
 
 ## Basic Usage
 

apps/website/docs/guide/07-file-system-conventions/05-events-directory.mdx

@@ -1,20 +1,21 @@
 ---
 title: Events Directory
-description: The events directory is used to define the events for your application.
+description: The events directory is used to define the events for your Discord.js application.
 ---
 
-CommandKit provides a special directory called `events` inside the `src/app` directory. This directory is used to define the events for your application. Each event is defined in its own file, and the file name should match the event name. For example, if you have an event called `messageCreate`, you should create a file called `messageCreate.ts` (or `messageCreate.js`) in the `src/app/events` directory.
+CommandKit provides a special directory called `events` inside the `src/app` directory. This directory is used to define the events for your Discord.js application. Each event is defined in its own directory, and the directory name should match the Discord.js event name. Inside each event directory, you can create multiple function files that will be executed when the event is triggered. For example, if you have an event called `messageCreate`, you should create a directory called `messageCreate` in the `src/app/events` directory, and place your event handler functions inside it.
 
 ```
-| src/
-  | app/
-  | events/
-    | messageCreate/
-      | give-xp.ts
-      | log.ts
-    | ready/
-      | log.ts
-      | initialize.ts
+.
+└── src/
+    └── app/
+        └── events/
+            ├── messageCreate/
+            │   ├── give-xp.ts
+            │   └── log.ts
+            └── ready/
+                ├── log.ts
+                └── initialize.ts
 ```
 
 CommandKit also supports using custom events in the `events` directory. Custom events must be defined in a namespaced directory, which are handled by the active plugins. For example, if you have a custom event called `guildMemberBoost`, you can create a file called `src/app/events/(custom)/guildMemberBoost/handler.ts` which will be handled by the appropriate active plugins.

apps/website/docs/guide/07-file-system-conventions/07-command-file.mdx

@@ -12,7 +12,7 @@ The command file can export multiple handler functions, such as:
 - `userContextMenu`: This function is executed when the command is triggered by a user context menu event.
 - `messageContextMenu`: This function is executed when the command is triggered by a message context menu event.
 
-When defining a command, if you export `userContextMenu` or `messageContextMenu`, commandkit will automatically register the command as a context menu command without you having to explicitly define them as one.
+When defining a command, if you export `userContextMenu` or `messageContextMenu`, CommandKit will automatically register the command as a context menu command without you having to explicitly define them as one.
 
 ## Example command