From: Eric Wong <e@yhbt.net>
To: meta@public-inbox.org
Subject: [PATCH 5/8] doc: speling fickses
Date: Thu, 27 Aug 2020 12:17:03 +0000 [thread overview]
Message-ID: <20200827121706.4545-6-e@yhbt.net> (raw)
In-Reply-To: <20200827121706.4545-1-e@yhbt.net>
---
Documentation/public-inbox-edit.pod | 2 +-
Documentation/public-inbox-purge.pod | 2 +-
Documentation/public-inbox-tuning.pod | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/public-inbox-edit.pod b/Documentation/public-inbox-edit.pod
index 3853fa9c..68180872 100644
--- a/Documentation/public-inbox-edit.pod
+++ b/Documentation/public-inbox-edit.pod
@@ -102,7 +102,7 @@ edited data remaining indexed.
Incremental L<public-inbox-index(1)> (without C<--reindex>)
is fine.
-Keep in mind this is a last resort, as it will be distruptive
+Keep in mind this is a last resort, as it will be disruptive
to anyone using L<git(1)> to mirror the inbox being edited.
=head1 CONTACT
diff --git a/Documentation/public-inbox-purge.pod b/Documentation/public-inbox-purge.pod
index e20e18df..a9479657 100644
--- a/Documentation/public-inbox-purge.pod
+++ b/Documentation/public-inbox-purge.pod
@@ -62,7 +62,7 @@ purged data remaining indexed.
Incremental L<public-inbox-index(1)> (without C<--reindex>)
is fine.
-Keep in mind this is a last resort, as it will be distruptive
+Keep in mind this is a last resort, as it will be disruptive
to anyone using L<git(1)> to mirror the inbox being purged.
=head1 CONTACT
diff --git a/Documentation/public-inbox-tuning.pod b/Documentation/public-inbox-tuning.pod
index e3f2899b..b4e7698b 100644
--- a/Documentation/public-inbox-tuning.pod
+++ b/Documentation/public-inbox-tuning.pod
@@ -131,7 +131,7 @@ for parallelism.
The open file descriptor limit (C<RLIMIT_NOFILE>, C<ulimit -n> in L<sh(1)>,
C<LimitNOFILE=> in L<systemd.exec(5)>) may need to be raised to
-accomodate many concurrent clients.
+accommodate many concurrent clients.
Transport Layer Security (IMAPS, NNTPS, or via STARTTLS) significantly
increases memory use of client sockets, sure to account for that in
next prev parent reply other threads:[~2020-08-27 12:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 12:16 [PATCH 0/8] mostly watch-related odds and ends Eric Wong
2020-08-27 12:16 ` [PATCH 1/8] watchmaildir: ensure I:/W:/E: prefixes in warnings Eric Wong
2020-08-27 12:17 ` [PATCH 2/8] imaptracker: preserve WAL journal_mode if set by user Eric Wong
2020-08-27 12:17 ` [PATCH 3/8] overidx: inline create_ghost sub Eric Wong
2020-08-27 12:17 ` [PATCH 4/8] doc: document graceful shutdown signals Eric Wong
2020-08-27 12:17 ` Eric Wong [this message]
2020-08-27 12:17 ` [PATCH 6/8] watch: imap: only remove \Seen spam Eric Wong
2020-08-27 12:17 ` [PATCH 7/8] doc: move watch config docs to -watch manpage Eric Wong
2020-08-27 12:17 ` [PATCH 8/8] doc: watch: expand on NNTP and IMAP-specific knobs Eric Wong
2020-08-28 4:22 ` 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: http://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=20200827121706.4545-6-e@yhbt.net \
--to=e@yhbt.net \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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).