Updated hyperlinks in own documentation.

README.md

@@ -93,16 +93,18 @@ The above example shows a `ACCESS_DENIED` error.
 
 The Bash `install.sh`-scripts are there for copying the needed files to the specificied location on the system, preferably from a webserver root into the ~(user)/Templates.
 
-The following endpoints are available by default. This is needed for the new machine to set itself up.
+The following endpoints are available by default after installing using `install.sh` (assuming success). This is needed for the new machine to set itself up.
 
 ```shell
+/assets/desktop.png 	        # This file will be used as the background for the installed device. Replacing must be done by exactly coping the name + filename extension.
+/aseets/gtk.css                 # This file applies some styling to make the UI look more modern and appealing.
 /assets/panel-profile.tar.bz2   # XFCE4 Panel profile.
 /credcon/credcon.sh             # Bash script for asking user credentials (for the RDP connection).
-/configs/minimal/preseed.cfg    # The Debian preseed file.
-/configs/default/preseed.cfg
-/configs/minimal/finish.sh      # The Bash script that applies all settings.
-/configs/default/finish.sh
-/rdp/<your-templates>           # Directory endpoint for premade '.rdp' files (for example /rdp/demo.rdp)
+/configs/minimal/preseed.cfg    # The Debian preseed file for the minimal configuration (~4GB).
+/configs/default/preseed.cfg    # The default Debian preseed file.
+/configs/minimal/finish.sh      # The Bash script that applies all settings with a modification for support on small drives.
+/configs/default/finish.sh      # The default bash script.
+/rdp/<your-templates>           # Directory endpoint for premade '.rdp' files (for example /rdp/demo.rdp). You NEED to populate this yourself.
 ```
 
 The above `/rdp` endpoint requires you to place premade `.rdp` files in the directory before running `setup.sh`.<br>

documentation/installation.md

@@ -4,7 +4,7 @@
     Just like a normal Debian installation boot off of the USB-medium. Then instead of entering the (graphical) install, go to `Advanced settings -> (graphical) Automated install.`<br>
     This will load basic modules from the installation media, and load them. These include but are not limited to network connectivity (to connect to the webserver presenting NTOS-files).<br>
 
-    > For an example see [preseed-screen](../assets/images/debian12-preseed-screen.png).<br>
+    > For an example see [preseed-screen](../assets/images/preseed.jpeg).<br>
 
 2.  Refering to the webserver endpoints below - enter the IP-address or hostname of the webserver (with the port) followed by `/configs/<desired-config>/preseed.cfg`. By default the minimal and default configurations are available.<br>
     This makes the [Debian-installer](https://www.debian.org/devel/debian-installer/) use the preseed configuration for its installation.<br>

documentation/ntos-management.md

@@ -6,8 +6,8 @@ Below I will describe a couple RMM/Management solutions I am familiar with.<br>
 ### MeshCentral:
 
 MeshCentral is the go-to application to use in this case - free, open-source and overal it has a great community ([More info](https://github.com/Ylianst/MeshCentral)).<br>
-The way to deploy a MeshCentral-agent to a NTOS-client is to configure your desired config, such as minimal (inside [the NTOS directories](../../ntos/configs/)).<br>
-For example, paste the lines below on the lines referenced in the main [README.md](../../README.md):
+The way to deploy a MeshCentral-agent to a NTOS-client is to configure your desired config, such as minimal (inside [the NTOS directories](../ntos)).<br>
+For example, paste the lines below on the lines referenced in the main [README.md](../README.md):
 
 > Note: The below instruction is just copied from MeshCentral when clicking '*Add Agent*' -> '*Linux / BSD*' (I just split it up into multiple lines).
 
@@ -21,13 +21,13 @@ For example, paste the lines below on the lines referenced in the main [README.m
 
 > Don't forget the remove the remaining files after this installation. I normally do this through `rm *mesh*`, but make sure that this does not delete other things as well.
 
-Once you have the above lines inside the `finish.sh` script, you can actually apply it - using `finish.sh` (as in [this image](../../assets/images/debian12-finishsh-progress.png)).<br>
+Once you have the above lines inside the `finish.sh` script, you can actually apply it - using `finish.sh` (as in [this image](../assets/images/finish_sh.jpeg)).<br>
 This should then use the MeshCentral instructions and make it pop-up in your specified group.
 
 ## Desktop:
 
 As an example, you can 'shadow' or 'share screen' from MeshCentral.<br>
 
-![MeshCentral Desktop Example (2560x1440p)](../../assets/images/meshcentral-ntos-desktop.png)
+![MeshCentral Desktop Example (2560x1440p)](../assets/images/meshcentral-ntos-desktop.png)
 
 > Note: Screenshot might be out-of-date. But functionality is the same.