diff --git a/.docs/content/1.installation/1.linux/0.prerequisites.md b/.docs/content/1.installation/1.linux/0.prerequisites.md
index 35eeae1d9..be569fd34 100644
--- a/.docs/content/1.installation/1.linux/0.prerequisites.md
+++ b/.docs/content/1.installation/1.linux/0.prerequisites.md
@@ -8,7 +8,7 @@ In order to install ArmoniK locally or on-premise, you must have a few of things
 
 You can easily install all of them using the [ArmoniK prerequisites installer](https://github.com/aneoconsulting/ArmoniK/blob/main/infrastructure/utils/scripts/installation/prerequisites-installer.sh) from the root repository.
 
-```bash
+```bash [shell]
 ./infrastructure/utils/scripts/installation/prerequisites-installer.sh
 ```
 
diff --git a/.docs/content/1.installation/1.linux/1.installation.md b/.docs/content/1.installation/1.linux/1.installation.md
index d1ad7e182..b29bbfea7 100644
--- a/.docs/content/1.installation/1.linux/1.installation.md
+++ b/.docs/content/1.installation/1.linux/1.installation.md
@@ -12,13 +12,13 @@ Before running the script, you must set environment variables.
 
 From the root of the repository:
 
-```bash
+```bash [shell]
 cd infrastructure/quick-deploy/localhost
 ```
 
 Then, you can set environment variables in the file `envvars.sh`:
 
-```bash
+```bash [shell]
 source envvars.sh
 ```
 
@@ -30,7 +30,7 @@ Please, read the file `envvars.sh` before running it.
 
 Create data directory:
 
-```bash
+```bash [shell]
 mkdir -p "${ARMONIK_SHARED_HOST_PATH}"
 ```
 
@@ -44,7 +44,7 @@ You can find why your pod doesn't start using `kubectl describe pod <pod_name> -
 
 Finally, you can run the script to deploy ArmoniK on your local machine:
 
-```bash
+```bash [shell]
 make deploy-all
 ```
 
@@ -66,23 +66,23 @@ armonik = {
 
 You can also deploy each resource independently:
 
-```bash
+```bash [shell]
 make deploy-keda
 ```
 
-```bash
+```bash [shell]
 make deploy-metrics-server
 ```
 
-```bash
+```bash [shell]
 make deploy-storage
 ```
 
-```bash
+```bash [shell]
 make deploy-monitoring
 ```
 
-```bash
+```bash [shell]
 make deploy-armonik
 ```
 
@@ -94,7 +94,7 @@ The order matters because top level resources depend on the bottom level resourc
 
 To destroy all the infrastructure, you can run the following command:
 
-```bash
+```bash [shell]
 make destroy-all
 ```
 
@@ -104,23 +104,23 @@ To reinstall, you must restart from [setup environment variables](#setup-environ
 
 You can also destroy each resource independently:
 
-```bash
+```bash [shell]
 make destroy-armonik
 ```
 
-```bash
+```bash [shell]
 make destroy-monitoring
 ```
 
-```bash
+```bash [shell]
 make destroy-storage
 ```
 
-```bash
+```bash [shell]
 make destroy-metrics-server
 ```
 
-```bash
+```bash [shell]
 make destroy-keda
 ```
 
@@ -132,7 +132,7 @@ The order matters. You must destroy the resources in the reverse order of the de
 
 To clean all the generated files from the deployment, you can run the following command:
 
-```bash
+```bash [shell]
 make clean-all
 ```
 
@@ -142,23 +142,23 @@ To reinstall, you must restart from [setup environment variables](#setup-environ
 
 You can also clean each resource independently:
 
-```bash
+```bash [shell]
 make clean-armonik
 ```
 
-```bash
+```bash [shell]
 make clean-monitoring
 ```
 
-```bash
+```bash [shell]
 make clean-storage
 ```
 
-```bash
+```bash [shell]
 make clean-metrics-server
 ```
 
-```bash
+```bash [shell]
 make clean-keda
 ```
 
diff --git a/.docs/content/1.installation/1.linux/2.verify-installation.md b/.docs/content/1.installation/1.linux/2.verify-installation.md
index 6b5724080..6442bcb75 100644
--- a/.docs/content/1.installation/1.linux/2.verify-installation.md
+++ b/.docs/content/1.installation/1.linux/2.verify-installation.md
@@ -14,7 +14,7 @@ You can also retrieve the `seq.web_url` from the Terraform outputs `monitoring/g
 
 Example:
 
-```bash
+```bash [shell]
 http://<ip_address>:8080
 ```
 
@@ -34,7 +34,7 @@ You can also retrieve the `armonik.admin_gui_url` from the Terraform outputs `ar
 
 Example:
 
-```bash
+```bash [shell]
 http://<ip_address>:5000
 ```
 
@@ -60,7 +60,7 @@ You can find more information about samples in their [dedicated documentation](h
 
 Before executing the samples, you must clone [ArmoniK.Samples](https://github.com/aneoconsulting/ArmoniK.Samples) into a folder name `Source` from the root repository of ArmoniK:
 
-```bash
+```bash [shell]
 git clone https://github.com/aneoconsulting/ArmoniK.Samples.git ./Source/ArmoniK.Samples/
 ```
 
@@ -69,7 +69,7 @@ git clone https://github.com/aneoconsulting/ArmoniK.Samples.git ./Source/ArmoniK
 <!-- TODO: Verify how to execute samples -->
 * Execute [tools/tests/symphony_like.sh](https://github.com/aneoconsulting/ArmoniK.Samples/blob/main/tools/tests/symphony_like.sh) from the **root** repository:
 
-  ```bash
+  ```bash [shell]
   tools/tests/symphony_like.sh
   ```
 
diff --git a/.docs/content/1.installation/1.linux/3.deploy-script.md b/.docs/content/1.installation/1.linux/3.deploy-script.md
index df7d9033a..8e1b7b0f3 100644
--- a/.docs/content/1.installation/1.linux/3.deploy-script.md
+++ b/.docs/content/1.installation/1.linux/3.deploy-script.md
@@ -9,37 +9,37 @@ You can find [prerequisites here](./0.prerequisites.md) and [installation instru
 
 From the **root** of the repository, position yourself in directory `infrastructure/utils/scripts/`:
 
-```bash
+```bash [shell]
 cd infrastructure/utils/scripts
 ```
 
 - To see the usage command:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh -h
   ```
 
 - To deploy for the first time all infrastructure:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh -m deploy-all
   ```
 
 - To redeploy all infrastructure:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh -m redeploy-all
   ```
 
 - To destroy all infrastructure:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh -m destroy-all
   ```
 
 - To clean and delete all generated files from all deployment:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh --clean all
   ```
 
@@ -47,31 +47,31 @@ If You want to deploy each resource independently:
 
 - To deploy Keda:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh -m deploy-keda
   ```
 
 - To deploy Metrics server:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh -m deploy-metrics-server
   ```
 
 - To deploy storage:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh -m deploy-storage
   ```
 
 - To deploy monitoring:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh -m deploy-monitoring
   ```
 
 - To deploy ArmoniK:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh -m deploy-armonik
   ```
 
@@ -79,31 +79,31 @@ If You want to redeploy each resource independently:
 
 - To redeploy Keda:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh -m redeploy-keda
   ```
 
 - To redeploy Metrics server:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh -m redeploy-metrics-server
   ```
 
 - To redeploy storage:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh -m redeploy-storage
   ```
 
 - To redeploy monitoring:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh -m redeploy-monitoring
   ```
 
 - To redeploy ArmoniK:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh -m redeploy-armonik
   ```
 
@@ -111,31 +111,31 @@ If You want to destroy each resource independently:
 
 - To destroy Keda:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh -m destroy-keda
   ```
 
 - To destroy Metrics server:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh -m destroy-metrics-server
   ```
 
 - To destroy storage:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh -m destroy-storage
   ```
 
 - To destroy monitoring:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh -m destroy-monitoring
   ```
 
 - To destroy ArmoniK:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh -m destroy-armonik
   ```
 
@@ -143,50 +143,50 @@ If You want to clean and delete generated files from each deployment independent
 
 - To clean Keda:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh --clean keda
   ```
 
 - To clean Metrics server:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh --clean metrics-server
   ```
 
 - To clean storage:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh --clean storage
   ```
 
 - To clean monitoring:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh --clean monitoring
   ```
 
 - To clean ArmoniK:
 
-  ```bash
+  ```bash [shell]
   ./deploy-dev-test-infra.sh --clean armonik
   ```
 
 If You want to deploy ArmoniK components on specific Kubernetes namespace, You execute the following command:
 
-```bash
+```bash [shell]
 ./deploy-dev-test-infra.sh -m deploy-all --namespace <NAMESPACE>
 ```
 
 If the `host_path` for shared storage for ArmoniK workers is not `${HOME}/data`, You can deploy the infrastructure as
 follows:
 
-```bash
+```bash [shell]
 ./deploy-dev-test-infra.sh -m deploy-all --host-path <HOST_PATH>
 ```
 
 If You have a NFS filesystem as shared storage for ArmoniK workers, You deploy the infrastructure as follows:
 
-```bash
+```bash [shell]
 ./deploy-dev-test-infra.sh \
   -m deploy-all \
   --host-path <HOST_PATH> \
@@ -196,7 +196,7 @@ If You have a NFS filesystem as shared storage for ArmoniK workers, You deploy t
 
 If You want to change container image and/or tag of control plane, polling agent, worker or metrics exporter:
 
-```bash
+```bash [shell]
 ./deploy-dev-test-infra.sh \
   -m deploy-all \
   --control-plane-image <CONTROL_PLANE_IMAGE> \
@@ -212,7 +212,7 @@ metrics exporter).
 
 If You change the max, min or idle replicas in the HPA of the compute plane:
 
-```bash
+```bash [shell]
 ./deploy-dev-test-infra.sh \
   -m deploy-all \
   --hpa-min-compute-plane-replicas <HPA_MIN_COMPUTE_PLANE_REPLICAS> \
@@ -227,7 +227,7 @@ where `<COMPUTE_PLANE_HPA_TARGET_VALUE>` is the target value for the number of m
 
 If You change the max, min or idle replicas in the HPA of the control plane:
 
-```bash
+```bash [shell]
 ./deploy-dev-test-infra.sh \
   -m deploy-all \
   --hpa-min-control-plane-replicas <HPA_MIN_CONTOL_PLANE_REPLICAS> \
@@ -242,24 +242,24 @@ where `<CONTROL_PLANE_HPA_TARGET_VALUE>` is the target value in percentage for t
 
 If You want to change logging level for ArmoniK components:
 
-```bash
+```bash [shell]
 ./deploy-dev-test-infra.sh -m deploy-all --logging-level <LOGGING_LEVEL_FOR_ARMONIK>
 ```
 
 If You want to activate the TLS:
 
-```bash
+```bash [shell]
 ./deploy-dev-test-infra.sh -m deploy-all --with-tls
 ```
 
 If You want to activate the mTLS:
 
-```bash
+```bash [shell]
 ./deploy-dev-test-infra.sh -m deploy-all --with-mtls
 ```
 
 If You want to deactivate the ingress with NGINX:
 
-```bash
+```bash [shell]
 ./deploy-dev-test-infra.sh -m deploy-all --without-nginx
 ```
diff --git a/.docs/content/1.installation/2.windows/0.installation-using-wsl2.md b/.docs/content/1.installation/2.windows/0.installation-using-wsl2.md
index e14358673..c6e0a6d2a 100644
--- a/.docs/content/1.installation/2.windows/0.installation-using-wsl2.md
+++ b/.docs/content/1.installation/2.windows/0.installation-using-wsl2.md
@@ -32,7 +32,7 @@ Then you can install the Ubuntu distribution from the Windows Store. We recommen
 
 You can also install Ubuntu LTS manually by following the instructions.
 
-```powershell
+```powershell [powershell]
 wsl --install -d Ubuntu
 ```
 
@@ -42,13 +42,13 @@ You can read more about Ubuntu on the [Microsoft documentation](https://learn.mi
 
 Once the installation is complete, verify the version of Ubuntu:
 
-```powershell
+```powershell [powershell]
 wsl -l -v
 ```
 
 You should see something like this:
 
-```powershell
+```powershell [powershell]
   NAME     STATE           VERSION
 * Ubuntu   Running         2
 # or Ubuntu-22.04 depending if you install the LTS or a specific version
@@ -56,19 +56,19 @@ You should see something like this:
 
 You can set the default WSL2 distro by using the following command:
 
-```powershell
+```powershell [powershell]
 wsl --set-default Ubuntu # or Ubuntu-22.04 depending if you install the LTS or a specific version
 ```
 
 Then, you can start your Ubuntu distribution:
 
-```powershell
+```powershell [powershell]
 wsl -d Ubuntu # or Ubuntu-22.04 depending if you install the LTS or a specific version
 ```
 
 Finally, you can update your packages:
 
-```bash
+```bash [shell]
 sudo apt update && sudo apt upgrade -y
 ```
 
diff --git a/.docs/content/1.installation/2.windows/1.wsl2-with-systemd.md b/.docs/content/1.installation/2.windows/1.wsl2-with-systemd.md
index 4f06dd901..2080e4047 100644
--- a/.docs/content/1.installation/2.windows/1.wsl2-with-systemd.md
+++ b/.docs/content/1.installation/2.windows/1.wsl2-with-systemd.md
@@ -16,7 +16,7 @@ Then, you will need to enable `systemd` support. In fact, ArmoniK uses Kubernete
 
 To enable `systemd` support, you must start your Ubuntu distribution and add these lines to the `/etc/wsl.conf` file (you will need sudo privileges):
 
-```bash
+```text [wsl.conf]
 [boot]
 systemd=true
 ```
@@ -27,25 +27,25 @@ Read more about `systemd` support on the [Microsoft documentation](https://devbl
 
 Then you must restart your Ubuntu distribution in order to apply the changes.
 
-```powershell
+```powershell [powershell]
 wsl --shutdown
 ```
 
 Then, restart your Ubuntu distribution.
 
-```powershell
+```powershell [powershell]
 wsl -d Ubuntu # Or Ubuntu-22.04 depending if you install the LTS or a specific version
 ```
 
 Don't forget to verify that `systemd` is enabled:
 
-```bash
+```bash [shell]
 systemctl
 ```
 
 To finish, update your packages:
 
-```bash
+```bash [shell]
 sudo apt update && sudo apt upgrade -y
 ```
 
@@ -57,7 +57,7 @@ Be careful, you must enable `systemd` support before installing ArmoniK.
 
 First, clone the ArmoniK repository (inside your home directory from WSL2 Ubuntu distribution):
 
-```bash
+```bash [shell]
 git clone https://github.com/aneoconsulting/ArmoniK.git
 ```
 
diff --git a/.docs/content/1.installation/2.windows/2.wsl2-with-genie.md b/.docs/content/1.installation/2.windows/2.wsl2-with-genie.md
index c10dee2d0..611545925 100644
--- a/.docs/content/1.installation/2.windows/2.wsl2-with-genie.md
+++ b/.docs/content/1.installation/2.windows/2.wsl2-with-genie.md
@@ -18,7 +18,7 @@ You must have installed WSL2 and Ubuntu before continuing. If you haven't, pleas
 
 To install `genie`, you can use the [install-genie](https://github.com/aneoconsulting/ArmoniK/blob/main/infrastructure/utils/scripts/installation/install-genie.sh) script:
 
-```bash
+```bash [shell]
 ./infrastructure/utils/scripts/installation/install-genie.sh
 ```
 
@@ -30,7 +30,7 @@ For manual installation, you can refer to [Genie How-To](https://arkane-systems.
 
 Finally, in order to avoid some issues, you need to mask some services.
 
-```bash
+```bash [shell]
 sudo systemctl disable getty@tty1.service multipathd.service multipathd.socket ssh.service
 sudo systemctl mask systemd-remount-fs.service
 ```
@@ -41,11 +41,11 @@ You can find more information about this issue on the [genie documentation](http
 
 Then, you need to exit your Ubuntu distribution and restart it.
 
-```bash
+```bash [shell]
 exit
 ```
 
-```powershell
+```powershell [powershell]
 wsl --shutdown
 ```
 
@@ -57,7 +57,7 @@ Please, do not start a WSL2 session with native `systemd` in parallel of `genie`
 
 Because `genie` must be started as PID 1, you need to start a session with `genie`.
 
-```bash
+```bash [shell]
 wsl genie -s
 ```
 
@@ -95,7 +95,7 @@ Be careful, you must enable `genie` support before installing ArmoniK.
 
 First, clone the ArmoniK repository (inside your home directory from WSL2 Ubuntu distribution):
 
-```bash
+```bash [shell]
 git clone https://github.com/aneoconsulting/ArmoniK.git
 ```
 
diff --git a/.docs/content/1.installation/2.windows/3.useful-commands-for-wsl2.md b/.docs/content/1.installation/2.windows/3.useful-commands-for-wsl2.md
index 627de362e..e330eed78 100644
--- a/.docs/content/1.installation/2.windows/3.useful-commands-for-wsl2.md
+++ b/.docs/content/1.installation/2.windows/3.useful-commands-for-wsl2.md
@@ -2,54 +2,54 @@
 
 - To verify the WSL version:
 
-  ```powershell
+  ```powershell [powershell]
   wsl --list --verbose
   ```
 
 - To view installed distro list:
 
-  ```powershell
+  ```powershell [powershell]
   wsl --list
   ```
 
 - To change the default distro:
 
-  ```powershell
+  ```powershell [powershell]
   wsl --set-default <distro_name>
   ```
 
 - To launch a distro:
 
-  ```powershell
+  ```powershell [powershell]
   wsl -d <distro_name>
   ```
 
 - To launch the default distro:
 
-  ```powershell
+  ```powershell [powershell]
   wsl
   ```
 
 - To launch a distro with a specific user:
 
-  ```powershell
+  ```powershell [powershell]
   wsl -d <distro_name> -u <user_name>
   ```
 
 - To launch a command in a distro:
 
-  ```powershell
+  ```powershell [powershell]
   wsl -d <distro_name> -e <command>
   ```
 
 - To lanch a distro in a specific directory:
 
-  ```powershell
+  ```powershell [powershell]
   wsl -d <distro_name> -w <directory>
   ```
 
 - To uninstall a distro:
 
-  ```powershell
+  ```powershell [powershell]
   wsl --unregister <distro_name>
   ```
diff --git a/.docs/content/1.installation/3.aws/aws-deployment-using-k3s.md b/.docs/content/1.installation/3.aws/aws-deployment-using-k3s.md
index 6834172cf..6bc3ad597 100644
--- a/.docs/content/1.installation/3.aws/aws-deployment-using-k3s.md
+++ b/.docs/content/1.installation/3.aws/aws-deployment-using-k3s.md
@@ -19,7 +19,7 @@ You must create and provide
 your [AWS programmatic access keys](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys)
 in your dev/test environment:
 
-```bash
+```bash [shell]
 mkdir -p ~/.aws
 cat <<EOF | tee ~/.aws/credentials
 [default]
@@ -32,7 +32,7 @@ EOF
 
 Use the following procedure to generate a SSH key pair and save it in `~/.ssh`:
 
-```bash
+```bash [shell]
 ssh-keygen -b 4096 -t rsa -f ~/.ssh/cluster-key
 ```
 
@@ -50,7 +50,7 @@ In [parameters.tfvars](https://github.com/aneoconsulting/ArmoniK/blob/main/infra
 * set the value of the parameter `ssh_key` with the content of the public SSH key `~/.ssh/cluster-key.pub` and the path
   to the private SSH key, for example:
 
-  ```bash
+  ```bash [shell]
   ssh_key = {
     private_key_path = "~/.ssh/cluster-key"
     public_key       = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQD3F6tyPEFEzV0LX3X8BsXdMsQz1x2cEikKDEY0aIj41qgxMCP/iteneqXSIFZBp5vizPvaoIR3Um9xK7PGoW8giupGn+EPuxIA4cDM4vzOqOkiMPhz5XK0whEjkVzTo4+S0puvDZuwIsdiW9mxhJc7tgBNL0cYlWSYVkz4G/fslNfRPW5mYAM49f4fhtxPb5ok4Q2Lg9dPKVHO/Bgeu5woMc7RY0p1ej6D4CKFE6lymSDJpW0YHX/wqE9+cfEauh7xZcG0q9t2ta6F6fmX0agvpFyZo8aFbXeUBr7osSCJNgvavWbM/06niWrOvYX2xwWdhXmXSrbX8ZbabVohBK41 email@example.com"
@@ -59,20 +59,20 @@ In [parameters.tfvars](https://github.com/aneoconsulting/ArmoniK/blob/main/infra
 
 * set the ID of an existing VPC and its subnet:
 
-  ```bash
+  ```bash [shell]
   vpc_id    = "<VPC_ID>"
   subnet_id = "<SUBNET_ID>"
   ```
 
 To deploy the cluster execute the command:
 
-```bash
+```bash [shell]
 make all
 ```
 
 The outputs display the public IP of each instance, like:
 
-```bash
+```bash [shell]
 master_public_ip = {
   "ip" = "54.185.23.147"
   "name" = "i-0168c936872babdf2"
@@ -111,6 +111,6 @@ manage your K3s cluster from your local machine.
 
 To delete all resources of the cluster created on AWS, execute the command:
 
-```bash
+```bash [shell]
 make destroy
 ```
diff --git a/.docs/content/1.installation/3.aws/aws-deployment-using-kubeadm.md b/.docs/content/1.installation/3.aws/aws-deployment-using-kubeadm.md
index 9bf37849a..1ee056354 100644
--- a/.docs/content/1.installation/3.aws/aws-deployment-using-kubeadm.md
+++ b/.docs/content/1.installation/3.aws/aws-deployment-using-kubeadm.md
@@ -19,7 +19,7 @@ You must create and provide
 your [AWS programmatic access keys](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys)
 in your dev/test environment:
 
-```bash
+```bash [shell]
 mkdir -p ~/.aws
 cat <<EOF | tee ~/.aws/credentials
 [default]
@@ -32,7 +32,7 @@ EOF
 
 Use the following procedure to generate a SSH key pair and save it in `~/.ssh`:
 
-```bash
+```bash [shell]
 ssh-keygen -b 4096 -t rsa -f ~/.ssh/cluster-key
 ```
 
@@ -50,7 +50,7 @@ In [parameters.tfvars](https://github.com/aneoconsulting/ArmoniK/blob/main/infra
 * set the value of the parameter `ssh_key` with the content of the public SSH key `~/.ssh/cluster-key.pub` and the path
   to the private SSH key, for example:
 
-  ```bash
+  ```bash [shell]
   ssh_key = {
     private_key_path = "~/.ssh/cluster-key"
     public_key       = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQD3F6tyPEFEzV0LX3X8BsXdMsQz1x2cEikKDEY0aIj41qgxMCP/iteneqXSIFZBp5vizPvaoIR3Um9xK7PGoW8giupGn+EPuxIA4cDM4vzOqOkiMPhz5XK0whEjkVzTo4+S0puvDZuwIsdiW9mxhJc7tgBNL0cYlWSYVkz4G/fslNfRPW5mYAM49f4fhtxPb5ok4Q2Lg9dPKVHO/Bgeu5woMc7RY0p1ej6D4CKFE6lymSDJpW0YHX/wqE9+cfEauh7xZcG0q9t2ta6F6fmX0agvpFyZo8aFbXeUBr7osSCJNgvavWbM/06niWrOvYX2xwWdhXmXSrbX8ZbabVohBK41 email@example.com"
@@ -59,20 +59,20 @@ In [parameters.tfvars](https://github.com/aneoconsulting/ArmoniK/blob/main/infra
 
 * set the ID of an existing VPC and its subnet:
 
-  ```bash
+  ```bash [shell]
   vpc_id    = "<VPC_ID>"
   subnet_id = "<SUBNET_ID>"
   ```
 
 To deploy the cluster execute the command:
 
-```bash
+```bash [shell]
 make all
 ```
 
 The outputs display the public IP of each instance, like:
 
-```bash
+```bash [shell]
 master_public_ip = {
   "ip" = "54.185.23.147"
   "name" = "i-0168c936872babdf2"
@@ -111,6 +111,6 @@ manage your Kubeadm cluster from your local machine.
 
 To delete all resources of the cluster created on AWS, execute the command:
 
-```bash
+```bash [shell]
 make destroy
 ```
diff --git a/.docs/content/2.guide/1.how-to/how-to-configure-authentication.md b/.docs/content/2.guide/1.how-to/how-to-configure-authentication.md
index 5fcd1ae73..89e3130eb 100644
--- a/.docs/content/2.guide/1.how-to/how-to-configure-authentication.md
+++ b/.docs/content/2.guide/1.how-to/how-to-configure-authentication.md
@@ -136,7 +136,7 @@ Please note that the ```Username``` and ```RoleName``` **MUST** be uniquely defi
 
 The resulting configuration is stored in the MongoDB database. If the database is restarted when MongoDB isn't setup with a persistent volume or if the database is emptied it needs to be repopulated by relaunching the authentication-in-database job. In a local deployment, this can be achieved using the following shell command:
 
-```bash
+```bash [shell]
 kubectl -n armonik get job authentication-in-database -o json | jq "del(.spec.selector)" | jq "del(.spec.template.metadata.labels)" | kubectl -n armonik replace --force -f -
 ```
 
@@ -148,13 +148,13 @@ The following json is an example defining two users, with their own different ro
 {
   "certificates_list":[
     {
-      "CN": "CNOfUserSubmitter", 
-      "Fingerprint" : "752c14ea195c369bac3c3b7896975ee9fd15eeb7", 
+      "CN": "CNOfUserSubmitter",
+      "Fingerprint" : "752c14ea195c369bac3c3b7896975ee9fd15eeb7",
       "Username": "UserSubmitter"
     },
     {
-      "CN": "CNOfUserMonitoring", 
-      "Fingerprint" : "c26dc0bf68e25099bc4a85b631efdb93d0768a20", 
+      "CN": "CNOfUserMonitoring",
+      "Fingerprint" : "c26dc0bf68e25099bc4a85b631efdb93d0768a20",
       "Username": "UserMonitoring"
     }
   ],
@@ -162,7 +162,7 @@ The following json is an example defining two users, with their own different ro
     {
       "Username": "UserSubmitter",
       "Roles": [
-        "Submitter", 
+        "Submitter",
         "Monitoring"
         ] // Note here that the permissions of Monitoring are included in Submitter, thus Monitoring could be omitted here
     },
diff --git a/.docs/content/2.guide/1.how-to/how-to-configure-seq.md b/.docs/content/2.guide/1.how-to/how-to-configure-seq.md
index 3986f156a..c2bb1c264 100644
--- a/.docs/content/2.guide/1.how-to/how-to-configure-seq.md
+++ b/.docs/content/2.guide/1.how-to/how-to-configure-seq.md
@@ -9,7 +9,7 @@ Then, redeploy.
 
 When you perform the command:
 
-```bash
+```bash [shell]
 kubectl get svc -n armonik
 ```