Everywhere: Remove unnecessary whitespace at the end of some lines.

3 files changed, 4 insertions, 4 deletions

diff --git a/Documentation/BuildInstructions.md b/Documentation/BuildInstructions.md
index 018b5b98f6..a5507aae08 100644
--- a/Documentation/BuildInstructions.md
+++ b/Documentation/BuildInstructions.md
@@ -105,12 +105,12 @@ brew install --cask osxfuse
 Toolchain/BuildFuseExt2.sh
 ```
 
-Notes: 
+Notes:
 - fuse-ext2 is not available as brew formula so it must be installed using `BuildFuseExt2.sh`
 - Xcode and `xcode-tools` must be installed (`git` is required by some scripts)
 - coreutils is needed to build gcc cross compiler
 - qemu is needed to run the compiled OS image. You can also build it using the `BuildQemu.sh` script
-- osxfuse, e2fsprogs, m4, autoconf, automake, libtool and `BuildFuseExt2.sh` are needed if you want to build the root filesystem disk image natively on macOS. This allows mounting an EXT2 fs and also installs commands like `mke2fs` that are not available on stock macOS. 
+- osxfuse, e2fsprogs, m4, autoconf, automake, libtool and `BuildFuseExt2.sh` are needed if you want to build the root filesystem disk image natively on macOS. This allows mounting an EXT2 fs and also installs commands like `mke2fs` that are not available on stock macOS.
 - Installing osxfuse for the first time requires enabling its system extension in System Preferences and then restarting your machine. The output from installing osxfuse with brew says this, but it's easy to miss.
 - bash is needed because the default version installed on macOS doesn't support globstar
 - If you install some commercial EXT2 macOS fs handler instead of osxfuse and fuse-ext2, you will need to `brew install e2fsprogs` to obtain `mke2fs` anyway.
diff --git a/Documentation/INSTALL.md b/Documentation/INSTALL.md
index 3d4307f377..f15544a335 100644
--- a/Documentation/INSTALL.md
+++ b/Documentation/INSTALL.md
@@ -7,7 +7,7 @@ Whilst it is possible to run Serenity on physical x86-compatible hardware, it is
 
 ## Hardware support and requirements
 
-Storage-wise Serenity requires a >= 2 GB parallel ATA or SATA IDE disk. Some older SATA chipsets already operate in IDE mode whilst some newer ones will depend upon adjusting a BIOS option to run your SATA controller in IDE (sometimes referred to as Legacy or PATA) mode. SATA AHCI, SCSI, SAS, eMMC and NVME are all presently unsupported. 
+Storage-wise Serenity requires a >= 2 GB parallel ATA or SATA IDE disk. Some older SATA chipsets already operate in IDE mode whilst some newer ones will depend upon adjusting a BIOS option to run your SATA controller in IDE (sometimes referred to as Legacy or PATA) mode. SATA AHCI, SCSI, SAS, eMMC and NVME are all presently unsupported.
 
 You must be willing to wipe your disk's contents to allow for writing the Serenity image so be sure to back up any important data on your disk first! Serenity uses the GRUB2 bootloader so it should be possible to multiboot it with any other OS that can be booted from GRUB2 post-installation.
 
diff --git a/Documentation/VirtualBox.md b/Documentation/VirtualBox.md
index 5ebe8876bc..adbf42c806 100644
--- a/Documentation/VirtualBox.md
+++ b/Documentation/VirtualBox.md
@@ -49,7 +49,7 @@ The way around this is to use a different file name for each VDI you generate. Y
 Yes, this is a mess. You can delete the old disk images without any issues. If you know a solution for this, *please* let us know.
 
 ## Configuring the virtual machine to boot Serenity
-Serenity will not be able to boot with the default configuration. There are a couple settings to adjust. Open **Settings** and: 
+Serenity will not be able to boot with the default configuration. There are a couple settings to adjust. Open **Settings** and:
 1. Go to **System**, open the **Processor** tab and tick **Enable PAE/NX**.
 2. Go to **Audio** and set **Audio Controller** to **SoundBlaster 16**.