From: boehm.igor@gmail.com
To: <9front@9front.org>
Subject: [9front] upasfs(4) patch
Date: Tue, 22 Dec 2020 16:44:55 +0100 [thread overview]
Message-ID: <4AABB19EEF42A07F705877F87BD17067@gmail.com> (raw)
Spotted two small typos while reading upasfs(4) during first time
email setup:
diff -r 33920ebb68d1 sys/man/4/upasfs
--- a/sys/man/4/upasfs Thu Dec 17 21:02:11 2020 +0100
+++ b/sys/man/4/upasfs Tue Dec 22 16:37:00 2020 +0100
@@ -226,7 +226,7 @@
have been closed.
.TP
.B "create \fImboxname\fP
-create a new maibox,
+create a new mailbox,
.BR mboxname .
The mailbox type must support creation.
.TP
@@ -479,5 +479,5 @@
.br
Erik Quanstrom
``Scaling Upas'',
-Procedings of IWP9,
+Proceedings of IWP9,
October, 2008.
next reply other threads:[~2020-12-22 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 15:44 boehm.igor [this message]
2020-12-22 16:44 ` cinap_lenrek
2020-12-22 16:46 ` ori
2020-12-22 16:59 ` ori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AABB19EEF42A07F705877F87BD17067@gmail.com \
--to=boehm.igor@gmail.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).