diff --git a/legacy/ecore/README.in b/legacy/ecore/README.in
index 2567738d3c..58e2c48cdb 100644
--- a/legacy/ecore/README.in
+++ b/legacy/ecore/README.in
@@ -13,10 +13,32 @@ Recommended:
 Optional:
   XCB SDL DirectFB
 
-Ecore is the event/X abstraction layer that makes doing selections,
-Xdnd, general X stuff, event loops, timeouts and idle handlers fast,
-optimized, and convenient. It's a separate library so anyone can make
-use of the work put into Ecore to make this job easy for applications.
+Ecore is a clean and tiny event loop library with many modules to do
+lots of convenient things for a programmer, to save time and effort.
+
+It's small and lean, designed to work on embedded systems all the way
+to large and powerful multi-cpu workstations. It serialises all system
+signals, events etc. into a single event queue, that is easily
+processed without needing to worry about concurrency. A properly
+written, event-driven program using this kind of programming doesn't
+need threads, nor has to worry about concurrency. It turns a program
+into a state machine, and makes it very robust and easy to follow.
+
+Ecore gives you other handy primitives, such as timers to tick over
+for you and call specified functions at particular times so the
+programmer can use this to do things, like animate, or time out on
+connections or tasks that take too long etc.
+
+Idle handlers are provided too, as well as calls on entering an idle
+state (often a very good time to update the state of the program). All
+events that enter the system are passed to specific callback functions
+that the program sets up to handle those events. Handling them is
+simple and other Ecore modules produce more events on the queue,
+coming from other sources such as file descriptors etc.
+
+Ecore also lets you have functions called when file descriptors become
+active for reading or writing, allowing for streamlined, non-blocking
+IO.
 
 ------------------------------------------------------------------------------
 COMPILING AND INSTALLING: