From: Nick Mathewson <nickm@torproject.org>
Date: Fri, 20 Dec 2013 18:31:29 +0000 (-0500)
Subject: Typo fixes from Linus Nordberg
X-Git-Tag: release-2.0.22-stable~19^2
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=cec62cb80a689f84470f8424ed70d39e8854f981;p=libevent

Typo fixes from Linus Nordberg
---

diff --git a/include/event2/bufferevent.h b/include/event2/bufferevent.h
index 7ce4e8f8..0cc6cb1c 100644
--- a/include/event2/bufferevent.h
+++ b/include/event2/bufferevent.h
@@ -44,10 +44,10 @@
   with bufferevent_enable() and bufferevent_disable().
 
   When reading is enabled, the bufferevent will try to read from the
-  file descriptor onto its input buffer, and and call the read callback.
+  file descriptor onto its input buffer, and call the read callback.
   When writing is enabled, the bufferevent will try to write data onto its
-  file descriptor when writing is enabled, and call the write callback
-  when the output buffer is sufficiently drained.
+  file descriptor when the output buffer has enough data, and call the write
+  callback when the output buffer is sufficiently drained.
 
   Bufferevents come in several flavors, including:
 
diff --git a/include/event2/event.h b/include/event2/event.h
index 700e8ca1..1da95560 100644
--- a/include/event2/event.h
+++ b/include/event2/event.h
@@ -646,7 +646,7 @@ int event_base_set(struct event_base *, struct event *);
 
   By default, this loop will run the event base until either there are no more
   added events, or until something calls event_base_loopbreak() or
-  evenet_base_loopexit().  You can override this behavior with the 'flags'
+  event_base_loopexit().  You can override this behavior with the 'flags'
   argument.
 
   @param eb the event_base structure returned by event_base_new() or