diff options
| author | Eric Andersen <andersen@codepoet.org> | 2002-06-21 21:34:44 +0000 |
|---|---|---|
| committer | Eric Andersen <andersen@codepoet.org> | 2002-06-21 21:34:44 +0000 |
| commit | 84aea56a2b2f048282c89864c9ffdcc40905035e (patch) | |
| tree | 01c505b36c7a1ba0e389f3f209b5202119ac1cba | |
| parent | 28a540720b6db3302cb6a2af3173cb070e2fdcbb (diff) | |
Fix silly spelling error
| -rw-r--r-- | docs/uclibc.org/index.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/uclibc.org/index.html b/docs/uclibc.org/index.html index aec556b4b..b85b3f28d 100644 --- a/docs/uclibc.org/index.html +++ b/docs/uclibc.org/index.html @@ -39,7 +39,7 @@ <a href="http://www.uclibc.org">uClibc</a> (aka µClibc/pronounced yew-see-lib-see) is a C library for developing embedded Linux systems. -It is much smaller then the +It is much smaller than the <a href="http://www.gnu.org/software/libc/libc.html">GNU C Library</a>, but nearly all applications supported by glibc also work perfectly with uClibc. Porting applications from glibc to uClibc typically involves @@ -52,7 +52,7 @@ PowerPC, SH, SPARC, and v850 processors. If you are building an embedded Linux system and you find that glibc is eating up too much space, you should consider using uClibc. If you are -building a huge fileserver with 12 Terabytes of storage, then using +building a huge fileserver with 12 Terabytes of storage, than using glibc may be a better choice... <p> |