about summary refs log tree commit homepage
path: root/Documentation
diff options
context:
space:
mode:
authorKyle Meyer <kyle@kyleam.com>2019-04-06 23:31:40 -0400
committerEric Wong <e@80x24.org>2019-04-11 04:24:56 +0000
commit96d4a98d1a28ec64b5abd8289ddd4177ff87ad7e (patch)
tree87e6b7781089cdb131985367953ec473c1ec39f9 /Documentation
parent3cf66514aea9e958999973b9f104473b6d800fbe (diff)
downloadpublic-inbox-96d4a98d1a28ec64b5abd8289ddd4177ff87ad7e.tar.gz
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/public-inbox-nntpd.pod2
-rw-r--r--Documentation/public-inbox-v2-format.pod4
2 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/public-inbox-nntpd.pod b/Documentation/public-inbox-nntpd.pod
index a38687f6..749851d4 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 05ef32a9..7dfe3296 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.