diff --git a/How-to-Unlock-MCU-Flash.md b/How-to-Unlock-MCU-Flash.md
index 4b78321..edaa50c 100644
--- a/How-to-Unlock-MCU-Flash.md
+++ b/How-to-Unlock-MCU-Flash.md
@@ -16,11 +16,12 @@ This procedure will erase the stock MCU firmware irreversibly! Perform these ste
 * Step 4: If you get the message `Can not read memory!` the MCU is most probably locked
 * Step 5: Go to `Target` and click `Option Bytes` 
 
-![unlock2](https://github.com/EmanuelFeru/hoverboard-firmware-hack-FOC/blob/main/docs/pictures/wiki_unlock/unlock_mcu_2.png)
+![unlock2](https://github.com/EmanuelFeru/hoverboard-firmware-hack-FOC/blob/main/docs/pictures/wiki_unlock/unlock_mcu_2.png) 
 
 * Step 6: Select **Disable** in `Read Out Protection` drop-down menu and click `Apply`
 
 ![unlock3](https://github.com/EmanuelFeru/hoverboard-firmware-hack-FOC/blob/main/docs/pictures/wiki_unlock/unlock_mcu_3.png)
+<br>⚠️ On GD32 chips, WD_SW should be checked<br>
 
 * Step 7: Click `Connect to target`
 
@@ -28,6 +29,8 @@ This procedure will erase the stock MCU firmware irreversibly! Perform these ste
 
 * Step 8: If you see the window above, then you have successfully unlocked your MCU. You can now flash the MCU.
 
+<br>⚠️ Make sure you disconnect st-link utility if you are using another tool for flashgin the firmware later<br>
+
 ## :toolbox: Troubleshooting
 If you get funny, unexpected behavior from your board after flashing (see this [thread](https://github.com/EmanuelFeru/hoverboard-sideboard-hack-GD/issues/3)), it is most likely that the unlocking process did not succeed properly. To fix it follow these steps:
 * Step 1: Lock the GD32 following the Steps above in reverse order