diff --git a/docs/docs/development/build-flash.md b/docs/docs/development/build-flash.md
index 6f4ba84d..f57c4b5c 100644
--- a/docs/docs/development/build-flash.md
+++ b/docs/docs/development/build-flash.md
@@ -130,8 +130,8 @@ The above build commands generate a UF2 file in `build/zephyr` (or
 `build/left|right/zephyr` if you followed the instructions for splits) and is by
 default named `zmk.uf2`. If your board supports USB Flashing Format (UF2), copy
 that file onto the root of the USB mass storage device for your board. The
-controller should flash your built firmware and automatically restart once
-flashing is complete.
+controller should flash your built firmware, unmount the USB storage device and
+automatically restart once flashing is complete.
 
 Alternatively, if your board supports flashing and you're not developing from
 within a Dockerized environment, enable Device Firmware Upgrade (DFU) mode on
diff --git a/docs/docs/user-setup.md b/docs/docs/user-setup.md
index 8faa72df..9d04c347 100644
--- a/docs/docs/user-setup.md
+++ b/docs/docs/user-setup.md
@@ -198,8 +198,9 @@ To flash the firmware, first put your board into bootloader mode by double click
 or the one that is part of your keyboard). The controller should appear in your OS as a new USB storage device.
 
 Once this happens, copy the correct UF2 file (e.g. left or right if working on a split), and paste it onto the root of that USB mass
-storage device. Once the flash is complete, the controller should automatically restart, and load your newly flashed firmware. It is
-recommended that you test your keyboard works over USB first to rule out hardware issues, before trying to connect to it wirelessly.
+storage device. Once the flash is complete, the controller should unmount the USB storage, automatically restart and load your newly
+flashed firmware. It is recommended that you test your keyboard works over USB first to rule out hardware issues, before trying to
+connect to it wirelessly.
 
 :::caution Split keyboards