svn commit: trunk/uClibc/extra/Configs

[aldot at uclibc.org]

Author: aldot
Date: 2007-09-20 05:07:10 -0700 (Thu, 20 Sep 2007)
New Revision: 19909

Log:
- spelling fix


Modified:
   trunk/uClibc/extra/Configs/Config.in


Changeset:
Modified: trunk/uClibc/extra/Configs/Config.in
===================================================================
--- trunk/uClibc/extra/Configs/Config.in	2007-09-20 11:38:19 UTC (rev 19908)
+++ trunk/uClibc/extra/Configs/Config.in	2007-09-20 12:07:10 UTC (rev 19909)
@@ -423,7 +423,7 @@
 	help
 	  The behavior of malloc(0) is listed as implementation-defined by
 	  SuSv3.  Glibc returns a valid pointer to something, while uClibc
-	  normally return a NULL.  I personally feel glibc's behavior is
+	  normally returns NULL.  I personally feel glibc's behavior is
 	  not particularly safe, and allows buggy applications to hide very
 	  serious problems.
 
@@ -431,7 +431,7 @@
 	  return a live pointer when someone calls malloc(0).  This pointer
 	  provides a malloc'ed area with a size of 1 byte.  This feature is
 	  mostly useful when dealing with applications using autoconf's broken
-	  AC_FUNC_MALLOC macro (which  redefines malloc as rpl_malloc if it
+	  AC_FUNC_MALLOC macro (which redefines malloc as rpl_malloc if it
 	  does not detect glibc style returning-a-valid-pointer-for-malloc(0)
 	  behavior).  Most people can safely answer N.