Rewritten event system to remove all macros, to make user code clearer.

[pub/USBasp.git] / LUFA / WritingBoardDrivers.txt

diff --git a/LUFA/WritingBoardDrivers.txt b/LUFA/WritingBoardDrivers.txt
index 0d0e74d..cf4f47c 100644 (file)
--- 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\r
  *  compiler to use the USBKEY board hardware drivers.\r
  *\r
  *  passed to the compiler, with a constant of BOARD_{Name}. For example <b>-DBOARD=BOARD_USBKEY</b> instructs the\r
  *  compiler to use the USBKEY board hardware drivers.\r
  *\r

- *  If your application does not use *any* board level drivers, you can ommit the definition of the BOARD macro.\r
+ *  If your application does not use *any* board level drivers, you can omit the definition of the BOARD macro.\r

  *  However, some users may wish to write their own custom board hardware drivers which are to remain compatible\r
  *  with the LUFA hardware API. To do this, the BOARD macro should be defined to the value BOARD_USER. This indicates\r
  *  that the board level drivers should be located in a folder named "Board" located inside the application's folder.\r
  *  However, some users may wish to write their own custom board hardware drivers which are to remain compatible\r
  *  with the LUFA hardware API. To do this, the BOARD macro should be defined to the value BOARD_USER. This indicates\r
  *  that the board level drivers should be located in a folder named "Board" located inside the application's folder.\r