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

content/en/3.serveex/9.apps/1.adguard.md

@@ -99,7 +99,7 @@ Go to `http://yourserverip:3000` and follow the setup instructions.
 The setup wizard asks you to pick an admin interface port. Keep it at `3000`: the SWAG configuration further down assumes the admin interface stays on that port, and changing it here would make exposing AdGuard with SWAG fail with a 502 error.
 ::
 
-### Done !
+### Done!
 ::
 
 That’s it! Adguard is deployed.
@@ -236,7 +236,7 @@ server {
 }
 ```
 
-### Done !
+### Done!
 ::
 
 ## Protecting AdGuard with TinyAuth

content/en/3.serveex/9.apps/2.vaultwarden.md

@@ -100,7 +100,7 @@ Then deploy the container.
 
 Recently, Vaultwarden requires SSL to be accessed, which prevents access via a local IP. We'll expose it with SWAG, which provides an SSL certificate.
 
-### Done !
+### Done!
 ::
 
 ::caution
@@ -244,7 +244,7 @@ server {
 
 Press :kbd{value="Ctrl+O"}, then :kbd{value="Enter"} to save, and :kbd{value="Ctrl+X"} to exit.
 
-### Done !
+### Done!
 ::
 
 And there you go! Vaultwarden is now exposed! Visit `https://vault.yourdomain.com/admin` to access the admin panel and paste the password you specified when generatique the `ADMIN_TOKEN`. For more information, see the [Bitwarden documentation](https://bitwarden.com/help/).
@@ -298,7 +298,7 @@ Press :kbd{value="Ctrl+O"}, then :kbd{value="Enter"} to save, and :kbd{value="Ct
 
 Redeploy Vaultwarden. Your next visit to `https://vault.yourdomain.com` will prompt for SSO login instead of (or alongside) the local master password.
 
-### Done !
+### Done!
 ::
 
 ::note{to="https://github.com/dani-garcia/vaultwarden/wiki/Enabling-SSO-support-using-OpenId-Connect"}
@@ -329,7 +329,7 @@ SSO_CLIENT_SECRET=
 SSO_SCOPES=email profile offline_access
 ```
 
-#### Done !
+#### Done!
 ::
 
 :::