From: Kyle Meyer <kyle@kyleam.com>
To: meta@public-inbox.org
Cc: Kyle Meyer <kyle@kyleam.com>
Subject: [PATCH] doc: fix a few minor typos
Date: Sat, 6 Apr 2019 23:31:40 -0400 [thread overview]
Message-ID: <20190407033140.22121-1-kyle@kyleam.com> (raw)
---
Documentation/public-inbox-nntpd.pod | 2 +-
Documentation/public-inbox-v2-format.pod | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/public-inbox-nntpd.pod b/Documentation/public-inbox-nntpd.pod
index a38687f..749851d 100644
--- a/Documentation/public-inbox-nntpd.pod
+++ b/Documentation/public-inbox-nntpd.pod
@@ -13,7 +13,7 @@ public-inbox. It uses options and environment variables common
to all L<public-inbox-daemon(8)> implementations.
The default configuration will never require write access
-tto the directory where the public-inbox is stored, so it
+to the directory where the public-inbox is stored, so it
may be run as a different user than the user running
L<public-inbox-watch(1)>, L<public-inbox-mda(1)>, or
L<git-fetch(1)>.
diff --git a/Documentation/public-inbox-v2-format.pod b/Documentation/public-inbox-v2-format.pod
index 05ef32a..7dfe329 100644
--- a/Documentation/public-inbox-v2-format.pod
+++ b/Documentation/public-inbox-v2-format.pod
@@ -109,7 +109,7 @@ code paths.
The performance of the storage device is now the bottleneck on
larger multi-core systems. In our experience, performance is
-improves with high-quality and high-quantity solid-state storage.
+improved with high-quality and high-quantity solid-state storage.
Issuing TRIM commands with L<fstrim(8)> was necessary to maintain
consistent performance while developing this feature.
@@ -210,7 +210,7 @@ for all non-atomic operations.
=head1 HEADERS
-Same handling as with v1, except the Message-ID header will will
+Same handling as with v1, except the Message-ID header will
be generated if not provided or conflicting. "Bytes", "Lines"
and "Content-Length" headers are stripped and not allowed, they
can interfere with further processing.
--
2.21.0
next reply other threads:[~2019-04-07 3:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-07 3:31 Kyle Meyer [this message]
2019-04-11 4:26 ` [PATCH] doc: fix a few minor typos Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190407033140.22121-1-kyle@kyleam.com \
--to=kyle@kyleam.com \
--cc=meta@public-inbox.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 read-only IMAP folder(s) and NNTP newsgroup(s).