X-Git-Url: http://git.linex4red.de/pub/USBasp.git/blobdiff_plain/071e02c6b6b4837fa9cf0b6d4c749994e02638d7..86a2be8536d9e246b2a87421c41b78c9fc1f25fc:/LUFA/ManPages/WritingBoardDrivers.txt

diff --git a/LUFA/ManPages/WritingBoardDrivers.txt b/LUFA/ManPages/WritingBoardDrivers.txt
index c3371a93a..e09e7d0d9 100644
--- a/LUFA/ManPages/WritingBoardDrivers.txt
+++ b/LUFA/ManPages/WritingBoardDrivers.txt
@@ -18,9 +18,10 @@
  *  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.
  *
- *  When used, the driver stub files located in the DriverStubs folder should be copied to the user Board directory,
- *  and fleshed out to include the values and code needed to control the custom board hardware. Once done, the existing
- *  LUFA board level APIs (accessed in the regular LUFA/Drivers/Board/ folder) will redirect to the user board drivers,
- *  maintaining code compatibility and allowing for a different board to be selected through the project makefile with
- *  no code changes.
+ *  When used, the driver stub files located in the LUFA/CodeTemplates/DriverStubs folder should be copied to the user
+ *  Board/ directory, and fleshed out to include the values and code needed to control the custom board hardware. Once
+ *  done, the existing LUFA board level APIs (accessed in the regular LUFA/Drivers/Board/ folder) will redirect to the
+ *  user board drivers, maintaining code compatibility and allowing for a different board to be selected through the
+ *  project makefile with no code changes.
  */
+