diff --git a/firmware/config/engines/mazda_miata_vvt.cpp b/firmware/config/engines/mazda_miata_vvt.cpp
index fe55fecf1a..0eff130474 100644
--- a/firmware/config/engines/mazda_miata_vvt.cpp
+++ b/firmware/config/engines/mazda_miata_vvt.cpp
@@ -17,6 +17,7 @@
  *
  * Crank   primary trigger        PA5 (3E in Miata board)       white
  * Cam     vvt input              PC6 (3G in Miata board)       blue
+ * Wideband input                 PA3 (3J in Miata board)
  *
  * coil1/4          (p1 +5 VP)    PE14
  * coil2/2          (p1 +5 VP)    PC7
@@ -27,6 +28,7 @@
  *
  * VVT solenoid on aux PID#1      PE3
  *
+ *
  */
 
 #include "mazda_miata_vvt.h"
diff --git a/unit_tests/readme.txt b/unit_tests/readme.txt
index 621959dacd..3d42bce8d1 100644
--- a/unit_tests/readme.txt
+++ b/unit_tests/readme.txt
@@ -1,6 +1,7 @@
-In this folder we have a naive test set. I am not sure what is the best approach to tests in C (someone can educate me), but my approach is:
+In this folder we have a naive test suite.
 
-1) with a symlink linking some (only some, not all) folders of the firmware implementation, we can compile some files of the firmware as win32 code.
-Please execute the 'makelinks.bat' file to get the links. On XP you might need to execute 'junction.exe' before exuting the .bat file.
+I am not sure what is the best approach to tests in C (someone can educate me), but my approach is:
 
-2) we then compile & run the .exe, which is expected to say SUCCESS and not fail :)
\ No newline at end of file
+Unit tests are not aware of ChibiOS or ARM or else, they are just plain C/C++ which you build for your desktop, not your MCU.
+
+Run 'make' to build desktop binary & run it on your PC/Mac, it's expected to say SUCCESS and not fail :)
\ No newline at end of file