Update failure methods to reflect relocated methods to platform-specific classes (#19)

Author: MrEisbear

docs/en/create-commands/executors/handle-failures.md

@@ -1,5 +1,6 @@
 ---
 order: 6
+preferences: ["paper-spigot"]
 authors:
   - DerEchtePilz
   - willkroboth
@@ -11,14 +12,26 @@ authors:
 
 Sometimes, you want your command to fail on purpose. This is the way to "gracefully" handle errors in your command execution. This is performed by throwing any of the following methods:
 
+<div class="paper">
+
 ```java
 throw CommandAPI.failWithString(String message);
 throw CommandAPI.failWithMessage(Message message);
-throw CommandAPIBukkit.failWithBaseComponents(BaseComponent... message);
-throw CommandAPIBukkit.failWithAdventureComponent(Component message);
-throw CommandAPIBukkit.failWithAdventureComponent(ComponentLike message);
+throw CommandAPIPaper.failWithAdventureComponent(Component message);
+throw CommandAPIPaper.failWithAdventureComponent(ComponentLike message);
 ```
 
+</div>
+<div class="spigot">
+
+```java
+throw CommandAPI.failWithString(String message);
+throw CommandAPI.failWithMessage(Message message);
+throw CommandAPISpigot.failWithBaseComponents(BaseComponent... message);
+```
+
+</div>
+
 When the CommandAPI handles the fail method, it will cause the command to return a _success value_ of 0, to indicate failure.
 
 ::::tip Example - Command failing for an element not in a list
@@ -39,4 +52,4 @@ Therefore, to gracefully handle this with a proper error message, we use one of
 :::info
 In general, it's a good idea to handle unexpected cases with one of the `CommandAPI.failWithXXX()` methods.
 Most arguments used by the CommandAPI will have their own built-in failsafe system _(e.g., the `EntitySelectorArgument` will not execute the command executor if it fails to find an entity)_, so this feature is for those extra cases.
-:::
+:::