user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: "Štěpán Němec" <stepnem@smrk.net>
Cc: meta@public-inbox.org
Subject: Re: [PATCH 5/5] Fix some typos/grammar/errors in docs and comments
Date: Mon, 28 Aug 2023 21:38:27 +0000	[thread overview]
Message-ID: <20230828213827.M189356@dcvr> (raw)
In-Reply-To: <20230828232247+0200.172961-stepnem@smrk.net>

Štěpán Němec <stepnem@smrk.net> wrote:
> Crystal clear, thank you!  Maybe add "With this option, [well-known...]"
> at the beginning, to avoid any possible confusion (it should go without
> saying, but being explicit doesn't hurt (and the original had it, too
> ("this option is given"))).

Alright, I'll squash this in before pushing:

diff --git a/Documentation/public-inbox-daemon.pod b/Documentation/public-inbox-daemon.pod
index 187c17d0..6f1e3b53 100644
--- a/Documentation/public-inbox-daemon.pod
+++ b/Documentation/public-inbox-daemon.pod
@@ -101,11 +101,11 @@ Default: 1
 The default TLS certificate for HTTPS, IMAPS, NNTPS, POP3S and/or STARTTLS
 support if the C<cert> option is not given with C<--listen>.
 
-Well-known TCP ports automatically get TLS or STARTTLS support if using
-systemd-compatible socket activation.  That is, ports 443, 563, 993, and
-995 support HTTPS, NNTPS, IMAPS, and POP3S, respectively; while ports
-110, 119, and 143 support STARTTLS on POP3, NNTP, and IMAP,
-respectively.
+With this option, well-known TCP ports automatically get TLS or STARTTLS
+support if using systemd-compatible socket activation.  That is, ports
+443, 563, 993, and 995 support HTTPS, NNTPS, IMAPS, and POP3S,
+respectively; while ports 110, 119, and 143 support STARTTLS on POP3,
+NNTP, and IMAP, respectively.
 
 =item --key /path/to/key
 

      reply	other threads:[~2023-08-28 21:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-28 10:42 [PATCH 1/5] ci/profiles.sh: fix case matching logic Štěpán Němec
2023-08-28 10:42 ` [PATCH 2/5] watch: remove unused variable Štěpán Němec
2023-08-28 10:42 ` [PATCH 3/5] spawn: remove stray variable $ndc_err Štěpán Němec
2023-08-28 10:42 ` [PATCH 4/5] spawn: remove distracting empty line Štěpán Němec
2023-08-28 10:42 ` [PATCH 5/5] Fix some typos/grammar/errors in docs and comments Štěpán Němec
2023-08-28 21:11   ` Eric Wong
2023-08-28 21:22     ` Štěpán Němec
2023-08-28 21:38       ` Eric Wong [this message]

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=20230828213827.M189356@dcvr \
    --to=e@80x24.org \
    --cc=meta@public-inbox.org \
    --cc=stepnem@smrk.net \
    /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).