fix: revert some unexpect changes

MC-XiaoHei · MC-XiaoHei · commit 8125857c4515 · 2024-12-11T20:01:08.000+08:00
diff --git a/docs/en/create-commands/arguments/listed-arguments.md b/docs/en/create-commands/arguments/listed-arguments.md
@@ -9,7 +9,7 @@ authors:
 
 # Listed arguments
 
-Arguments have a setting that determines whether they’re present in the [`CommandArguments args`](./command-arguments) that is populated when executing a command.
+Arguments have a setting that determines whether or not they are present in the [`CommandArguments args`](./command-arguments) that is populated when executing a command.
 
 By default, the `LiteralArgument` has this setting set to `false`, hence the literal values are _not_ present in the [`CommandArguments args`](command-arguments).
 
diff --git a/docs/en/create-commands/arguments/optional-arguments.md b/docs/en/create-commands/arguments/optional-arguments.md
@@ -142,7 +142,7 @@ A.combineWith(B)
 This does two things:
 
 1. When checking optional argument constraints the argument `B` will be ignored so the `OptionalArgumentException` will not be thrown
-2. It allows you to define additional optional arguments afterward which can only be entered if argument `B` has been entered
+2. It allows you to define additional optional arguments afterwards which can only be entered if argument `B` has been entered
 
 This is how you would add another optional `PlayerArgument` (here simplified to `C`):
 
diff --git a/docs/en/create-commands/arguments/suggestions/async-suggestions.md b/docs/en/create-commands/arguments/suggestions/async-suggestions.md
@@ -10,7 +10,7 @@ authors:
 
 # Asynchronous suggestions
 
-In addition to normal suggestions, safely typed suggestions and suggestions with tooltips, the CommandAPI can support computing the list of suggestions to send to a player asynchronously. This allows you to perform suggestions independent of the main server thread, which is useful for slow operations, such as:
+In addition to normal suggestions, safely-typed suggestions and suggestions with tooltips, the CommandAPI can support computing the list of suggestions to send to a player asynchronously. This allows you to perform suggestions independent of the main server thread, which is useful for slow operations, such as:
 
 - Retrieving suggestions from a remote database
 - Retrieving information from the web
diff --git a/docs/en/create-commands/arguments/suggestions/safe-suggestions.md b/docs/en/create-commands/arguments/suggestions/safe-suggestions.md
@@ -9,7 +9,7 @@ authors:
 
 # Type-Safe suggestions
 
-So far, we've covered how to replace suggestions using the `replaceSuggestions()` method. The issue with using strings for suggestion listings is that they’re prone to errors - it is possible to suggest something, which is not actually a valid argument, which makes that suggestion unusable. As a result, some arguments include the `replaceSafeSuggestions()`, which provides type-safety checks for argument suggestions, as well as automatic "Bukkit-to-suggestion" conversion.
+So far, we've covered how to replace suggestions using the `replaceSuggestions()` method. The issue with using strings for suggestion listings is that they’re prone to errors - it is possible to suggest something which is not actually a valid argument, which makes that suggestion unusable. As a result, some arguments include the `replaceSafeSuggestions()`, which provides type-safety checks for argument suggestions, as well as automatic "Bukkit-to-suggestion" conversion.
 
 The whole point of the safe argument suggestions method is that parameters entered in this method are **guaranteed** to work.
 
