diff --git a/Firmware-Compatibility.md b/Firmware-Compatibility.md
index 298e1f9..2e1f2b1 100644
--- a/Firmware-Compatibility.md
+++ b/Firmware-Compatibility.md
@@ -9,7 +9,7 @@ For those you can use the alternate mapping by changing parameter BOARD_VARIANT
 It could be that your mainboard was designed differently, please check if the pin mapping is matching with the one in this [section](https://github.com/EFeru/hoverboard-firmware-hack-FOC/wiki/Firmware-Compatibility#pin-mapping).
 
 ## :toolbox: Troubleshooting
-* Motors are cogging/not running in a smooth way - please try to swap the phases. Usually, color-correct mapping (blue to blue, green to green, yellow to yellow) works fine. However, some hoverboards have a different layout then others, and this might be the reason your motor isn't spinning well
+* Motors are cogging/not running in a smooth way - please try to swap the phases. Usually, color-correct mapping (blue to blue, green to green, yellow to yellow) works fine. However, some hoverboards have a different layout then others, and this might be the reason your motor isn't spinning well. It could also be that a defective mosfet is not turning ON
 * In speed mode, wheels are running at maximum speed - find the right mapping for hall sensors, firmware probably measures a speed with opposite sign
 * With hovercar variant in torque mode, braking actually accelerates - find the right mapping for hall sensors, firmware probably measures a speed with opposite sign
 * If you have a problem on a single motor, try to swap the motors to understand if the problem is coming from the board or the wheel. Some boards have a different phase mapping or current sensing on one the wheels (discussed [here](https://github.com/EFeru/hoverboard-firmware-hack-FOC/issues/230) )