Wording tweaks

1 files changed, 11 insertions, 11 deletions

diff --git a/waiting-for.mdwn b/waiting-for.mdwn
index f476302..e5af7ee 100644
--- a/waiting-for.mdwn
+++ b/waiting-for.mdwn
@@ -3,7 +3,7 @@ Waiting for things to happen
 
 After delegating something, you usually want to keep track of the issue
 to make sure it gets done. Minions are often lazy, and
-you don't want to be the kind of overlord who forgets orders he's given.
+you don't want to be the kind of overlord who forgets having given orders.
 So you need another list: a list of things you're waiting for to happen.
 
 This list is not just for delegations. It's also for other events you're
@@ -15,10 +15,9 @@ waiting for. For example:
   after it arrives, there's a bunch of things you'll need to do, or you'd
   like to do
 
-Lars uses a "waiting for" list of the following format:
+I use a "waiting for" list of the following format:
 
-    * End-of-year bonus arrives.
-      - since 2009-09-01
+    * End-of-year bonus arrives. 2009-09-01
       - then buy a new disco ball
       - then pay off credit card debt
 
@@ -32,12 +31,13 @@ they might be in the project list, and the project would be marked
 that there are blocked actions, so you'd at least need to write down
 pointers to the blocked projects.
 
-Lars also keeps another kind of "waiting for" list, for things that will
-need to be finished the same day. He calls this the "in progress" list.
-It usually contains things that automation is doing for him, but he needs
+I also keep another kind of "waiting for" list, for things that will
+need to be finished the same day. I call this the "in progress" list,
+and it's actually a context in my next actions list.
+It usually contains things that automation is doing for me, but that I need
 to remember to check up on when they're finished. For example:
 
-* a half-hour test run for some software he's writing (it's so easy to
+* a half-hour test run for some software I'm writing (it's so easy to
   start one, then lose the window under a dozen others, and only notice
   it a week later: this seriously slows down development speed)
 * Roomba is vacuuming in another room
@@ -46,9 +46,9 @@ to remember to check up on when they're finished. For example:
 * a co-worker is looking up some information and promised to have something
   by lunchtime
 
-The "in progress" list is otherwise like the "waiting for" one, but he
-keeps it at the top of the "next actions" list, so it's always in his
+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
 face. This makes it harder to forget stuff that is currently happening.
-The crucial difference, for Lars, is that "in progress" needs to be
+The crucial difference, for me, is that "in progress" needs to be
 finished the same day, whereas "waiting for" may usually wait until the
 next weekly review.