@@ -40,7 +40,7 @@ SafeSuggestions<T> tooltipsAsync(Function<SuggestionInfo, CompletableFuture<Tool
 
 Not all arguments support safe suggestions. This is mostly due to implementation constraints or inadequate support by the Bukkit API.
 
-The list of supported arguments is displayed in the following table. The parameter `T` (shown in the method the signatures above) are also provided for each argument. This parameter is the same as the cast argument described in [Argument Casting](../command-arguments#argument-casting), except for a few exceptions which are outlined in **bold**.
+The list of supported arguments are displayed in the following table. The parameter `T` (shown in the method signatures above) are also provided for each argument. This parameter is the same as the cast argument described in [Argument Casting](../command-arguments#argument-casting), except for a few exceptions which are outlined in **bold**.
 
 |                                                                                      Argument | Class (T)                                      |
 |----------------------------------------------------------------------------------------------:|:-----------------------------------------------|
diff --git a/docs/en/create-commands/arguments/suggestions/string-suggestions.md b/docs/en/create-commands/arguments/suggestions/string-suggestions.md
@@ -67,7 +67,7 @@ We can then use this to generate our suggested list of friends:
 
 ## Suggestions depending on previous arguments
 
-The `strings(Function<SuggestionInfo, String[]>)` method can also suggest arguments based on the values of previously inputted arguments, using the `previousArgs()` method in `SuggestionInfo`. This `previousArgs()` method returns a **list of previous arguments** which are parsed exactly like any regular CommandAPI command argument.
+The `strings(Function<SuggestionInfo, String[]>)` method also has the capability to suggest arguments based on the values of previously inputted arguments, using the `previousArgs()` method in `SuggestionInfo`. This `previousArgs()` method returns a **list of previous arguments** which are parsed exactly like any regular CommandAPI command argument.
 
 :::danger
 
diff --git a/docs/en/create-commands/arguments/suggestions/suggestions-info.md b/docs/en/create-commands/arguments/suggestions/suggestions-info.md
@@ -30,7 +30,7 @@ CommandSender sender();
 CommandArguments previousArgs();
 ```
 
-`previousArgs()` represents the previously declared arguments, which are parsed and interpreted as if they were being used to execute the command. See [this example on the string argument suggestions page](./string-suggestions#suggestions-depending-on-previous-arguments) for an idea of how to use this field.
+`previousArgs()` represents the previously declared arguments, which are parsed and interpreted as if they were being used to execute the command. See [this example on the string argument suggestions page](./string-suggestions#suggestions-depending-on-previous-arguments) for an idea of how to utilize this field.
 
 ```java
 String currentInput();
diff --git a/docs/en/create-commands/arguments/suggestions/tooltips.md b/docs/en/create-commands/arguments/suggestions/tooltips.md
@@ -151,7 +151,7 @@ First, we'll declare our arguments. Here, we use a `LocationArgument` and use th
 <<< @/../reference-code/src/main/kotlin/createcommands/arguments/suggestions/Tooltips.kt#createArgumentsWithTooltipsAndSafeSuggestions
 :::
 
-In the argument declaration, we've cast the command sender to a player. To ensure that the command sender is definitely a player, we'll use the `executesPlayer` command execution method in our command declaration:
+In the arguments declaration, we've casted the command sender to a player. To ensure that the command sender is definitely a player, we'll use the `executesPlayer` command execution method in our command declaration:
 
 :::tabs
 ===Java
diff --git a/docs/en/create-commands/arguments/types/primitive-arguments.md b/docs/en/create-commands/arguments/types/primitive-arguments.md
@@ -7,7 +7,7 @@ authors:
 
 # Primitive arguments
 
-Primitive arguments are arguments that represent Java primitive types such as `int`, `float`, `double`, `boolean` and `long`. These arguments are defined in their respective classes:
+Primitive arguments are arguments that represent Java primitive types, such as `int`, `float`, `double`, `boolean` and `long`. These arguments are defined in their respective classes:
 
 | Primitive type | CommandAPI class  |
 |----------------|-------------------|
diff --git a/docs/en/create-commands/executors/native-sender.md b/docs/en/create-commands/executors/native-sender.md
@@ -8,7 +8,7 @@ authors:
 
 # Native command senders
 
-In a similar way that the `ProxiedCommandSender` is used to store information about two command senders: a caller (the one that wrote the command) and a callee (the one that ends up executing the command), the CommandAPI also has a special `NativeProxyCommandSender` class which is a more powerful representation of the `ProxiedCommandSender` class. In addition to inheriting all the methods from `ProxiedCommandSender`, this class also has the following two methods:
+In a similar way that the `ProxiedCommandSender` is used to store information about two command senders: a caller (the one that wrote the command) and a callee (the one that ends up executing the command), the CommandAPI also has a special `NativeProxyCommandSender` class which is a more powerful representation of the `ProxiedCommandSender` class. In addition to inheriting all of the methods from `ProxiedCommandSender`, this class also has the following two methods:
 
 ```java
 public World getWorld();
diff --git a/docs/en/create-commands/executors/normal-executors.md b/docs/en/create-commands/executors/normal-executors.md
@@ -102,7 +102,7 @@ This saves having to use `instanceof` multiple times to check the type of the `C
 
 ::::
 
-The different command sender priority is the following (from the highest priority to the lowest priority):
+The different command sender priority is the following (from highest priority to lowest priority):
 
 ```mermaid
 graph TD
diff --git a/docs/en/create-commands/executors/resulting-executors.md b/docs/en/create-commands/executors/resulting-executors.md
@@ -28,7 +28,7 @@ The concept of result values is better explained through examples:
 
 ::::tip Example – Random number result command
 
-Say we want a command that returns a random number as a result. This can then be used by vanilla Minecraft's `/execute store result ...` command, which can be used for other commandblock chains.
+Say we want a command that returns a random number as a result. This can then be used by vanilla Minecraft's `/execute store result ...` command, which can be used for other command block chains.
 
 :::tabs
 ===Java
diff --git a/docs/en/create-commands/registration.md b/docs/en/create-commands/registration.md
@@ -26,13 +26,13 @@ I think the easiest way to explain it is with an example:
 
 - In this example, we add an alias, "broadcast", to the command. This allows the sender to use either `/broadcastmsg <message>` or `/broadcast <message>`.
 
-- By using `withPermission`, we require the sender to be an OP to run the command.
+- By using `withPermission`, we require the sender to be an OP in order to run the command.
 
 - We control what the command does using `executes` (this is described in more detail in [the section on command executors](./executors/command-executors)).
 
 - Finally, we register the command to the CommandAPI using `register`.
 
-That's it! This simple snippet of code fully registers the command to the server. You don't need to supply a plugin instance, you don't have to create a custom class, and you don't have to mess with the `plugin.yml` file.
+That's it! This simple snippet of code fully registers the command to the server. You don't need to supply a plugin instance, you don't have to create a custom class and you don't have to mess with the `plugin.yml` file.
 
 Throughout this documentation, we will use the various different methods for command registration to give you an idea of when and where certain methods are more suitable than others.
 
@@ -62,7 +62,7 @@ CommandAPICommand withPermission(CommandPermission)
 CommandAPICommand withPermission(String)
 ```
 
-The `withPermission` method is used to assign a permission required to execute the command. (See [the section on permissions](./permissions) for more info).
+The `withPermission` method is used to assign a permission that is required to execute the command. (See [the section on permissions](./permissions) for more info).
 
 ```java
 CommandAPICommand withRequirements(sender -> {})
diff --git a/docs/en/dev-setup/annotations.md b/docs/en/dev-setup/annotations.md
@@ -9,7 +9,7 @@ authors:
 
 # Using the annotation system
 
-The annotation system is a separate part of the CommandAPI, and as a result, it needs to be included as an additional dependency to your project.
+The annotation system is a separate part of the CommandAPI, and as a result it needs to be included as an additional dependency to your project.
 
 The annotation system effectively needs to be added twice: Once for compilation and again to invoke the annotation processor itself.
 
diff --git a/docs/en/dev-setup/shading.md b/docs/en/dev-setup/shading.md
@@ -63,7 +63,7 @@ public class CommandAPIBukkitConfig extends CommandAPIConfig {
 }
 ```
 
-To create a `CommandAPIBukkitConfig` object, you must give it a reference to your `JavaPlugin` instance. The CommandAPI always uses this to register events, so it is required when loading the CommandAPI on Bukkit. There are also Bukkit-specific features, such as the `hook-paper-reload` configuration option, which may be configured using a `CommandAPIBukkitConfig` instance.
+In order to create a `CommandAPIBukkitConfig` object, you must give it a reference to your `JavaPlugin` instance. The CommandAPI always uses this to registers events, so it is required when loading the CommandAPI on Bukkit. There are also Bukkit-specific features, such as the `hook-paper-reload` configuration option, which may be configured using a `CommandAPIBukkitConfig` instance.
 
 For example, to load the CommandAPI on Bukkit with all logging disabled, you can use the following:
 
diff --git a/docs/en/user-setup/command-conversion/conversion.md b/docs/en/user-setup/command-conversion/conversion.md
@@ -13,7 +13,7 @@ import ConfigValidator from '../../../.vitepress/theme/components/ConfigValidato
 
 # Command Conversion for server admins
 
-The CommandAPI can convert plugin commands into "Vanilla compatible" commands automatically on startup. This allows you to use `/execute` and Minecraft functions/tags for plugins that don’t use the CommandAPI. For example, if you want to use the `/hat` command from the plugin `Essentials` in an `/execute` command or from a command block, you can use the CommandAPI's command conversion setting to do so.
+The CommandAPI has the ability to convert plugin commands into "Vanilla compatible" commands automatically on startup. This allows you to use `/execute` and Minecraft functions/tags for plugins that don’t use the CommandAPI. For example, if you want to use the `/hat` command from the plugin `Essentials` in an `/execute` command or from a command block, you can use the CommandAPI's command conversion setting to do so.
 
 The CommandAPI has 3 different conversion methods, each one more specific and powerful than the others. These are the following:
 
@@ -48,7 +48,7 @@ If you're uncertain if your configuration is valid (or you're getting weird erro
 
 ### Converting all plugin commands
 
-To convert all the commands that a plugin has, add the name of the plugin, followed by a `~` character to the list of plugins to convert in the `config.yml` file.
+To convert all of the commands that a plugin has, add the name of the plugin, followed by a `~` character to the list of plugins to convert in the `config.yml` file.
 
 ::: tip Example – Converting all commands from EssentialsX
 
diff --git a/docs/en/user-setup/command-conversion/entity-selectors.md b/docs/en/user-setup/command-conversion/entity-selectors.md
@@ -7,7 +7,7 @@ authors:
 
 # Entity selectors
 
-[Entity selectors](https://minecraft.wiki/w/Target_selectors) (also known as target selectors) allows you to select certain entities or players which fit a certain criteria when writing a command. Typically, these are of the form `@p`, `@r`, `@a`, `@e` or `@s`. By default, when converting a command without arguments, the CommandAPI will not handle these entity selectors. To get entity selectors to cooperate with plugins, they must be declared in the relevant `config.yml` section.
+[Entity selectors](https://minecraft.wiki/w/Target_selectors) (also known as target selectors) allows you to select certain entities or players which fit a certain criteria when writing a command. Typically, these are of the form `@p`, `@r`, `@a`, `@e` or `@s`. By default, when converting a command without arguments, the CommandAPI will not handle these entity selectors. In order to get entity selectors to cooperate with plugins, they must be declared in the relevant `config.yml` section.
 
 ::: tip Example - Converting EssentialsX's /ext command
 
@@ -18,7 +18,7 @@ EssentialsX includes a command `/ext` which lets you extinguish a player that is
 /ext <player>
 ```
 
-To convert this command, we could use the following `config.yml` file:
+In order to convert this command, we could use the following `config.yml` file:
 
 ```yaml
 verbose-outputs: false
@@ -42,7 +42,7 @@ However, the above `config.yml` **will not** support the following commands:
 /ext @p
 ```
 
-To handle this, we have to use the conversion with arguments (as described in the [previous section](./single-command-with-args)). For this `ext` command, we want to only use this command on _one or more players_, therefore, we want to use the `api:players` argument which is compatible with one or more players:
+In order to handle this, we have to use the conversion with arguments (as described in the [previous section](./single-command-with-args)). For this `ext` command, we want to only use this command on _one or more players_, therefore we want to use the `api:players` argument which is compatible with one or more players:
 
 ```yaml
 verbose-outputs: false
diff --git a/docs/en/user-setup/command-conversion/single-command-with-args.md b/docs/en/user-setup/command-conversion/single-command-with-args.md
@@ -52,7 +52,7 @@ Using this, we can display options, such as "fly" and "walk", as well as optiona
 
 ![A command "/execute run speed" with argument suggestions for entity selectors, as well as "fly" and "walk"](/images/speedoptions.png)
 
-Additionally, we can apply limits to the numbers that can be provided. For example, here we limit the number to a value between 0 and 10. If a value is outside of that range, and error is shown to the user:
+Additionally, we can apply limits to the numbers that can be provided. For example, here we limit the number to a value between 0 to 10. If a value is outside of that range, and error is shown to the user:
 
 ![A command "/execute run speed walk 15" with an error displaying `"Long must not be more than 10, found 15 at position 24: ...peed walk <--[HERE]`](/images/speedlimit.png)
 
@@ -99,7 +99,7 @@ The name in the argument can be whatever you want, but it is recommended to keep
 | `brigadier:string`    | A single word                                                                               |
 | `minecraft:block_pos` | A location of x, y and z coordinates (whole numbers)                                        |
 
-In the example above, we used the "range type" in the form `[0..10]`. This is a special argument type that will conform to `brigader:long` or `brigader:double` and apply a limit to the values that can be entered.
+In the example above, we used the a "range type" in the form `[0..10]`. This is a special argument type that will conform to `brigader:long` or `brigader:double` and apply a limit to the values that can be entered.
 
 ::: tip Example – Declaring "range type" arguments
 
diff --git a/docs/en/user-setup/command-conversion/single-command.md b/docs/en/user-setup/command-conversion/single-command.md
@@ -19,7 +19,7 @@ To convert a single command, you need to first populate the `config.yml` with th
 
 ::::tip Example – Converting plugin commands
 
-Say we're using [EssentialsX](https://www.spigotmc.org/resources/essentialsx.9089/) on our server, and we want to be able to use `/afk` and `/hat` in command blocks. This would allow us to use (for example) the following commands in command blocks:
+Say we're using [EssentialsX](https://www.spigotmc.org/resources/essentialsx.9089/) on our server and we want to be able to use `/afk` and `/hat` in command blocks. This would allow us to use (for example) the following commands in command blocks:
 
 ```mccmd
 /execute as @p run afk
@@ -71,15 +71,15 @@ commands:
 
 ## Arbitrary command conversion
 
-Some commands that are registered by plugins aren’t present in the plugin's `plugin.yml` file. Due to this, the CommandAPI can’t link a command to its respective plugin for command conversion. To deal with this, the CommandAPI can link arbitrary commands via the `other-commands-to-convert` option in the CommandAPI's `config.yml` file.
+Some commands which are registered by plugins aren’t present in the plugin's `plugin.yml` file. Due to this, the CommandAPI can’t link a command to its respective plugin for command conversion. In order to deal with this, the CommandAPI can link arbitrary commands via the `other-commands-to-convert` option in the CommandAPI's `config.yml` file.
 
 This can be used for any of the following (and more):
 
 - Commands created using [Skript](https://github.com/SkriptLang/Skript)
 - Commands created using [MyCommand](https://dev.bukkit.org/projects/mycommand)
 - Commands which are not registered in a `plugin.yml`, such as [WorldEdit](https://dev.bukkit.org/projects/worldedit) commands
 
-To add commands to be converted, add them under the `other-command-to-convert` section in the CommandAPI's `config.yml`.
+To add commands to be converted, simply add them under the `other-command-to-convert` section in the CommandAPI's `config.yml`.
 
 ::: tip Example – Converting arbitrary commands
 
