Rename architecture specific driver files, to make them appear with uniquely identify...

[pub/lufa.git] / LUFA / ManPages / LUFAvsAtmelStack.txt

diff --git a/LUFA/ManPages/LUFAvsAtmelStack.txt b/LUFA/ManPages/LUFAvsAtmelStack.txt
index 99e2dc3..b4fce2d 100644 (file)
--- a/LUFA/ManPages/LUFAvsAtmelStack.txt
+++ b/LUFA/ManPages/LUFAvsAtmelStack.txt
@@ -12,13 +12,13 @@
  *  official Atmel USB stack. Below are just some of the advantages to choosing LUFA over the official 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.
  *
@@ -43,4 +43,4 @@
  *    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.
  */
- 
+