aboutsummaryrefslogtreecommitdiffstats
path: root/LUFA/WritingBoardDrivers.txt
diff options
context:
space:
mode:
authorDean Camera <dean@fourwalledcubicle.com>2009-04-19 14:29:57 +0000
committerDean Camera <dean@fourwalledcubicle.com>2009-04-19 14:29:57 +0000
commit619b0b7b6b44e4422ea9aeb0cde41343bb5dda70 (patch)
tree86746a10853d261e18a4ad37b4e970a4917e89a0 /LUFA/WritingBoardDrivers.txt
parent663f449c10b9a77a429aaa81066ce2b43ca6dc39 (diff)
downloadlufa-619b0b7b6b44e4422ea9aeb0cde41343bb5dda70.tar.gz
lufa-619b0b7b6b44e4422ea9aeb0cde41343bb5dda70.tar.bz2
lufa-619b0b7b6b44e4422ea9aeb0cde41343bb5dda70.zip
Spell checked non-source documentation pages.
Diffstat (limited to 'LUFA/WritingBoardDrivers.txt')
-rw-r--r--LUFA/WritingBoardDrivers.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/LUFA/WritingBoardDrivers.txt b/LUFA/WritingBoardDrivers.txt
index 0d0e74d04..cf4f47c13 100644
--- a/LUFA/WritingBoardDrivers.txt
+++ b/LUFA/WritingBoardDrivers.txt
@@ -13,7 +13,7 @@
* passed to the compiler, with a constant of BOARD_{Name}. For example <b>-DBOARD=BOARD_USBKEY</b> instructs the
* compiler to use the USBKEY board hardware drivers.
*
- * If your application does not use *any* board level drivers, you can ommit the definition of the BOARD macro.
+ * If your application does not use *any* board level drivers, you can omit the definition of the BOARD macro.
* However, some users may wish to write their own custom board hardware drivers which are to remain compatible
* with the LUFA hardware API. To do this, the BOARD macro should be defined to the value BOARD_USER. This indicates
* that the board level drivers should be located in a folder named "Board" located inside the application's folder.