docs: add terminal into code blocks (#1146)

.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
 ```
 

.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
 ```
 

.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
   ```