Typo fixes to ChangeLogs and ReleaseNotes

3 files changed, 18 insertions, 17 deletions

diff --git a/misc/buildroot/ChangeLog b/misc/buildroot/ChangeLog
index 6c9d71ae1..57396b639 100644
--- a/misc/buildroot/ChangeLog
+++ b/misc/buildroot/ChangeLog
@@ -143,11 +143,11 @@ buildroot-1.13 2014-01-29 <gnutt@nuttx.org>
 
 buildroot-1.14 2014-03-15 <gnutt@nuttx.org>
 
-	* Support for the GCC 4.7.3 compiler from David Alession (2014-2-18)
+	* Support for the GCC 4.7.3 compiler from David Alessio (2014-2-18)
 	* Support for the Cortex-M4F (with hardware floating point).  Also from
 	  David Alessio (2014-2-18).
 	* Added a Cortex-M3 GCC 4.8.2 EABI configuration (2014-2-27).
-	* toolchain/nxflat/ldnxflat.c and mknxflat.c:  Fix error with binutils-2.4:
+	* toolchain/nxflat/ldnxflat.c and mknxflat.c:  Fix error with binutils-2.24:
 	  bfd.h wants us to include config.h first (2014-2.27).
 	* Added support for the kconfig-frontends-3.12.0.0 tools.
 
diff --git a/misc/buildroot/ReleaseNotes b/misc/buildroot/ReleaseNotes
index 10eab477a..dce79d50b 100644
--- a/misc/buildroot/ReleaseNotes
+++ b/misc/buildroot/ReleaseNotes
@@ -8,30 +8,30 @@ This is a highly hacked up version of the buildroot (see
 http://buildroot.uclibc.org/). It has been hacked so that it
 can be used to build the following NuttX-compatible toolchains:
 
-  o arm-elf toolchain needed for use with the TI C5471 (ARM7TDMI),
+  o arm-nuttx-elf toolchain needed for use with the TI C5471 (ARM7TDMI),
     NXP LPC214x (ARM7TMDI), STMicro STR71x (ARM7TDMI), Freescale
     i.MX1 (ARM920T), and TI DM320 (ARM926EJ-S) provided with the
     NuttX releases.
 
     NXFLAT toolchain for use with the ARM7 and ARM9.
 
-  o arm-eabi ARM Cortex-M0 toolchain needed for use with
+  o arm-nuttx-eabi ARM Cortex-M0 toolchain needed for use with
     the NUC120 and Freescale KL ports provided with the NuttX releases.
 
-  o arm-elf and arm-eabi ARM Cortex-M3/4 (thumb2) toolchain needed
+  o arm-nuttx-elf and arm-nuttx-eabi ARM Cortex-M3/4 (thumb2) toolchain needed
     for use with the Freescale Kinetis and KL, TI Tiva/Stellaris LM3S, LM4F,
     and TM4C, NXP LPC17xx, NXP LPC43xx, Atmel SAM3/4, and STMicro STM32 F1,
     F2, F3 and F4 ports  provided with the NuttX releases.
 
     NXFLAT toolchain for use with the ARM Cortex-M3/4.
 
-  o arm-eabi ARM Cortex-M4F (thumb2) toolchain needed for use with the
+  o arm-nuttx-eabi ARM Cortex-M4F (thumb2) toolchain needed for use with the
     Tiva/Stellaris LM4F, and TM4C, NXP LPC43xx, Atmel SAM3/4, and STMicro
     STM32 F3 and F3 ports provided with the NuttX releases.
 
     NXFLAT toolchain for use with the ARM Cortex-M4F.
 
-  o arm-elf and arm-eabi ARM Cortex-A5/A8 toolchain needed
+  o arm-nuttx-elf and arm-nuttx-eabi ARM Cortex-A5/A8 toolchain needed
     for use with the Atmel SAMA5D3x and Allwinner A10 ports provided
     with the NuttX releases.
 
@@ -77,8 +77,9 @@ Supported tool versions include:
   o gcc-3.4.6 + binutils-2.17
   o gcc-4.2.4 + binutils-2.19
   o gcc-4.3.3 + binutils-2.19.1
-  o gcc-4.5.2 + binutils-2.21
+  o gcc-4.5.2 + binutils-2.21/2.21.1
   o gcc-4.6.3 + binutils-2.22
+  o gcc-4.7.3 + binutils-2.24
   o gcc-4.8.2 + binutils-2.24
 
 See the ChangeLog of features/architectures added in v1.13.
diff --git a/nuttx/ReleaseNotes b/nuttx/ReleaseNotes
index d07357b88..be8747902 100644
--- a/nuttx/ReleaseNotes
+++ b/nuttx/ReleaseNotes
@@ -5868,7 +5868,7 @@ Additional new features and extended functionality:
       - As mentioned above, the per-thread CPU load information is now
         reported in the procfs under <pid>/loadavg.
       - Many file system interfaces have been extended to operate on the
-        top-level NuttX pseudo filestem.  These include rmdir, mkdir,
+        top-level NuttX pseudo filesystem.  These include rmdir, mkdir,
         rename, and unlink.  This capability can be disabled with
         CONFIG_DISABLE_PSEUDOFS_OPERATIONS in order to keep the footprint
         small.
@@ -5924,7 +5924,7 @@ Additional new features and extended functionality:
 
       - Added architecture support for the TI Tiva TM4C123G parts.  This was
         merged into the existing support for the LM3S and LM4F families. 
-        All directory, file, and function references changed from m to tiva.
+        All directory, file, and function references changed from lm to tiva.
 
     * TI Tiva TMC4C123G Board Support:
 
@@ -5934,8 +5934,8 @@ Additional new features and extended functionality:
 
     * STMicro STM32 Boards:
 
-      - configs/mikroe-stm32f4/src/up_mio283qt9a.c: The Mikroe STM32F4 can
-        now support the newer MIO283QT9A LCD. From Toby Duckworth.
+      - The Mikroe STM32F4 can now support the newer MIO283QT9A LCD. From
+        Toby Duckworth.
       - Miscellaneous changes to better support FPU on STM32F429 Discovery
         from David Alessio.
 
@@ -5977,7 +5977,7 @@ Additional new features and extended functionality:
       - NSH can now use an EMACS-like command line editor.  This CLE, is
         really more like the traditional readline than is the default, tiny
         the NuttX readline .
-      - The touscreen example can now be configured to work with either a
+      - The touchscreen example can now be configured to work with either a
         touchscreen or a mouse device.
       - Several NSH commands can now be used to operate on objects in the
         top-level pseudo-filesystem: rmdir, mkdir, mv, and rm.  This
@@ -6012,12 +6012,12 @@ Bugfixes (see the ChangeLog for details).  Some of these are very important:
 
       - Fix one place where the connection reference count was not being
         decremented in the socket close() logic.  This is really a cosmetic
-        change BUT when CONFIG_DEBUG_NET is enable, it will cause assertions.
+        change BUT when CONFIG_DEBUG_NET is enabled, it will cause assertions.
       - Backed out a small part of the NuttX 6.33 write buffering changed. 
         David G says that this causes problems in connecting to a server.
-      - In DHCPD, there was a place where the logic called should not call
-        ntohl() inappropriately; the address was already in the correct
-        order.  How could DHCPD have worked with this bug?
+      - In DHCPD, there was a place where the logic was calling ntohl()
+        inappropriately; the address was already in the correct order.  How
+        could DHCPD have worked with this bug?
 
     * TI Tiva/Stellaris Drivers: