diff --git a/Hardware.md b/Hardware.md
index 4206139..4816dbc 100644
--- a/Hardware.md
+++ b/Hardware.md
@@ -93,7 +93,7 @@ Here are some good articles discussing jitter on linux systems:
 - https://community.mellanox.com/s/article/rivermax-linux-performance-tuning-guide--1-x (General Tips)
 
 We use the following settings: 
-```shell script
+```
 mce=ignore_ce nosoftlockup nmi_watchdog=0 transparent_hugepage=never processor.max_cstate=1 idle=poll nohz=on nohz_full=1-7
 ```
 
@@ -115,7 +115,7 @@ our benchmark cores, to ensure low influence of background tasks. Cgroups also n
 the real time scheduler, as described here https://www.linuxjournal.com/article/10165, because
 they allow to adapt the scheduler to ignore the other cores in its decision making process.
 Note the exclusive cpu groups in this output:
-```shell script
+```sh
 florian@bananapim3:~$ cset set
 cset: 
          Name       CPUs-X    MEMs-X Tasks Subs Path
@@ -126,7 +126,7 @@ cset:
 ```
 
 Create a file called 'setup_cgroups.sh' and modify it with 'chmod +x setup_cgroups.sh':
-```shell script
+```sh
 #!/bin/bash
 
 sudo cset shield --cpu=1-7 -k on
@@ -142,7 +142,7 @@ Limiting the frequency to 1GHz makes sure that the banana PI dose not throttle d
 Additionally, disabling any dynamic frequency scaling makes tests more reproducable.
 
 Create a file called 'setup_cpu.sh' and modify it with 'chmod +x setup_cpu.sh':
-```shell script
+```sh
 #!/bin/bash
 
 echo "Writing frequency utils settings file..."
@@ -160,7 +160,7 @@ echo "Test your cooling by stressing the cpu and watching the temperature output
 ```
 
 Create a file called 'watch_cpu.sh' and modify it with 'chmod +x watch_cpu.sh':
-````shell script
+````sh
 #!/bin/bash
 
 echo "Min/Max Frequencies"
@@ -190,7 +190,7 @@ Interrupts can infer with our benchmarks. We therefore map them to core 0 if pos
 cores 1 to 7.
 
 Create a file called 'map_interrupts_core_0.sh' and modify it with 'chmod +x map_interrupts_core_0.sh':
-```shell script
+```sh
 #!/bin/bash
 
 echo "Try to map interrupts to core 0."
@@ -215,7 +215,7 @@ leaving the system in a responsive state if a RT application eats all CPU. We do
 try to get a very predictable behavior in our RT scheduler.
 
 Create a file called 'setup_rt.sh' and modify it with 'chmod +x setup_rt.sh':
-```shell script
+```sh
 #!/bin/bash
 
 sysctl -w kernel.sched_rt_runtime_us=1000000