From c2fb132cbc161fcb2cd668e2247fdfb55cc6db2d Mon Sep 17 00:00:00 2001
From: Oskar Weigl <oskar.weigl@gmail.com>
Date: Sun, 4 Aug 2019 11:52:56 -0700
Subject: [PATCH] Update odrivetool.md

---
 docs/odrivetool.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/odrivetool.md b/docs/odrivetool.md
index 13616a37..cb8059c3 100644
--- a/docs/odrivetool.md
+++ b/docs/odrivetool.md
@@ -89,7 +89,7 @@ To compile firmware from source, refer to the [developer guide](developer-guide)
 * If the DFU script can't find the device, try forcing it into DFU mode.
 
   <details><summary markdown="span">How to force DFU mode (ODrive v3.5)</summary><div markdown="block">
-  Flick the DIP switch that "DFU, RUN" to "DFU" and power cycle the board. After you're done, put the switch back into the "RUN" position and power cycle the board again.
+  Flick the DIP switch that "DFU, RUN" to "DFU" and power cycle the board. After you're done upgrading firmware, don't forget to put the switch back into the "RUN" position and power cycle the board again.
   </div></details>
 
   <details><summary markdown="span">How to force DFU mode (ODrive v3.1, v3.2)</summary><div markdown="block">