Update changelog

[oweals/busybox.git] / README

diff --git a/README b/README
index 631d4c15bc931fc2f4afc3f7d3f53b8278a08323..aa58cd1b98346a540baed17527ab5e61271718c4 100644 (file)
--- a/README
+++ b/README
@@ -5,17 +5,18 @@ small executable. It provides minimalist replacements for most of the utilities
 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
@@ -47,8 +48,8 @@ Supported kernels:
    Full functionality requires Linux 2.2.x or better.  A large fraction of the
    code should run on just about anything.  While the current code is fairly
    Linux specific, it should be fairly easy to port the majority of the code
-   to, say, FreeBSD or Solaris, or MacOsX, or even Windows (if you are into that
-   sortof thing).
+   to, say, FreeBSD or Solaris, or Mac OS X, or even Windows (if you are into
+   that sort of thing).
 
 ----------------