From d889c37644f5fffa3aa4d8700da6d79230e30561 Mon Sep 17 00:00:00 2001
From: metanoic <5554798+metanoic@users.noreply.github.com>
Date: Sat, 21 Jul 2018 02:26:48 -0500
Subject: [PATCH] Fix typo

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

diff --git a/docs/developer-guide.md b/docs/developer-guide.md
index 4a37082c..263affcc 100644
--- a/docs/developer-guide.md
+++ b/docs/developer-guide.md
@@ -32,7 +32,7 @@ The recommended tools for ODrive development are:
 
  * **make**: Used to invoke tup
  * **Tup**: The build system used to invoke the compile commands
- * **ARM GNU Compiler**: For cross-comiling code
+ * **ARM GNU Compiler**: For cross-compiling code
  * **ARM GDB**: For debugging the code and stepping through on the device
  * **OpenOCD**: For flashing the ODrive with the STLink/v2 programmer
  * **Python**: For running the Python tools