X-Git-Url: http://git.linex4red.de/pub/lufa.git/blobdiff_plain/071e02c6b6b4837fa9cf0b6d4c749994e02638d7..6005a42150bf4d713fd962498bde8b540fef4035:/LUFA/ManPages/LUFAvsAtmelStack.txt

diff --git a/LUFA/ManPages/LUFAvsAtmelStack.txt b/LUFA/ManPages/LUFAvsAtmelStack.txt
index 582bb9e0f..239c2772b 100644
--- a/LUFA/ManPages/LUFAvsAtmelStack.txt
+++ b/LUFA/ManPages/LUFAvsAtmelStack.txt
@@ -5,20 +5,20 @@
  */
 
 /**
- *  \page Page_LUFAvsAtmelStack LUFA vs the Atmel Stack
+ *  \page Page_LUFAvsAtmelStack LUFA vs the Atmel 8-bit USB AVR Stack
  *
- *  Atmel offers an official USB AVR stack, which may be incorporated into user projects and products. As LUFA and the Atmel
- *  stack aims to give roughly the same functionality to a design, it is often asked what advantages LUFA carries over the
- *  official Atmel USB stack. Below are just some of the advantages to choosing LUFA over the official stack.
+ *  Atmel offers an official 8-bit USB AVR stack, which may be incorporated into user projects and products. As LUFA and the Atmel
+ *  stack aims to give roughly the same functionality to a design, it is often asked what advantages LUFA carries over the official
+ *  Atmel USB stack for the 8-bit USB AVRs. Below are just some of the advantages to choosing LUFA over the official Atmel stack.
  *
  *  - <b>Licensing:</b>
- *    LUFA is released under a very permissive MIT license (see \ref Page_LicenceInfo), while the Atmel stack carries several
+ *    LUFA is released under a very permissive MIT license (see \ref Page_LicenseInfo), while the Atmel stack carries several
  *    restrictions as to how and where it can be used. LUFA's licensing should be suitable for both Commercial and Non-Commercial
  *    entities alike.
  *
  *  - <b>Demos and Projects:</b>
  *    Unlike the Atmel stack, LUFA comes with many different Device and Host mode Demos and Projects ready to run out of the box.
- *    Atmel favours separate downloads for each of their (small set) of USB AVR demos, which requires more time and offers less
+ *    Atmel favors separate downloads for each of their (small set) of USB AVR demos, which requires more time and offers less
  *    to the end-user. LUFA also contains several open source Bootloaders, which can be modified as the user wishes to suit his or
  *    her application, instead of being forced to use Atmel's single prebuilt (closed-source) DFU bootloader.
  *
@@ -30,7 +30,7 @@
  *
  *  - <b>Clean API:</b>
  *    One of the main design goals of LUFA is to make the API easy to use. While LUFA is a fluid project which has undergone many
- *    API improvements, the API is arguably much nicer to use and easier to understand than the equivelent Atmel stack code. LUFA's
+ *    API improvements, the API is arguably much nicer to use and easier to understand than the equivalent Atmel stack code. LUFA's
  *    API is also more complete than the Atmel stack, and contains many features to speed up application development.
  *
  *  - <b>Full Hardware Support:</b>
@@ -42,5 +42,11 @@
  *  - <b>Better Library Support:</b>
  *    As many people are now using LUFA, there is a community being built around it. You can get answers to your LUFA related questions
  *    quickly by either emailing the library author (subject to author's schedule) or by posting to the official LUFA support mailing list.
+ *
+ *  - <b>More Compact Code:</b>
+ *    LUFA is written from the ground up to compile optimally, using clean code and good design. Two demos giving the same functionality -
+ *    the LUFA Low Level API Mouse Demo vs. the Atmel AVR270 HID Mouse application note shows LUFA to be the clear size winner *.
+ *
+ *  * <i>LUFA Low Level Mouse Demo: 3510 bytes, Atmel AVR270 Mouse Application Note: 4222 bytes, using an identical build environment.</i>
  */
- 
\ No newline at end of file
+