Spellcheck issues

.wordlist.txt

@@ -1,5 +1,6 @@
 aarch
 ACP
+ACPI
 ActivityPub
 addictiveness
 addon
@@ -579,6 +580,7 @@ selectable
 Servarr
 serverless
 servlet
+severities
 SFTP
 SHA
 Shairport

docs/releases/v9_9.md

@@ -18,7 +18,7 @@ The **December 17th, 2024** release of **DietPi v9.9** comes with new images for
 
 ### Enhancements
 
-- [**Virtual Machines**](../hardware.md#native-pc-virtual-machines) :octicons-arrow-right-16: systemd-logind is now enabled by default on VMs, as it provides ACPI functionality, needed to properly shutdown or reboot the VM from the virtualiser software, usually expected by users.
+- [**Virtual Machines**](../hardware.md#native-pc-virtual-machines) :octicons-arrow-right-16: `systemd-logind` is now enabled by default on VMs, as it provides ACPI functionality, needed to properly shutdown or reboot the VM from the virtualiser software, usually expected by users.
 - [**DietPi-Tools**](../dietpi_tools.md) | [**DietPi-DDNS**](../dietpi_tools/software_installation.md#dietpi-ddns) :octicons-arrow-right-16: The `IPv6or4` option to update IPv6 only, if supported by server, network and provider, has been replaced with `IPv4and6`. A server being reachable via IPv6 only is rarely wanted, as many networks do not support it. Instead, usually one will want to have it reachable via both, IPv4 as well as IPv6, which is now possible when using DietPi-DDNS, and the new default. If, e.g. for security reason, IPv6 only is wanted, this option of course remains available, like before. Many thanks to @LOGIN-TB for doing this suggestion: <https://github.com/MichaIng/DietPi/issues/7278>
 - [**DietPi-Tools**](../dietpi_tools.md) | [**DietPi-DDNS**](../dietpi_tools/software_installation.md#dietpi-ddns) :octicons-arrow-right-16: The cron job does now log server response messages and connection errors separately with respective severities. Some DDNS providers do not return an HTTP error code, but an error text embedded into a regular HTTP 200 response. This, as well as success responses can now be seen via `journalctl -t dietpi-ddns`. Many thanks to @jtmoon79 for doing this suggestion: <https://github.com/MichaIng/DietPi/issues/5954>
 - [**DietPi-Tools**](../dietpi_tools.md) | [**DietPi-Services**](../dietpi_tools/system_configuration.md#dietpi-services) :octicons-arrow-right-16: `dietpi-services start` will not start disabled services anymore. This aligns with the behaviour of the `restart` command, which as well skips disabled services. The script is used within other DietPi scripts to (re)start services after maintenance operations, and it is unexpected when services, who were not running before, but explicitly disabled, are running afterwards. To manually start/stop individual services from the console, we recommend using `systemctl` directly, like on any other Linux distribution with `systemd`. Many thanks to @intiplink for reporting this unexpected behaviour while using dietpi-drive_manager: <https://github.com/MichaIng/DietPi/issues/7302>