summaryrefslogtreecommitdiff
path: root/doing.mdwn
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2012-04-09 20:36:43 +0100
committerLars Wirzenius <liw@liw.fi>2012-04-09 20:36:43 +0100
commit29b0268a9bf0d0ddf520b817eb46c8e93fc063d7 (patch)
treeae90a8f7b2799d2542c1985310fa3b089f868272 /doing.mdwn
parentbf94a47c43d1e748eccb2b7345cb5c859450b434 (diff)
downloadgtdfh.liw.fi-29b0268a9bf0d0ddf520b817eb46c8e93fc063d7.tar.gz
Fix typo
Thanks to Mark.
Diffstat (limited to 'doing.mdwn')
-rw-r--r--doing.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/doing.mdwn b/doing.mdwn
index 3e836bd..eed88dd 100644
--- a/doing.mdwn
+++ b/doing.mdwn
@@ -15,7 +15,7 @@ Sometimes the problem is that the next action is defined vaguely:
it's not actually clear what you need to do. Perhaps it was clear
when you were planning it, but you didn't write down enough details
to remember later why you need to do it, or exactly what needs doing.
-"Call Clara's cell" may what you wrote down, but you can't remember
+"Call Clara's cell" may be what you wrote down, but you can't remember
which Clara, and whether to call her mobile phone or the jail? You
need to describe next actions with enough information that you don't
have uncertainty.