Minor documentation and formatting updates.

diff --git a/LUFA/Build/lufa_sources.mk b/LUFA/Build/lufa_sources.mk
index 0e026c5..f63718c 100644 (file)
--- a/LUFA/Build/lufa_sources.mk
+++ b/LUFA/Build/lufa_sources.mk
@@ -113,4 +113,4 @@ LUFA_SRC_ALL_FILES   := $(LUFA_SRC_USB)            \
                         $(LUFA_SRC_TEMPERATURE)    \
                         $(LUFA_SRC_SERIAL)         \
                         $(LUFA_SRC_TWI)            \
-                                           $(LUFA_SRC_PLATFORM)
+                        $(LUFA_SRC_PLATFORM)

diff --git a/LUFA/DoxygenPages/BuildSystem.txt b/LUFA/DoxygenPages/BuildSystem.txt
index 9906fc6..a1ed841 100644 (file)
--- a/LUFA/DoxygenPages/BuildSystem.txt
+++ b/LUFA/DoxygenPages/BuildSystem.txt
@@ -15,14 +15,15 @@
  *  For details on the prerequisites needed for Linux and Windows machines to be able to use the LUFA\r
  *  build system, see \ref Sec_Prerequisites.\r
  *\r
- *  To use a LUFA build system module, simply add an include to your project makefile:\r
+ *  To use a LUFA build system module, simply add an include to your project makefile. All user projects\r
+ *  should at a minimum include \ref Page_BuildModule_CORE for base functionality:\r
  *  \code\r
  *  include $(LUFA_PATH)/Build/lufa_core.mk\r
  *  \endcode\r
  *\r
- *  And the associated build module targets will be added to your project's build makefile automatically.\r
- *  To call a build target, run <tt>make {TARGET_NAME}</tt> from the command line, substituting in\r
- *  the appropriate target name.\r
+ *  Once included in your project makefile, the associated build module targets will be added to your\r
+ *  project's build makefile targets automatically. To call a build target, run <tt>make {TARGET_NAME}</tt>\r
+ *  from the command line, substituting in the appropriate target name.\r
  *\r
  *  \see \ref Sec_AppConfigParams for a copy of the sample LUFA project makefile.\r
  *\r
@@ -49,7 +50,7 @@
  *\r
  *  The BUILD LUFA build system module, providing targets for the compilation,\r
  *  assembling and linking of an application from source code into binary files\r
- *  suitable for programming into a target device.\r
+ *  suitable for programming into a target device, using the GCC compiler.\r
  *\r
  *  To use this module in your application makefile, add the following code:\r
  *  \code\r
@@ -57,7 +58,7 @@
  *  \endcode\r
  *\r
  *  \section SSec_BuildModule_BUILD_Requirements Requirements\r
- *  This module requires the the architecture appropriate binaries of the GCC compiler are  available in your\r
+ *  This module requires the the architecture appropriate binaries of the GCC compiler are available in your\r
  *  system's <b>PATH</b> variable. The GCC compiler and associated toolchain is distributed in Atmel AVR Studio\r
  *  5.x and Atmel Studio 6.x installation directories, as well as in many third party distribution packages.\r
  *\r
@@ -381,7 +382,7 @@
  *  \section SSec_BuildModule_AVRDUDE_Requirements Requirements\r
  *  This module requires the <tt>avrdude</tt> utility to be available in your system's <b>PATH</b>\r
  *  variable. The <tt>avrdude</tt> utility is distributed in the old WinAVR project releases for\r
- *  Windows (<a>winavr.sourceforge.net</a>) or can be installed on *nix systems via the project's\r
+ *  Windows (<a>http://winavr.sourceforge.net</a>) or can be installed on *nix systems via the project's\r
  *  source code (<a>https://savannah.nongnu.org/projects/avrdude</a>) or through the package manager.\r
  *\r
  *  \section SSec_BuildModule_AVRDUDE_Targets Targets\r