Fix Done! spacing site-wide, and EN-only content errors (Docker/Linux mixup, missing spaces, ProloNAS pun explanation)

content/en/3.serveex/2.core/1.installation.md

@@ -8,7 +8,7 @@ description: Step-by-step guide to install Debian 13 on a home server and set up
 
 [Debian 13 "Trixie"](https://www.debian.org/) is the base this whole guide sits on. It's a plain, boring, stable Linux, and for a homelab that's exactly the point: package versions stay frozen for the life of the release, security patches keep coming for about five years counting LTS, so the machine keeps running for years instead of needing a rebuild every few months.
 
-The other reason is that it stays out of your way. Appliance systems like Unraid, TrueNAS or Synology's DSM put their own layer on top of Docker, and the day you need something their interface doesn't expose, you're stuck working around it. Debian is just a server: you install what you want, where you want, and nothing is hidden behind someone else's UI. It also happens to be what most self-hosted projects target first, so their docs hand you `apt` commands that work as-is, Docker publishes an official Debian repository, and any error message you paste into a search engine already has years of answers behind it. A minimal install is light enough to leave nearly all the RAM and CPU of a small N100 box to your containers.
+The other reason is that it stays out of your way. Appliance systems like Unraid, TrueNAS or Synology's DSM put their own layer on top of Linux, and the day you need something their interface doesn't expose, you're stuck working around it. Debian is just a server: you install what you want, where you want, and nothing is hidden behind someone else's UI. It also happens to be what most self-hosted projects target first, so their docs hand you `apt` commands that work as-is, Docker publishes an official Debian repository, and any error message you paste into a search engine already has years of answers behind it. A minimal install is light enough to leave nearly all the RAM and CPU of a small N100 box to your containers.
 
 ![picture](/img/serveex/server.svg)
 
@@ -55,7 +55,7 @@ _Screenshot from [this bootable USB guide on DEV Community](https://dev.to/devop
 
 Writing takes a few minutes.
 
-#### Done !
+#### Done!
 ::
 
 ### Install Debian
@@ -117,7 +117,7 @@ Install it on the disk you just partitioned (`/dev/sda`, `/dev/nvme0n1`...), not
 
 ![Debian installer asking which device to install the GRUB boot loader to](/img/serveex/install/debian-install-grub.png)
 
-#### Done !
+#### Done!
 ::
 
 ::note
@@ -209,7 +209,7 @@ Keep your current SSH session open while you test. Open a **second** terminal an
 The door is now closed for every other machine too, including the next one you'll want to connect from. To let a new one in, set `PasswordAuthentication yes` back in `hardening.conf`, restart SSH, run the two key steps above from that machine, then set it to `no` again and restart SSH one last time.
 ::
 
-#### Done !
+#### Done!
 ::
 
 ### Wake the server up remotely
@@ -278,7 +278,7 @@ wakeonlan aa:bb:cc:dd:ee:ff
 
 Windows has no built-in sender, so the simplest route there is a phone app: any of the free *Wake on LAN* apps takes the MAC address and works the same way. The server should start within a couple of seconds.
 
-#### Done !
+#### Done!
 ::
 
 ::note
@@ -322,7 +322,7 @@ sudo reboot
 
 A kernel or libc update only takes effect after a restart. Everything else applies immediately, so this is only needed when the upgrade touched one of those, and it's worth planning for a moment when nothing depends on the machine.
 
-#### Done !
+#### Done!
 ::
 
 ::tip

content/en/3.serveex/2.core/2.docker.md

@@ -37,7 +37,7 @@ sudo apt-get update
 sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
 ```
 
-### Done !
+### Done!
 ::
 
 **More options:** [Install Docker for Debian 13](https://docs.docker.com/engine/install/debian/)
@@ -153,7 +153,7 @@ Then go to `http://yourserverip:3555` in your browser to access the login page.
 
 More info on [Dockge and how to use it](https://github.com/louislam/dockge)
 
-#### Done !
+#### Done!
 ::
 
 And there you go! Docker and a tool to easily manage your containers are ready!
@@ -264,7 +264,7 @@ services:
 
 Then restart the modified stacks.
 
-#### Done !
+#### Done!
 ::
 
 And that's it! You now have a solid base to start deploying the services you want!

content/en/3.serveex/2.core/3.wireguard.md

@@ -150,7 +150,7 @@ Then go to *Administrator → Admin Panel → Config*:
 - Change `Allowed IPs` from the default `0.0.0.0/0` (full tunnel) to `10.8.0.0/24` for **split tunneling**.
 - Optionally remove the IPv6 entry from `Allowed IPs` if you don't want client IPv6 traffic routed through the tunnel. This only affects what clients tunnel, not the container's own IPv6 setup above.
 
-### Done !
+### Done!
 ::
 
 ### Retrieve Configuration Files
@@ -176,7 +176,7 @@ Set it to `25` if it’s a permanently connected client.
 
 Save, download, and rename the file to `wg0.conf` (or `wg1.conf`, etc.)
 
-#### Done !
+#### Done!
 ::
 
 ## Client Server Setup
@@ -255,7 +255,7 @@ cd /srv/docker/wireguard
 sudo docker compose up -d
 ```
 
-### Done !
+### Done!
 ::
 
 ::note

content/en/3.serveex/2.core/4.swag.md

@@ -175,7 +175,7 @@ include /config/nginx/dbip.conf;
 
 Restart the stack in Dockge. This time, the SSL certificate should be successfully generated! Check the logs to confirm the server is ready.
 
-### Done !
+### Done!
 ::
 
 ## Dashboard
@@ -250,7 +250,7 @@ geo $lan-ip {
 
 Save and close the file, then restart the stack.
 
-### Done !
+### Done!
 ::
 
 In the domain config files (see next section), you can enable or disable the whitelist or blacklist ([see documentation here](https://www.forum-nas.fr/threads/tuto-installer-swag-en-docker-reverse-proxy.15057/)). In our case, the whitelist allows only French requests. The blacklist blocks only the listed countries. We'll use the blacklist, like so:
@@ -383,7 +383,7 @@ Redeploy the SWAG stack.
 
 Wait a moment, then visit `https://dockge.mydomain.com` in your browser. You should be redirected to Dockge. You can also check the service status from the dashboard (`http://yourserverip:81` on your local network).
 
-### Done !
+### Done!
 ::
 
 ## Exposing Another Service with SWAG