X-Git-Url: https://arthur.barton.de/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=libevent%2Fwhatsnew-2.0.txt;h=be0c71bc217eba9dabeccc4f0944bfb241430726;hb=refs%2Fheads%2Fv3.1.3-alex;hp=3b4cfbdb4cc1c95dca9aa10c70f0d016b952184d;hpb=85d268c10175d1e8050188a3a4797b40519a285e;p=netatalk.git

diff --git a/libevent/whatsnew-2.0.txt b/libevent/whatsnew-2.0.txt
index 3b4cfbdb..be0c71bc 100644
--- a/libevent/whatsnew-2.0.txt
+++ b/libevent/whatsnew-2.0.txt
@@ -24,7 +24,7 @@ What's New In Libevent 2.0 so far:
 
   COMPATIBILITY:
 
-  Nearly all existing code that worked with should Libevent 1.4 should still
+  Nearly all existing code that worked with Libevent 1.4 should still
   work correctly with Libevent 2.0.  However, if you are writing new code,
   or if you want to port old code, we strongly recommend using the new APIs
   and avoiding deprecated APIs as much as possible.
@@ -75,7 +75,7 @@ What's New In Libevent 2.0 so far:
   evutil.h) will continue to work by including the corresponding new
   headers.  Old code should not be broken by this change.
 
-2.2. New thread-safe, binary-compatibile, harder-to-mess-up APIs
+2.2. New thread-safe, binary-compatible, harder-to-mess-up APIs
 
   Some aspects of the historical Libevent API have encouraged
   non-threadsafe code, or forced code built against one version of Libevent