From 22f965ce5f21007924296ca7bc9850b0eb7d66a3 Mon Sep 17 00:00:00 2001
From: DerEchtePilz <81232921+DerEchtePilz@users.noreply.github.com>
Date: Wed, 10 Apr 2024 23:45:35 +0200
Subject: [PATCH] Revert "Minor modification in docs/commandfailures"

This reverts commit ea35f9c117c5345dc04b8aae22fd8429f317cb23.
---
 docs/9.3.0/commandfailures.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/9.3.0/commandfailures.html b/docs/9.3.0/commandfailures.html
index 27c1685b15..f80be445b9 100644
--- a/docs/9.3.0/commandfailures.html
+++ b/docs/9.3.0/commandfailures.html
@@ -163,8 +163,8 @@ <h1 id="handling-command-failures"><a class="header" href="#handling-command-fai
 <p>Sometimes, you want your command to fail on purpose. This is the way to &quot;gracefully&quot; handle errors in your command execution. This is performed by throwing any of the following methods:</p>
 <pre><code class="language-java">throw CommandAPI.failWithString(String message);
 throw CommandAPI.failWithMessage(Message message);
-throw CommandAPIBukkit.failWithBaseComponents(BaseComponent... message);
-throw CommandAPIBukkit.failWithAdventureComponent(Component message);
+throw CommandAPI.failWithBaseComponents(BaseComponent... message);
+throw CommandAPI.failWithAdventureComponent(Component message);
 </code></pre>
 <p>When the CommandAPI handles the fail method, it will cause the command to return a <em>success value</em> of 0, to indicate failure.</p>
 <div class="example">