Final fixup

Author: Strokkur424

docs/paper/dev/api/command-api/arguments/minecraft-arguments.mdx

@@ -6,7 +6,7 @@ toc_max_heading_level: 4
 ---
 
 # Minecraft Arguments
-The [Arguments and Literals](./arguments-and-literals) page covers the most used, native Brigadier arguments. But Minecraft (and Paper) defines a few more. These can be accessed
+The [Arguments and Literals](../basics/arguments-and-literals) page covers the most used, native Brigadier arguments. But Minecraft (and Paper) defines a few more. These can be accessed
 in a static context using the `ArgumentTypes` class. We will go over all of those in this section.
 
 ## Quick overview
@@ -16,7 +16,7 @@ A quick overview of all possible arguments is defined here:
 |-----------------------------------------|--------------------------------|----------------------------------------------------------------------------------------|
 | `blockPosition()`                       | BlockPositionResolver          | [Block Position Argument](./location-arguments#block-position-argument)                |
 | `blockState()`                          | BlockState                     | [Block State Argument](./bukkit-arguments#block-state-argument)                        |
-| `component()`                           | Component (Kyori)              | [Adventure Component Argument](./adventure-arguments#adventure-component-argument)     |
+| `component()`                           | Component (Kyori)              | [Component Argument](./adventure-arguments#component-argument)                         |
 | `doubleRange()`                         | DoubleRangeProvider            | [Double Range argument](./predicate-arguments#double-range-argument)                   |
 | `entity()`                              | EntitySelectorArgumentResolver | [Entity Argument](./entity-player-arguments#entity-argument)                           |
 | `entities()`                            | EntitySelectorArgumentResolver | [Entities Argument](./entity-player-arguments#entities-argument)                       |
@@ -27,7 +27,7 @@ A quick overview of all possible arguments is defined here:
 | `integerRange()`                        | IntegerRangeProvider           | [Integer Range Argument](./predicate-arguments#integer-range-argument)                 |
 | `itemPredicate()`                       | ItemStackPredicate             | [Item Predicate Argument](./predicate-arguments#item-predicate-argument)               |
 | `itemStack()`                           | ItemStack                      | [ItemStack Argument](./bukkit-arguments#itemstack-argument)                            |
-| `key()`                                 | Key (Kyori)                    | [Adventure Key Argument](./adventure-arguments#adventure-key-argument)                 |
+| `key()`                                 | Key (Kyori)                    | [Key Argument](./adventure-arguments#key-argument)                                     |
 | `namedColor()`                          | NamedTextColor (Kyori)         | [Named Color Argument](./adventure-arguments#named-color-argument)                     |
 | `namespacedKey()`                       | NamespacedKey (Bukkit)         | [Bukkit NamespacedKey Argument](./bukkit-arguments#bukkit-namespacedkey-argument)      |
 | `objectiveCriteria()`                   | Criteria                       | [Objective Criteria Argument](./enum-arguments#objective-criteria-argument)            |
@@ -36,7 +36,7 @@ A quick overview of all possible arguments is defined here:
 | `playerProfiles()`                      | PlayerProfileListResolver      | [Player Profiles Argument](./entity-player-arguments#player-profiles-argument)         |
 | `resource(RegistryKey)`                 | (Depends on RegistryKey)       | [Resource Argument](./registry-arguments#resource-argument)                            |
 | `resourceKey(RegistryKey)`              | (Depends on RegistryKey)       | [Resource Key Argument](./registry-arguments#resource-key-argument)                    |
-| `style()`                               | Style (Kyori)                  | [Adventure Style Argument](./adventure-arguments#adventure-style-argument)             |
+| `style()`                               | Style (Kyori)                  | [Style Argument](./adventure-arguments#adventure-style-argument)                       |
 | `signedMessage()`                       | SignedMessageResolver          | [Signed Message Argument](./adventure-arguments#signed-message-argument)               |
 | `scoreboardDisplaySlot()`               | DisplaySlot                    | [Scoreboard Display Slot Argument](./enum-arguments#scoreboard-display-slot-argument)  |
 | `time(float mintime)`                   | Integer                        | [Time Argument](./bukkit-arguments#time-argument)                                      |

docs/paper/dev/api/command-api/basics/introduction.mdx

@@ -14,7 +14,7 @@ It offers many advantages above the previously widely used Bukkit command system
 
 :::info
 
-To see a comparison between the new Brigadier system and the old Bukkit system, check out [this page](./comparison)
+To see a comparison between the new Brigadier system and the old Bukkit system, check out [this page](../misc/comparison-bukkit-brigadier)
 
 :::
 

docs/paper/dev/api/command-api/misc/comparison-bukkit-brigadier.mdx

@@ -59,7 +59,7 @@ As you can see, you have to do a lot of manual checking in order to register a s
 the Brigadier api do it?
 
 ### The new Paper way
-First, we need to retrieve a `LiteralCommandNode<CommandSourceStack>`. That's a special Brigadier class that holds some sort of [command tree](./command-tree). 
+First, we need to retrieve a `LiteralCommandNode<CommandSourceStack>`. That's a special Brigadier class that holds some sort of [command tree](../basics/command-tree). 
 In our case, it is the root of our command. We can do that by running `Commands.literal(final String literal)`, which returns a 
 `LiteralArgumentBuilder<CommandSourceStack>`, where we can define some arguments and executors. Once we are done, we can call
 `LiteralArgumentBuilder#build()` to retrieve our build `LiteralCommandNode`, which we can then register. That sounds complicated at first,