Label terminal commands and directory trees in code blocks

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

@@ -39,7 +39,7 @@ This tutorial assumes you have a domain name pointing to your server, and that y
 
 File structure to be modified:
 
-```sh
+```text [Directory tree]
 root
 └── docker
     └── swag
@@ -138,7 +138,7 @@ In CLI, go to the dns-conf folder and edit the `ovh.ini` file:
 You can use [File Browser](/serveex/files/file-browser) to browse and edit files instead of using terminal commands.
 ::
 
-```sh
+```bash [Terminal]
 sudo nano /docker/swag/config/dns-conf/ovh.ini
 ```
 
@@ -168,7 +168,7 @@ Save with :kbd{value="Ctrl+O"}, then :kbd{value="Enter"}, and exit with :kbd{val
 
 Now configure swag to access DBIP, the geolocation-based access control module. Open the `nginx.conf` file:
 
-```sh
+```bash [Terminal]
 sudo nano /docker/swag/config/nginx/nginx.conf
 ```
 
@@ -195,7 +195,7 @@ This configuration can be enabled or disabled per service (see the Dockge exampl
 
 Open `dbip.conf`:
 
-```sh
+```bash [Terminal]
 sudo nano /docker/swag/config/nginx/dbip.conf
 ```
 
@@ -278,7 +278,7 @@ Dockge does not support multi-factor authentication. Exposing it online could co
 
 Open the `dockge.subdomain.conf` file:
 
-```sh
+```bash [Terminal]
 sudo nano /docker/swag/config/nginx/proxy-confs/dockge.subdomain.conf
 ```
 
@@ -361,7 +361,7 @@ Wait a moment, then visit `https://dockge.mydomain.com` in your browser — you
 ## Exposing Another Service with SWAG
 SWAG includes templates for most known services, named `servicename.subdomain.conf.sample`. Just create the subdomain in your registrar's DNS zone (like OVH), point it to your main domain via a CNAME, then copy and rename the sample file:
 
-```sh
+```bash [Terminal]
 cd /docker/swag/config/proxy-confs
 sudo cp servicename.subdomain.conf.sample servicename.subdomain.conf
 ```