From 86f9aaa0aee99d61b2784ceace5af29dff8b5661 Mon Sep 17 00:00:00 2001
From: Upsided <73066977+Upsidedly@users.noreply.github.com>
Date: Fri, 1 Dec 2023 15:23:34 -0500
Subject: [PATCH] docs: fix typo ("autoCompleteRun" to "autocompleteRun")
 (#249)

Change autoCompleteRun to the correct autocompleteRun
---
 docs/Guide/interaction-handlers/autocomplete.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/Guide/interaction-handlers/autocomplete.mdx b/docs/Guide/interaction-handlers/autocomplete.mdx
index a0e0d1a1..f621b3d0 100644
--- a/docs/Guide/interaction-handlers/autocomplete.mdx
+++ b/docs/Guide/interaction-handlers/autocomplete.mdx
@@ -66,7 +66,7 @@ export class AutocompleteHandler extends InteractionHandler {
 ## Autocomplete run method
 
 Sapphire will first attempt to find the command class for which the autocomplete is for, and if it exists _and_ it has
-the `autoCompleteRun` method set, call it, otherwise we pass it down to interaction handlers. It's the best of both
+the `autocompleteRun` method set, call it, otherwise we pass it down to interaction handlers. It's the best of both
 worlds, and lets you decide which is better for your projects.
 
 The downside of using `autocompleteRun` is if you have multiple commands that have a similar option and use the same