summaryrefslogtreecommitdiff
path: root/waiting-for.mdwn
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2012-04-09 09:11:36 +0100
committerLars Wirzenius <liw@liw.fi>2012-04-09 09:11:36 +0100
commit567df61de1124b13a14c00a6f88d6fe13a1619cf (patch)
tree267bf0345ccaa104cb42d2b7c0b3effd8f1e4a77 /waiting-for.mdwn
parentbf0d0cd35676f56d6fb7f6c2ef5e76b901dedeee (diff)
downloadgtdfh.liw.fi-567df61de1124b13a14c00a6f88d6fe13a1619cf.tar.gz
Typo fix
Thanks, anonymous commenter.
Diffstat (limited to 'waiting-for.mdwn')
-rw-r--r--waiting-for.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/waiting-for.mdwn b/waiting-for.mdwn
index e5af7ee..d292f84 100644
--- a/waiting-for.mdwn
+++ b/waiting-for.mdwn
@@ -47,7 +47,7 @@ to remember to check up on when they're finished. For example:
by lunchtime
The "in progress" list is otherwise like the "waiting for" one, but I
-keeps it at the top of the "next actions" list, so it's always in my
+keep it at the top of the "next actions" list, so it's always in my
face. This makes it harder to forget stuff that is currently happening.
The crucial difference, for me, is that "in progress" needs to be
finished the same day, whereas "waiting for" may usually wait until the