Better sh hl

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

@@ -41,7 +41,7 @@ Below is an example exposing Dockge. We will install SWAG along with the dbip mo
 
 File structure to be modified:
 
-```console
+```sh
 root
 └── docker
     └── swag
@@ -133,7 +133,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.
 ::
 
-```shell
+```sh
 sudo vi /docker/swag/config/dns-conf/ovh.ini
 ```
 
@@ -163,7 +163,7 @@ Save and exit the file.
 
 Now configure swag to access DBIP, the geolocation-based access control module. Open the `nginx.conf` file:
 
-```shell
+```sh
 sudo vi /docker/swag/config/nginx/nginx.conf
 ```
 
@@ -193,7 +193,7 @@ This configuration can be enabled or disabled per service (see the Dockge exampl
 
 Open `dbip.conf`:
 
-```shell
+```sh
 sudo vi /docker/swag/config/nginx/dbip.conf
 ```
 
@@ -278,7 +278,7 @@ Now it's time to expose Dockge on the internet so you can access and manage your
 
 Open the `dockge.subdomain.conf` file:
 
-```shell
+```sh
 sudo vi /docker/swag/config/nginx/proxy-confs/dockge.subdomain.conf
 ```
 
@@ -363,7 +363,7 @@ Wait a moment, then visit `https://dockge.mydomain.com` in your browser — you
 ---
 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:
 
-```shell
+```sh
 cd /docker/swag/config/proxy-confs
 sudo cp servicename.subdomain.conf.sample servicename.subdomain.conf
 ```