aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLeah Neukirchen <leah@vuxu.org>2017-03-13 16:12:31 +0100
committerLeah Neukirchen <leah@vuxu.org>2017-03-13 16:12:31 +0100
commit53c6a3b37ee28dd11698ec414939aad18244db68 (patch)
treecb6c9c8dcac1786d178a874cf13cd6c371288523
parent04b29f4e307b2e7f7467d091b9e2bb840223a4dd (diff)
downloadmblaze-53c6a3b37ee28dd11698ec414939aad18244db68.tar.gz
mblaze.7: small edits
-rw-r--r--README10
-rw-r--r--man/mblaze.712
2 files changed, 11 insertions, 11 deletions
diff --git a/README b/README
index 754ccdb..20bbf49 100644
--- a/README
+++ b/README
@@ -8,9 +8,9 @@ DESCRIPTION
kept in Maildir folders.
Its design is roughly inspired by MH, the RAND Message Handling System,
- but its is a complete implementation from scratch.
+ but it is a complete implementation from scratch.
- mblaze consists of a set of Unix tools that each do one job:
+ mblaze consists of these Unix tools that each do one job:
maddr(1) to extract addresses from mail
magrep(1) to find mails matching a pattern
mcom(1) to write and send mail
@@ -34,8 +34,8 @@ DESCRIPTION
mthread(1) to arrange mail into discussions
PRINCIPLES
- mblaze is a classic command line MUA with no features related to
- receiving and transferring mail. You are expected to fetch your mail
+ mblaze is a classic command line MUA and has no features related to
+ receiving and transferring mail; you are expected to fetch your mail
using offlineimap(1), fdm(1), procmail(1), getmail(1) or similar and send
it using sendmail(8), as provided by OpenSMTPD, Postfix, msmtp(1), dma(8)
or similar. mblaze expects your mail to reside in Maildir folders.
@@ -48,7 +48,7 @@ PRINCIPLES
operations on big Maildir may feel slow, but as soon as they are in file
system cache, everything is blazing fast. The tools are written to be
memory efficient (i.e. not wasteful), but whole messages are assumed to
- fit into RAM easily (at a time).
+ fit into RAM easily (one at a time).
mblaze has been written from scratch and tested on a big pile of personal
mail, but is not actually 100% RFC conforming (which is neither worth it
diff --git a/man/mblaze.7 b/man/mblaze.7
index ee8b3e5..4af87af 100644
--- a/man/mblaze.7
+++ b/man/mblaze.7
@@ -11,10 +11,10 @@ message system is a set of Unix utilities to deal with
mail kept in Maildir folders.
.Pp
Its design is roughly inspired by MH, the RAND Message Handling
-System, but its is a complete implementation from scratch.
+System, but it is a complete implementation from scratch.
.Pp
.Nm
-consists of a set of Unix tools that each do one job:
+consists of these Unix tools that each do one job:
.Bl -tag -width 11n -compact
.It Xr maddr 1
to extract addresses from mail
@@ -62,9 +62,9 @@ to arrange mail into discussions
.El
.Sh PRINCIPLES
.Nm
-is a classic command line MUA with no features related to receiving
-and transferring mail.
-You are expected to fetch your mail using
+is a classic command line MUA and has no features related to receiving
+and transferring mail;
+you are expected to fetch your mail using
.Xr offlineimap 1 ,
.Xr fdm 1 ,
.Xr procmail 1 ,
@@ -91,7 +91,7 @@ Parsing mail metadata is optimized to use few I/O requests.
Initial operations on big Maildir may feel slow, but as soon as they
are in file system cache, everything is blazing fast.
The tools are written to be memory efficient (i.e. not wasteful), but
-whole messages are assumed to fit into RAM easily (at a time).
+whole messages are assumed to fit into RAM easily (one at a time).
.Pp
.Nm
has been written from scratch and tested on a big pile of personal mail,