From af0dba2ab6beab036b3a2079c7e5166bb8ec15f4 Mon Sep 17 00:00:00 2001 From: sobrado Date: Tue, 8 Jul 2014 07:59:31 +0000 Subject: fix typos. ok jmc@ --- usr.sbin/smtpd/ioev.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'usr.sbin/smtpd/ioev.c') diff --git a/usr.sbin/smtpd/ioev.c b/usr.sbin/smtpd/ioev.c index c1d6736cb8b..802cd7098e4 100644 --- a/usr.sbin/smtpd/ioev.c +++ b/usr.sbin/smtpd/ioev.c @@ -1,4 +1,4 @@ -/* $OpenBSD: ioev.c,v 1.18 2014/04/19 17:36:54 gilles Exp $ */ +/* $OpenBSD: ioev.c,v 1.19 2014/07/08 07:59:31 sobrado Exp $ */ /* * Copyright (c) 2012 Eric Faurot * @@ -161,7 +161,7 @@ io_set_linger(int fd, int linger) /* * Event framing must not rely on an io pointer to refer to the "same" io - * throughout the frame, beacuse this is not always the case: + * throughout the frame, because this is not always the case: * * 1) enter(addr0) -> free(addr0) -> leave(addr0) = SEGV * 2) enter(addr0) -> free(addr0) -> malloc == addr0 -> leave(addr0) = BAD! @@ -203,7 +203,7 @@ io_frame_leave(struct io *io) * the response in the output buffer and goes to write mode. * There, the write event is set and will be triggered in the next * event frame. In most case, the write call could be done - * immediatly as part of the last read frame, thus avoiding to go + * immediately as part of the last read frame, thus avoiding to go * through the event loop machinery. So, as an optimisation, we * could detect that case here and force an event dispatching. */ -- cgit v1.2.3-59-g8ed1b