complete first draft

Author: notunderctrl

apps/nextra-docs/pages/docs/_meta.json

@@ -1,7 +1,6 @@
 {
     "installation": "Installation",
     "commandkit-setup": "CommandKit Setup",
-    "handler-properties": "Handler Properties",
     "command-file-setup": "Commands Setup",
     "event-file-setup": "Events Setup",
     "validation-file-setup": "Validations Setup"

apps/nextra-docs/pages/docs/validation-file-setup.mdx

@@ -2,7 +2,7 @@ import { Tabs, Callout } from 'nextra/components';
 
 # Validations Setup
 
-Validations are functions that are called before the `run()` function from a command object is called. They can be used for many things, including validating your command object, or even implementing features such as cooldowns where the user will not be able to run the command if a validation functions says so.
+Validations are functions that are called before the `run` function from a command object is called. They can be used for many things, including validating your command object, or even implementing features such as cooldowns where the user will not be able to run the command if a validation functions says so.
 
 Validation functions are called on every command trigger, so it's important to keep them as lightweight as possible.
 
@@ -70,9 +70,9 @@ Validation functions are called on every command trigger, so it's important to k
 
 Within every validation function, you have the ability to check what command is trying to be executed using `commandObj` and the `interaction` object from the parameters and respond accordingly.
 
-The `commandObj` object is what's being exported from your command file (excluding the `run()` function). This means you can access the `data` and `options` property from within your validation function.
+The `commandObj` object is what's being exported from your command file (excluding the `run` function). This means you can access the `data` and `options` property from within your validation function.
 
-The `handler` object is your [CommandKit instance](/api/classes/classcommandkit/).
+The `handler` object is the current CommandKit instance.
 
 ### Stopping the command from running
 

apps/nextra-docs/pages/docs/handler-properties.mdx renamed to apps/nextra-docs/pages/typedef/CommandKit.mdx

@@ -1,6 +1,4 @@
-# Handler properties
-
-When a CommandKit class has been instantiated, it's easier to refer to the resulting object as the "handler". The `handler` object has properties which will be available throughout the whole project (commands, events, validations, etc) by extracting the `handler` object through the parameters. You'll learn more about this when you setup [commands](/docs/command-file-setup), [events](/docs/event-file-setup) and [validations](validation-file-setup).
+# CommandKit
 
 ### `commands`
 

apps/nextra-docs/pages/typedef/ContextMenuCommandProps.mdx

@@ -1 +1,13 @@
 # ContextMenuCommandProps
+
+### `client`
+
+-   Type: [`Client`](https://old.discordjs.dev/#/docs/discord.js/main/class/Client)
+
+### `handler`
+
+-   Type: [`CommandKit`](/typedef/CommandKit)
+
+### `interaction`
+
+-   Type [`ContextMenuCommandInteraction`](https://old.discordjs.dev/#/docs/discord.js/main/class/ContextMenuCommandInteraction)

apps/nextra-docs/pages/typedef/SlashCommandProps.mdx

@@ -1 +1,13 @@
 # SlashCommandProps
+
+### `client`
+
+-   Type: [`Client`](https://old.discordjs.dev/#/docs/discord.js/main/class/Client)
+
+### `handler`
+
+-   Type: [`CommandKit`](/typedef/CommandKit)
+
+### `interaction`
+
+-   Type [`ChatInputCommandInteraction`](https://old.discordjs.dev/#/docs/discord.js/main/class/ChatInputCommandInteraction)

apps/nextra-docs/pages/typedef/_meta.json

@@ -1,5 +1,6 @@
 {
     "CommandData": "CommandData",
+    "CommandKit": "CommandKit",
     "CommandObject": "CommandObject",
     "CommandOptions": "CommandOptions",
     "ContextMenuCommandProps": "ContextMenuCommandProps",