[uClibc-cvs] uClibc/docs/uclibc.org FAQ.html, 1.15, 1.16 index.html, 1.68, 1.69

[Erik Andersen]

Update of /var/cvs/uClibc/docs/uclibc.org
In directory winder:/tmp/cvs-serv31560/docs/uclibc.org

Modified Files:
	FAQ.html index.html 
Log Message:
Yet more trivial doc updates


Index: index.html
===================================================================
RCS file: /var/cvs/uClibc/docs/uclibc.org/index.html,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -d -r1.68 -r1.69
--- index.html	9 Sep 2003 09:07:10 -0000	1.68
+++ index.html	9 Sep 2003 10:02:31 -0000	1.69
@@ -47,14 +47,17 @@
 just recompiling the source code. uClibc even supports shared libraries
 and threading.  It currently runs on <a href="http://kernel.org/">standard Linux</a> 
 and <a href="http://www.uclinux.org">MMU-less (also known as µClinux)</a>
-systems with support for alpha, ARM, i386, i960, h8300, m68k, mips/mipsel, 
+systems with support for alpha, ARM, cris, i386, i960, h8300, m68k, mips/mipsel, 
 PowerPC, SH, SPARC, and v850 processors.
 <p>
 
-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, than using
-glibc may be a better choice...
+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 glibc may make more sense.  Unless, for
+example, that 12 Terabytes will be Network Attached Storage and
+you plan to burn Linux into the system's firmware...
+
 <p>
 
 uClibc is maintained by 

Index: FAQ.html
===================================================================
RCS file: /var/cvs/uClibc/docs/uclibc.org/FAQ.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -d -r1.15 -r1.16
--- FAQ.html	7 Sep 2003 05:30:52 -0000	1.15
+++ FAQ.html	9 Sep 2003 10:02:30 -0000	1.16
@@ -53,8 +53,8 @@
 </TD></TR>
 <TR><TD BGCOLOR="#eeeee0">
 
-    Currently uClibc runs on alpha, ARM, i386, i960, h8300, m68k, mips/mipsel,
-    PowerPC, SH, SPARC, and v850 processors.
+    Currently uClibc runs on alpha, ARM, cris, h8300, i386, i960, m68k,
+    mips/mipsel, PowerPC, SH, SPARC, and v850 processors.
     
 
 <p>
@@ -166,10 +166,12 @@
 
     <p>
 
-    If you are trying to build a huge fileserver for your company that will
-    have 12 Terabytes of storage, then using glibc may make more sense.  
-    Unless, for example, that 12 Terabytes will be Network Attached Storage 
-    and you plan to burn Linux into the system's firmware...
+    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 glibc may make more sense.  Unless, for
+    example, that 12 Terabytes will be Network Attached Storage and
+    you plan to burn Linux into the system's firmware...