From f24b28e4aff1dbc3440e283f70ac15aa7cebcc8d Mon Sep 17 00:00:00 2001 From: Dmitry Alimov Date: Mon, 15 Jan 2018 17:30:08 +0300 Subject: [PATCH] Fix typos in comments --- include/event2/event.h | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/include/event2/event.h b/include/event2/event.h index 2ad2ec83..af56c9ed 100644 --- a/include/event2/event.h +++ b/include/event2/event.h @@ -1029,7 +1029,7 @@ EVENT2_EXPORT_SYMBOL void *event_self_cbarg(void); /** - Allocate and asssign a new event structure, ready to be added. + Allocate and assign a new event structure, ready to be added. The function event_new() returns a new event that can be used in future calls to event_add() and event_del(). The fd and events @@ -1055,10 +1055,10 @@ void *event_self_cbarg(void); The EV_TIMEOUT flag has no effect here. It is okay to have multiple events all listening on the same fds; but - they must either all be edge-triggered, or all not be edge triggerd. + they must either all be edge-triggered, or all not be edge triggered. When the event becomes active, the event loop will run the provided - callbuck function, with three arguments. The first will be the provided + callback function, with three arguments. The first will be the provided fd value. The second will be a bitfield of the events that triggered: EV_READ, EV_WRITE, or EV_SIGNAL. Here the EV_TIMEOUT flag indicates that a timeout occurred, and EV_ET indicates that an edge-triggered @@ -1163,13 +1163,13 @@ typedef void (*event_finalize_callback_fn)(struct event *, void *); event_finalize() does not. A finalizer callback must not make events pending or active. It must not - add events, activate events, or attempt to "resucitate" the event being + add events, activate events, or attempt to "resuscitate" the event being finalized in any way. THIS IS AN EXPERIMENTAL API. IT MIGHT CHANGE BEFORE THE LIBEVENT 2.1 SERIES BECOMES STABLE. - @return 0 on succes, -1 on failure. + @return 0 on success, -1 on failure. */ /**@{*/ EVENT2_EXPORT_SYMBOL @@ -1199,7 +1199,7 @@ int event_free_finalize(unsigned, struct event *, event_finalize_callback_fn); @param arg an argument to be passed to the callback function @param timeout the maximum amount of time to wait for the event. NULL makes an EV_READ/EV_WRITE event make forever; NULL makes an - EV_TIMEOUT event succees immediately. + EV_TIMEOUT event success immediately. @return 0 if successful, or -1 if an error occurred */ EVENT2_EXPORT_SYMBOL @@ -1210,7 +1210,7 @@ int event_base_once(struct event_base *, evutil_socket_t, short, event_callback_ The function event_add() schedules the execution of the event 'ev' when the condition specified by event_assign() or event_new() occurs, or when the time - specified in timeout has elapesed. If atimeout is NULL, no timeout + specified in timeout has elapsed. If a timeout is NULL, no timeout occurs and the function will only be called if a matching event occurs. The event in the ev argument must be already initialized by event_assign() or event_new() @@ -1236,7 +1236,7 @@ int event_add(struct event *ev, const struct timeval *timeout); leaves the event otherwise pending. @param ev an event struct initialized via event_assign() or event_new() - @return 0 on success, or -1 if an error occurrect. + @return 0 on success, or -1 if an error occurred. */ EVENT2_EXPORT_SYMBOL int event_remove_timer(struct event *ev); @@ -1531,7 +1531,7 @@ const struct timeval *event_base_init_common_timeout(struct event_base *base, Note also that if you are going to call this function, you should do so before any call to any Libevent function that does allocation. - Otherwise, those funtions will allocate their memory using malloc(), but + Otherwise, those functions will allocate their memory using malloc(), but then later free it using your provided free_fn. @param malloc_fn A replacement for malloc. @@ -1627,7 +1627,7 @@ int event_base_foreach_event(struct event_base *base, event_base_foreach_event_c cached time. Generally, this value will only be cached while actually - processing event callbacks, and may be very inaccuate if your + processing event callbacks, and may be very inaccurate if your callbacks take a long time to execute. Returns 0 on success, negative on failure. -- 2.40.0