From 107933674452a37a746c507aec45d3c053dcde0f Mon Sep 17 00:00:00 2001
From: root <root>
Date: Tue, 6 Nov 2007 19:45:29 +0000
Subject: *** empty log message ***

---
 README.embed | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/README.embed b/README.embed
index 0ab2878..caf1145 100644
--- a/README.embed
+++ b/README.embed
@@ -8,6 +8,8 @@ EMBEDDING THE LIBEV CODE INTO YOUR OWN PROGRAMS
 
 FILESETS
 
+    CORE EVENT LOOP
+
     To include only the libev core (all the ev_* functions):
 
         #define EV_STANDALONE   1
@@ -36,6 +38,8 @@ FILESETS
 
     "ev.c" includes the backend files directly when enabled.
 
+    LIBEVENT COMPATIBILITY API
+
     To include the libevent compatibility API, also include:
 
         #include "event.c"
@@ -144,7 +148,7 @@ EXAMPLES
     For a real-world example of a program the includes libev
     verbatim, you can have a look at the EV perl module
     (http://software.schmorp.de/pkg/EV.html).  It has the libev files in
-    the liev/ subdirectory and includes them in the EV/EVAPI.h (public
-    interface) and EV.xs (implementation) files. Only EV.xs file will be
-    compiled.
+    the libev/ subdirectory and includes them in the EV/EVAPI.h (public
+    interface) and EV.xs (implementation) files. Only the EV.xs file will
+    be compiled.
 
-- 
cgit v1.2.3