summaryrefslogtreecommitdiff
path: root/whatsnew-2.0.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-02-18 16:17:22 -0500
committerNick Mathewson <nickm@torproject.org>2011-02-18 16:17:22 -0500
commitdeb2f73879102b4a65df772972910f62e3a64649 (patch)
tree9adb4b35c400c023107d6a360f80b46d364c2fe1 /whatsnew-2.0.txt
parentf665924649b3d6306eb3c24df8f77c3671b7a082 (diff)
downloadlibevent-deb2f73879102b4a65df772972910f62e3a64649.tar.gz
fix spelling mistake in whatsnew-2.0.txt
Diffstat (limited to 'whatsnew-2.0.txt')
-rw-r--r--whatsnew-2.0.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/whatsnew-2.0.txt b/whatsnew-2.0.txt
index 3b4cfbdb..5ad6b979 100644
--- a/whatsnew-2.0.txt
+++ b/whatsnew-2.0.txt
@@ -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