summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2012-04-17 23:05:04 +0100
committerLars Wirzenius <liw@liw.fi>2012-04-17 23:05:04 +0100
commit6ac6a5bd1e197ee3792df20a6a98e36cf4efdb7e (patch)
tree71b21462761eed87b2e69d39492f2a32e8f13df9
parentdb1db627c74087bdcbbeae31fa922b3b5d41d1a7 (diff)
downloadgtdfh.liw.fi-6ac6a5bd1e197ee3792df20a6a98e36cf4efdb7e.tar.gz
Fixes from Kristina Hoeppner
-rw-r--r--calendars.mdwn2
-rw-r--r--files.mdwn4
-rw-r--r--getting-started.mdwn2
-rw-r--r--inboxes.mdwn11
-rw-r--r--introduction.mdwn2
-rw-r--r--projects-next-actions.mdwn2
-rw-r--r--quickie-overview.mdwn18
-rw-r--r--review.mdwn4
-rw-r--r--ungood.mdwn2
9 files changed, 23 insertions, 24 deletions
diff --git a/calendars.mdwn b/calendars.mdwn
index 972837d..b9d2e88 100644
--- a/calendars.mdwn
+++ b/calendars.mdwn
@@ -43,7 +43,7 @@ sent out the invitation, and not remind you if you have.
Some stuff does not fit so easily with calendars. For example,
suppose you want to cut your nails when they get too long, but you
-keep getting distracted by your computer so that it may take your a
+keep getting distracted by your computer so that it may take you 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
diff --git a/files.mdwn b/files.mdwn
index 6559022..15a6ab0 100644
--- a/files.mdwn
+++ b/files.mdwn
@@ -19,7 +19,7 @@ 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.
-You may need have things other than documents you need to keep track
+You may have other things than documents you need to keep track
of for some of your projects. For example, one of your projects might
be to move some artwork to a different country, and the artwork would
then be part of your current files. Since large paintings are hard
@@ -45,7 +45,7 @@ have very specific folders (envelopes, tabs in ring binders, whatever).
Each folder should have very specific kinds of items in it. Thus,
a folder named "Edinburgh council tax, 2011" would be better than
"Financial stuff". The former is very specific, the latter would
-quickly grow to be unhelpfully large very quick.
+quickly grow to be unhelpfully large.
Every folder should be labelled clearly. People with a lousy
handwriting font might want to invest in a label writer of some
diff --git a/getting-started.mdwn b/getting-started.mdwn
index 5fc5cd2..ceea9f9 100644
--- a/getting-started.mdwn
+++ b/getting-started.mdwn
@@ -42,7 +42,7 @@ After I'd cleared the table, I did the same thing with my computers. I
collected all my files and e-mails and bookmarks and so on into one
digital inbox per computer, and then processed those. I still kept all
my lists on paper, though. As it turned out, my digital life was in much
-better order so there was rather less next actions and projects generated
+better order so there were rather fewer next actions and projects generated
from that.
By Sunday evening all my inboxes were clear, and my lists were long.
diff --git a/inboxes.mdwn b/inboxes.mdwn
index 15941a5..caca35a 100644
--- a/inboxes.mdwn
+++ b/inboxes.mdwn
@@ -11,7 +11,7 @@ Each such folder would be a separate inbox.
A common anti-pattern for people is to keep e-mail in their inboxes.
They read it, and leave it there. The next time they read e-mail, there
-might be some more new mail, which they read, and leave there. Eventually,
+might be some new mail, which they read, and leave there. Eventually,
the mail piles up a lot, and it gets hard to find a specific mail you
may need. Even more importantly, it gets hard to know which mails still
require you to do something. Perhaps there was a mail from your boss
@@ -54,8 +54,7 @@ action, and any mails that do require action are easy to find.
This will make you be much more relaxed about your e-mail. You never need
to worry whether you've replied to everything that needs replying. A further
-benefit, also of great benefit, is that you're likely to reply to mail
-much faster than before.
+benefit is that you're likely to reply to mail much faster than before.
Other kinds of inputs
------
@@ -138,7 +137,7 @@ Inboxes a la Lars
Here are the inboxes I use:
* physical inbox: letters and other mail, notes written on paper, etc.
-* wallet: receipts, other bits and pieces that gets collected during the day
+* wallet: receipts, other bits and pieces that get collected during the day
* notebooks: notes made while out and about and phone/laptop wasn't available
* backpack: random stuff tends to get collected there
* phone text messages
@@ -146,8 +145,8 @@ Here are the inboxes I use:
* phone notebook: I use a note taking application on my smartphone as
a replacement for a notebook, when I can, because my handwriting font
is abysmally hard to read
-* e-mail: these two inboxes (personal vs work); I don't split mailing list
- into separate folders anymore
+* e-mail: this is two inboxes (personal vs work); I no longer have a separate
+ folder for each mailing list, everything goes into the same inbox
* feeds: blogs, news sites, etc.
* home directory for each computer I regularly use: tends to collect
random downloaded files, notes, etc.
diff --git a/introduction.mdwn b/introduction.mdwn
index 44c6111..033563c 100644
--- a/introduction.mdwn
+++ b/introduction.mdwn
@@ -22,7 +22,7 @@ a different view of, and perhaps opinion of, the GTD system.
I discuss what has been good about GTD for me, what has been hard
to implement, and what has not worked. My goal is to explain what
-I do, and provide inspiration to you for building their own
+I do, and provide inspiration to you for building your own
GTD system.
GTD is not a system you buy in a shop and install on your desk. It is
diff --git a/projects-next-actions.mdwn b/projects-next-actions.mdwn
index a6e5826..a821ed8 100644
--- a/projects-next-actions.mdwn
+++ b/projects-next-actions.mdwn
@@ -20,7 +20,7 @@ fulfill the following criteria:
* a _physical_ action ("write", not "think about")
* thinking is part of planning! and that should happend during review phase
* planning can be broken down into next actions, however
-* it's clear what I need to (a widget to crank)
+* it's clear what I need to do (a widget to crank)
* duration at most 15 minutes, preferably
* I'm committed to doing it
* does not depend on anything, can be done immediately
diff --git a/quickie-overview.mdwn b/quickie-overview.mdwn
index 119f473..6625dfd 100644
--- a/quickie-overview.mdwn
+++ b/quickie-overview.mdwn
@@ -11,16 +11,16 @@ A condensed summary of GTD:
in one or more inboxes
* you empty your inboxes regularly from stuff
* stuff is dealt with by one of the following:
- - do it at once (if it's quick, or you have to, or really want to)
- - defer it for later
- - delegate it to someone else
- - file it somewhere (if you may need it later)
- - discard it (ignore it, throw it in a trash bin, whatever)
+ **do it at once** (if it's quick, or you have to, or really want to);
+ **defer** it for later;
+ **delegate** it to someone else;
+ **file** it somewhere (if you may need it later);
+ **discard** it (ignore it, throw it in a trash bin, whatever)
* keep several lists:
- - next actions: deferred stuff
- - projects: anything that needs more than one next action to be finished
- - waiting for: delegated stuff
- - someday/maybe: what you may want to do someday, but isn't an active
+ **next actions**: deferred stuff;
+ **projects**: anything that needs more than one next action to be finished;
+ **waiting for**: delegated stuff;
+ **someday/maybe**: what you may want to do someday, but isn't an active
concern right now
* at least once a week, process all inboxes, and review all lists
* have an archiving system for documents and such
diff --git a/review.mdwn b/review.mdwn
index 69148ee..8ce3188 100644
--- a/review.mdwn
+++ b/review.mdwn
@@ -71,12 +71,12 @@ another problem.)
Other reviews
-------------
-In addition to the weekly review, it is good to another kind of review
+In addition to the weekly review, it is good to have another kind of review
about once or twice a year. For this, I find it's best to do a weekly
review first, and then concentrate on bigger issues: what do I want
out of life? How do I want to live in one year, five years, twenty years,
or in my retirement? What do I need to do to achieve those things?
-I've not done much of that yet, so I dont have a lot of concrete advice
+I've not done much of that yet, so I don't have a lot of concrete advice
about that. I'll add more about it when I do.
diff --git a/ungood.mdwn b/ungood.mdwn
index 2c6de7f..9d136e2 100644
--- a/ungood.mdwn
+++ b/ungood.mdwn
@@ -9,7 +9,7 @@ Split systems: personal versus work GTD
---------------------------------------
I've tried having a separate GTD system for work and personal lives,
-but as a free software develper, the two are mixed enough that it's
+but as a free software developer, the two are mixed enough that it's
annoying to keep the two systems in sync. For example, if I find a
bug in Debian, while doing work, should reporting it and maybe fixing
it be a work-GTD thing or a personal-GTD thing? It's really both: