[BusyBox-cvs] busybox README,1.32,1.33

[Erik Andersen]

Update of /var/cvs/busybox
In directory nail:/tmp/cvs-serv19182

Modified Files:
	README 
Log Message:
Yet more doc updates


Index: README
===================================================================
RCS file: /var/cvs/busybox/README,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -d -r1.32 -r1.33
--- a/README	27 Mar 2004 09:40:15 -0000	1.32
+++ b/README	6 Apr 2004 15:39:19 -0000	1.33
@@ -5,17 +5,18 @@
 you usually find in GNU coreutils, util-linux, etc. The utilities in BusyBox
 generally have fewer options than their full-featured GNU cousins; however, the
 options that are included provide the expected functionality and behave very
-much like their GNU counterparts. BusyBox provides a fairly complete POSIX
-environment for any small or embedded system.
+much like their GNU counterparts.
 
 BusyBox has been written with size-optimization and limited resources in mind.
 It is also extremely modular so you can easily include or exclude commands (or
 features) at compile time. This makes it easy to customize your embedded
 systems. To create a working system, just add /dev, /etc, and a Linux kernel.
+BusyBox provides a fairly complete POSIX environment for any small or embedded
+system.
 
 BusyBox is extremely configurable.  This allows you to include only the
 components you need, thereby reducing binary size. Run 'make config' or
-'make menuconfig' for select the functionality that you wish to enable.
+'make menuconfig' to select the functionality that you wish to enable.
 
 After the build is complete, a busybox.links file is generated.  This is
 used by 'make install' to create symlinks to the BusyBox binary for all