summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--calendars.mdwn2
-rw-r--r--files.mdwn2
-rw-r--r--inboxes.mdwn2
-rw-r--r--projects-next-actions.mdwn2
4 files changed, 4 insertions, 4 deletions
diff --git a/calendars.mdwn b/calendars.mdwn
index df4f600..972837d 100644
--- a/calendars.mdwn
+++ b/calendars.mdwn
@@ -47,7 +47,7 @@ keep getting distracted by your computer so that it may take your a
month to notice that it's time to cut them. And when you do, it's
because you break a nail, which is a bit painful. After some experimentation
you decide that twelve days after the previous time is a good time to
-cut your nails. Having your computer remind you about it s makes it
+cut your nails. Having your computer remind you about it makes it
much more likely that you'll do it when it's time. However, having
your calendar remind you every twelve days may not work so well,
because you might be travelling on that 12th day, and the annoying
diff --git a/files.mdwn b/files.mdwn
index d8f0a4e..6559022 100644
--- a/files.mdwn
+++ b/files.mdwn
@@ -15,7 +15,7 @@ unless you can find things from it when you need them.
Files may be digital or on paper. You may have current files on your
computer, and on paper, and ditto for archived files. This might not
-affect the way you organize them: much of the organization is depdendent
+affect the way you organize them: much of the organization is dependent
on naming and sorting, and it is probably best to use the same naming
system for both digital and paper files.
diff --git a/inboxes.mdwn b/inboxes.mdwn
index c299290..4fa44ab 100644
--- a/inboxes.mdwn
+++ b/inboxes.mdwn
@@ -102,7 +102,7 @@ Hackers tend to deal with bug trackers, ticketing systems, and similar
systems. These are not purely inboxes. They're also sort of project
lists, and next actions lists. I have found it most efficient to use
them as places to trawl for inbox material. It's not possible to
-remove items from bug trackers just because you've decided what to
+remove items from bug trackers just because you've decided what to do
with them. Instead, I review the list of open bugs, and see if there's
anything there that's new or that I need to deal with. If there is, I
add a proxy into my own inbox (or, sometimes, directly as a next action).
diff --git a/projects-next-actions.mdwn b/projects-next-actions.mdwn
index da9a0d2..dd41dfe 100644
--- a/projects-next-actions.mdwn
+++ b/projects-next-actions.mdwn
@@ -99,7 +99,7 @@ what should you do? If it takes five minutes to scan the list and find
something to do, you've wasted maybe half of your available time. Not good.
You should break down the list by context or other suitable category.
-A context is the things that are reqwuired for you to do the action:
+A context is the things that are required for you to do the action:
"at phone" would be the context for anything that requires you to use
your phone; "online" would be all the things you need Internet access
to do; "at home" for things you must be at home to do, etc.