Remove stray blank lines and start every stack with ---

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

@@ -69,14 +69,12 @@ services:
     image: adguard/adguardhome
     restart: unless-stopped
     ports:
-
       - 53:53/udp
       - 8080:80/tcp
       - 4443:443/tcp
       - 853:853/tcp
       - 3000:3000/tcp
     volumes:
-
       - /docker/adguardhome/confdir:/opt/adguardhome/conf
       - /docker/adguardhome/workdir:/opt/adguardhome/work
       - /docker/swag/config/etc/letsencrypt:/swag-ssl:ro
@@ -86,11 +84,11 @@ services:
 ✨ __Tip:__ Add the watchtower label to each container to automate updates
 
 ```yaml [compose.yaml]
+---
 services:
   adguardhome:
     # ...
     labels:
-
       - com.centurylinklabs.watchtower.enable=true
 ```
 ::
@@ -117,6 +115,7 @@ Do not use Cloudflare tunnels to expose AdGuard, and make sure any proxying is d
 In Dockge, go to the SWAG stack and edit the compose file to add the AdGuard network:
 
 ```yaml [compose.yaml]
+---
 services:
   swag:
      container_name: # ...

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

@@ -41,16 +41,12 @@ services:
     image: vaultwarden/server:latest
     restart: unless-stopped
     env_file:
-
       - .env
     volumes:
-
       - ./data/:/data/
     ports:
-
       - 3050:80
     environment:
-
       - DOMAIN=${URL}
       - LOGIN_RATELIMIT_MAX_BURST=10
       - LOGIN_RATELIMIT_SECONDS=60
@@ -70,11 +66,11 @@ services:
 ✨ __Tip:__ Add the Watchtower label in each container to automate updates
 
 ```yaml [compose.yaml]
+---
 services:
   vaultwarden:
     #...
     labels:
-
       - com.centurylinklabs.watchtower.enable=true
 ```
 ::
@@ -118,6 +114,7 @@ The main benefit of Vaultwarden is being able to access it remotely from any dev
 In Dockge, go to the SWAG stack and edit the compose file to add the Vaultwarden network:
 
 ```yaml [compose.yaml]
+---
 services:
   swag:
      container_name: # ...