Address some more code review

Co-authored-by: willkroboth <46540330+willkroboth@users.noreply.github.com>

Author: DerEchtePilz

docs/en/create-commands/registration.md

@@ -219,6 +219,8 @@ Places where you can register commands are listed below:
 |--------------------------------|-----------------------------------------------------------------|
 | `onLoad()`/`onEnable()` method | Register regular commands not available in datapacks by default |
 
+If you want your command to be accessible in Minecraft functions, make sure the [datapack reload](../user-setup/config#skip-initial-datapack-reload) process is set to `false`.
+
 </div>
 
-The CommandAPI does support registering commands outside of these methods while the server is running. Commands registered after the server is done loading _should_ work the same as commands registered in `onLoad()`/`onEnable()`.
+The CommandAPI does support registering commands anytime after the server is done loading. Commands registered while the server is running _should_ work the same as commands registered in `onLoad()`/`onEnable()`.

docs/en/dev-setup/shading.md

@@ -31,9 +31,7 @@ If you want to handle reloading, the CommandAPI has minimal support for it with
 
 ### Loading
 
-The `onLoad(CommandAPIConfig)` method initializes the CommandAPI's loading sequence. This must be called _before_ you start to access the CommandAPI and must be placed in your plugin's `onLoad()` method. The argument `CommandAPIConfig` is used to configure how the CommandAPI works. The `CommandAPIConfig` class has the following parameters which let you set how the CommandAPI works similar to the `config.yml`, which is described [here](../user-setup/config).
-
-The `CommandAPIConfig` class follows a typical builder pattern (without you having to run `.build()` at the end), which lets you easily construct configuration instances.
+The `onLoad(CommandAPIConfig)` method initializes the CommandAPI. This must be called _before_ you access any other CommandAPI features. The `CommandAPIConfig` argument is used to configure how the CommandAPI works, similar to the `config.yml`. The `CommandAPIConfig` class follows a builder pattern, with methods for each option in the `config.yml`, which are listed and described [here](../user-setup/config).
 
 <div class="paper">
 

update.sh

@@ -5,7 +5,7 @@ echo "New version:"
 read -r newVer
 
 # Update CommandAPI dependency versions
-sed -i "s/commandApiVersion=$oldVer/commandApiVersion$newVer/" reference-code/gradle.properties
+sed -i "s/commandApiVersion=$oldVer/commandApiVersion=$newVer/" reference-code/gradle.properties
 
 # Update CommandAPI version in documentation files (Maven)
 sed -i "s/<version>$oldVer<\/version>/<version>$newVer<\/version>/" docs/en/dev-setup/annotations.md