Cold boot/warm boot update names

docs/transparent-validation/rte/v1.1.0/specification.md

@@ -51,7 +51,7 @@ operating system and starts automatically on port `8000` without the necessity
 of additional configuration. REST API dashboard can be reached through the
 Internet browser and provides a possibility to:
 
-* control Device Under Test power supply (coldboot and warmboot)
+* control Device Under Test power supply (cold boot and warm boot)
 * reset Device Under Test platform
 * flash Device Under Test firmware
 More information can be found at [RteCtrl repository](https://github.com/3mdeb/RteCtrl)

docs/unified-test-documentation/dasharo-compatibility/31G-ec-and-superio.md

@@ -1560,11 +1560,11 @@ properly by the operating system.
 
 1. Pressing the button once should increase the keyboard backlight.
 
-## ECR025.001 Permanent keyboard illumination after cold-boot (Firmware)
+## ECR025.001 Permanent keyboard illumination after cold boot (Firmware)
 
 **Test description**
 
-This test aims to verify that after performing cold-boot, keyboard still
+This test aims to verify that after performing cold boot, keyboard still
 illuminates in firmware.
 
 **Test configuration data**
@@ -1587,13 +1587,13 @@ illuminates in firmware.
 
 **Expected result**
 
-1. After cold-boot keyboard brightness and colors settings remain the same.
+1. After cold boot keyboard brightness and colors settings remain the same.
 
-## ECR025.002 Permanent keyboard illumination after cold-boot (Ubuntu 22.04)
+## ECR025.002 Permanent keyboard illumination after cold boot (Ubuntu 22.04)
 
 **Test description**
 
-This test aims to verify that after performing cold-boot, keyboard still
+This test aims to verify that after performing cold boot, keyboard still
 illuminates in Ubuntu 22.04.
 
 **Test configuration data**
@@ -1620,13 +1620,13 @@ illuminates in Ubuntu 22.04.
 
 **Expected result**
 
-1. After cold-boot keyboard brightness and colors settings remain the same.
+1. After cold boot keyboard brightness and colors settings remain the same.
 
-## ECR025.003 Permanent keyboard illumination after cold-boot (Windows 11)
+## ECR025.003 Permanent keyboard illumination after cold boot (Windows 11)
 
 **Test description**
 
-This test aims to verify that after performing cold-boot, keyboard still
+This test aims to verify that after performing cold boot, keyboard still
 illuminates in Windows 11.
 
 **Test configuration data**
@@ -1653,13 +1653,13 @@ illuminates in Windows 11.
 
 **Expected result**
 
-1. After cold-boot keyboard brightness and colors settings remain the same.
+1. After cold boot keyboard brightness and colors settings remain the same.
 
-## ECR026.001 Permanent keyboard illumination after warm-boot (Firmware)
+## ECR026.001 Permanent keyboard illumination after warm boot (Firmware)
 
 **Test description**
 
-This test aims to verify that after performing warm-boot, keyboard still
+This test aims to verify that after performing warm boot, keyboard still
 illuminates in firmware.
 
 **Test configuration data**
@@ -1681,13 +1681,13 @@ illuminates in firmware.
 
 **Expected result**
 
-1. After warm-boot keyboard brightness and colors settings remain the same.
+1. After warm boot keyboard brightness and colors settings remain the same.
 
-## ECR026.002 Permanent keyboard illumination after warm-boot (Ubuntu 22.04)
+## ECR026.002 Permanent keyboard illumination after warm boot (Ubuntu 22.04)
 
 **Test description**
 
-This test aims to verify that after performing warm-boot, keyboard still
+This test aims to verify that after performing warm boot, keyboard still
 illuminates in Ubuntu 22.04.
 
 **Test configuration data**
@@ -1713,13 +1713,13 @@ illuminates in Ubuntu 22.04.
 
 **Expected result**
 
-1. After warm-boot keyboard brightness and colors settings remain the same.
+1. After warm boot keyboard brightness and colors settings remain the same.
 
-## ECR026.003 Permanent keyboard illumination after warm-boot (Windows 11)
+## ECR026.003 Permanent keyboard illumination after warm boot (Windows 11)
 
 **Test description**
 
-This test aims to verify that after performing warm-boot, keyboard still
+This test aims to verify that after performing warm boot, keyboard still
 illuminates in Windows 11.
 
 **Test configuration data**
@@ -1745,7 +1745,7 @@ illuminates in Windows 11.
 
 **Expected result**
 
-1. After warm-boot keyboard brightness and colors settings remain the same.
+1. After warm boot keyboard brightness and colors settings remain the same.
 
 ## ECR027.001 Permanent keyboard illumination after reboot (Firmware)
 

docs/unified-test-documentation/dasharo-compatibility/31N-usb-boot.md

@@ -1,11 +1,11 @@
 # Dasharo Compatibility: USB Boot
 
-## UBT001.001 USB detect and boot after coldboot
+## UBT001.001 USB detect and boot after cold boot
 
 **Test description**
 
 This test aims to verify that the DUT properly detects USB device and boots
-into the operating system after coldboot (reboot realized by power supply
+into the operating system after cold boot (reboot realized by power supply
 cutting off then restoring back). This test case may be re-done several times
 to specify the platform and connection stability.
 
@@ -32,14 +32,14 @@ to specify the platform and connection stability.
 **Expected result**
 
 The `Debian GNU/Linux` is visible and confirms successful boot into OS after
-coldboot.
+cold boot.
 
-## UBT002.001 USB detect and boot after warmboot
+## UBT002.001 USB detect and boot after warm boot
 
 **Test description**
 
 This test aims to verify that the DUT properly detects USB device and boots
-into the operating system after warmboot (reboot realized by device turning
+into the operating system after warm boot (reboot realized by device turning
 off then turning on). This test case may be re-done several times to specify
 the platform and connection stability.
 
@@ -65,7 +65,7 @@ the platform and connection stability.
 **Expected result**
 
 The `Debian GNU/Linux` is visible and confirms successful boot into OS after
-warmboot.
+warm boot.
 
 ## UBT003.001 USB detect and boot after system reboot
 

docs/unified-test-documentation/dasharo-compatibility/31O-usb-detect.md

@@ -1,11 +1,11 @@
 # Dasharo Compatibility: USB Detection
 
-## UDT001.001 USB detection after coldboot
+## UDT001.001 USB detection after cold boot
 
 **Test description**
 
 This test aims to verify that the DUT properly detects USB device after
-coldboot (reboot realized by power supply cutting off then restoring back).
+cold boot (reboot realized by power supply cutting off then restoring back).
 This test case may be re-done several times to specify the platform and
 connection stability.
 
@@ -30,15 +30,16 @@ connection stability.
 **Expected result**
 
 The `USB_STICK` entry is visible which confirms successful detection after
-coldboot.
+cold boot.
 
-## UDT002.001 USB detection after warmboot
+## UDT002.001 USB detection after warm boot
 
 **Test description**
 
 This test aims to verify that the DUT properly detects USB device after
-warmboot (reboot realized by device turning off then turning on). This test case
-may be re-done several times to specify the platform and connection stability.
+warm boot (reboot realized by device turning off then turning on). This test
+case may be re-done several times to specify the platform and connection
+stability.
 
 **Test configuration data**
 
@@ -60,7 +61,7 @@ may be re-done several times to specify the platform and connection stability.
 **Expected result**
 
 The `USB_STICK` entry is visible which confirms successful detection after
-warmboot.
+warm boot.
 
 ## UDT003.001 USB detection after system reboot
 

docs/unified-test-documentation/dasharo-compatibility/323-docking-station-detect.md

@@ -14,12 +14,12 @@
     [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
 1. The `USB-C docking station` connected to the USB-C port.
 
-## DUD001.001 Docking station detection after coldboot (Ubuntu 22.04)
+## DUD001.001 Docking station detection after cold boot (Ubuntu 22.04)
 
 **Test description**
 
 This test aims to verify that the DUT properly detects the docking station after
-coldboot (realized by power supply cutting off then restoring back).
+cold boot (realized by power supply cutting off then restoring back).
 This test case may be re-done several times to specify the platform and
 connection stability.
 
@@ -60,12 +60,12 @@ Bus 002 Device 009: Prolific Technology, Inc. USB SD Card Reader
 Bus 002 Device 008: VIA Labs, Inc. USB3.0 Hub
 ```
 
-## DUD002.001 Docking station detection after warmboot (Ubuntu 22.04)
+## DUD002.001 Docking station detection after warm boot (Ubuntu 22.04)
 
 **Test description**
 
 This test aims to verify that the DUT properly detects the docking station
-after warmboot (realized by device turning off then turning on). This test case
+after warm boot (realized by device turning off then turning on). This test case
 may be re-done several times to specify the platform and connection stability.
 
 **Test configuration data**

docs/unified-test-documentation/dasharo-compatibility/352-thunderbolt-docking-station-detect.md

@@ -14,12 +14,12 @@
     [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
 1. The `Thunderbolt docking station` connected to the Thunderbolt port.
 
-## TDD001.001 Docking station detection after coldboot (Ubuntu 22.04)
+## TDD001.001 Docking station detection after cold boot (Ubuntu 22.04)
 
 **Test description**
 
 This test aims to verify that the DUT properly detects the docking station after
-coldboot (realized by power supply cutting off then restoring back).
+cold boot (realized by power supply cutting off then restoring back).
 This test case may be re-done several times to specify the platform and
 connection stability.
 
@@ -60,12 +60,12 @@ Bus 002 Device 009: Prolific Technology, Inc. USB SD Card Reader
 Bus 002 Device 008: VIA Labs, Inc. USB3.0 Hub
 ```
 
-## TDD002.001 Docking station detection after warmboot (Ubuntu 22.04)
+## TDD002.001 Docking station detection after warm boot (Ubuntu 22.04)
 
 **Test description**
 
 This test aims to verify that the DUT properly detects the docking station
-after warmboot (realized by device turning off then turning on). This test case
+after warm boot (realized by device turning off then turning on). This test case
 may be re-done several times to specify the platform and connection stability.
 
 **Test configuration data**

docs/unified-test-documentation/dasharo-performance/400-coreboot-boot-measure.md

@@ -13,11 +13,11 @@
 1. Download `cbmem` from <https://cloud.3mdeb.com/index.php/s/zTqkJQdNtJDo5Nd>
     to the DUT.
 
-## CBMEM001.001 coreboot booting time measure after coldboot (Ubuntu 22.04)
+## CBMEM001.001 coreboot booting time measure after cold boot (Ubuntu 22.04)
 
 **Test description**
 
-This test aims to verify whether the DUT boots after coldboot and how long this
+This test aims to verify whether the DUT boots after cold boot and how long this
 process takes. This test case may be re-done several times to to average the
 results and specify the platform stability.
 
@@ -44,11 +44,11 @@ sudo ./cbmem -T
 The output of the command should contain the information about duration of
 all boot stages.
 
-## CBMEM002.001 coreboot booting time measure after warmboot (Ubuntu 22.04)
+## CBMEM002.001 coreboot booting time measure after warm boot (Ubuntu 22.04)
 
 **Test description**
 
-This test aims to verify whether the DUT boots after warmboot and how long this
+This test aims to verify whether the DUT boots after warm boot and how long this
 process takes. This test case may be re-done several times to to average the
 results and specify the platform stability.
 

docs/unified-test-documentation/dasharo-performance/403-device-boot-measure.md

@@ -13,11 +13,11 @@
 1. Proceed with the
     [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
 
-## DBM001.001 Device boot measure after coldboot (Ubuntu 22.04)
+## DBM001.001 Device boot measure after cold boot (Ubuntu 22.04)
 
 **Test description**
 
-This test aims to verify whether the DUT boots after coldboot and how long this
+This test aims to verify whether the DUT boots after cold boot and how long this
 process takes. This test case may be re-done several times to to average the
 results and specify the platform stability.
 
@@ -50,11 +50,11 @@ results and specify the platform stability.
 The output of the command should contain the information about duration of
 all boot stages.
 
-## DBM002.001 Device boot measure after warmboot (Ubuntu 22.04)
+## DBM002.001 Device boot measure after warm boot (Ubuntu 22.04)
 
 **Test description**
 
-This test aims to verify whether the DUT boots after warmboot and how long this
+This test aims to verify whether the DUT boots after warm boot and how long this
 process takes. This test case may be re-done several times to to average the
 results and specify the platform stability.
 

docs/unified-test-documentation/dasharo-performance/405-fan-control-measure.md

@@ -19,12 +19,12 @@
     apt-get install --assume-yes lm-sensors
     ```
 
-## FNM001.001 Fan does not stuck after coldboot (Ubuntu 22.04)
+## FNM001.001 Fan does not stuck after cold boot (Ubuntu 22.04)
 
 **Test description**
 
 This test aims to verify that the fan does not stuck on initial or any defined
-speed after coldboot.
+speed after cold boot.
 
 **Test configuration data**
 
@@ -64,12 +64,12 @@ Example output:
 fan1:        1131 RPM  (min =  329 RPM)
 ```
 
-## FNM002.001 Fan does not stuck after warmboot (Ubuntu 22.04)
+## FNM002.001 Fan does not stuck after warm boot (Ubuntu 22.04)
 
 **Test description**
 
 This test aims to verify that the fan does not stuck on initial or any defined
-speed after warmboot.
+speed after warm boot.
 
 **Test configuration data**
 

docs/unified-test-documentation/dasharo-performance/407-ubuntu-booting-performance-test.md

@@ -13,12 +13,12 @@
 1. Proceed with the
    [Generic test setup: OS boot from disk](../../generic-test-setup/#os-boot-from-disk).
 
-## BUB001.001 Boot Ubuntu LTS from disk after cold-boot
+## BUB001.001 Boot Ubuntu LTS from disk after cold boot
 
 **Test description**
 
 This test aims to verify that Ubuntu LTS could be booted from the disk on the
-DUT after cold-boot. The test is performed in multiple iterations.
+DUT after cold boot. The test is performed in multiple iterations.
 
 **Test configuration data**
 
@@ -43,12 +43,12 @@ DUT after cold-boot. The test is performed in multiple iterations.
 
 The `OPERATING_SYSTEM` login screen should be displayed.
 
-## BUB002.001 Boot Ubuntu LTS from disk after warm-boot
+## BUB002.001 Boot Ubuntu LTS from disk after warm boot
 
 **Test description**
 
 This test aims to verify that Ubuntu LTS could be booted from the disk on the
-DUT after warm-boot. The test is performed in multiple iterations.
+DUT after warm boot. The test is performed in multiple iterations.
 
 **Test configuration data**