X-Git-Url: https://codewiz.org/gitweb?a=blobdiff_plain;f=README.bertos;h=65edccce173bdbd65b734aafc134564f61c7e98c;hb=225b5f86a6cac80cdafe0e3b1cc91f735c6b902e;hp=3bcec29baca14428580c20d5712dcebb5a05a0b2;hpb=d9d95af77b73deb9a3a923a2dbf4013602770ebd;p=bertos.git

diff --git a/README.bertos b/README.bertos
index 3bcec29b..65edccce 100644
--- a/README.bertos
+++ b/README.bertos
@@ -21,10 +21,11 @@ environments, from 8-bit processor to Linux and Win32 hosted application
 
 \section history History and Motivation
 
-BeRTOS was born as a collection of useful, highly optimized and fine-tuned
-libraries for embedded systems.  Each library had its own scope and could be
-used singularly in a project, though they were also meant to cooperate to
-build the whole underlying software layer commonly called "operating system".
+BeRTOS was born as a extremely modular, highly optimized and fine-tuned
+operating system for embedded programming.
+As a result, each module has its own scope and can be used alone or in
+cooperation with other modules.
+It's even possible to use most of the drivers without activating the kernel module.
 
 We have grown it following our guidelines: simplicity and beauty.
 These guidelines made it possible to evolve it in a full-featured real
@@ -33,7 +34,7 @@ without giving up reliability and performace.
 
 To achieve the highest possible reusability, most BeRTOS components are
 designed for fine-grained modularity and minimal external dependencies.
-Most non-essential features can be configured out for application with small
+Most non-essential features can be configured out for applications with small
 memory footprint requirements.
 
 \section features Features