commit 829ba5dc87657cd7f097f766ae4bc1d7ff3879c8
parent 85ec356041c06f0e7955ff3aceda513dcb065d4e
Author: wmorgan <wmorgan@5c8cc53c-5e98-4d25-b20a-d8db53a31250>
Date: Fri, 14 Sep 2007 01:59:32 +0000
userguide spelling corrections thanks to ian taylor
git-svn-id: svn://rubyforge.org/var/svn/sup/trunk@571 5c8cc53c-5e98-4d25-b20a-d8db53a31250
Diffstat:
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/UserGuide.txt b/doc/UserGuide.txt
@@ -68,7 +68,7 @@ messages together into threads: each line in the inbox is a thread,
and the number in parentheses is the number of messages in that
thread. (If there's no number, there's just one message in the
thread.) In Sup, most operations are on threads, not individual
-messages. The ideais that you rarely want to operate on a message
+messages. The idea is that you rarely want to operate on a message
independent of its context. You typically want to view, archive, kill,
or label all the messages in a thread at one time.
@@ -238,7 +238,7 @@ Here's what I recommend:
on, and with a label corresponding to the mailing list name.
(E.g.: sup-add mbox:/home/me/Mail/ruby-talk -a -l ruby-talk)
3. Voila! Sup will load new messages into the index but not into the
- inbox, and you can browse the mailing list traffice at any point by
+ inbox, and you can browse the mailing list traffic at any point by
searching for that label.