about summary refs log tree commit
diff options
context:
space:
mode:
authorEric Wong <e@yhbt.net>2020-02-04 11:15:15 +0000
committerEric Wong <e@yhbt.net>2020-02-04 21:39:43 +0000
commit69a58f258672fb0b4b5768b6d1cd75c6b1c5f3a8 (patch)
treebd23f4b4b3211442f59c1cd4dfc552365c3cd35b
parente95b4225b32cd561e608e3b9740024ed66fe7b0f (diff)
downloadpublic-inbox-69a58f258672fb0b4b5768b6d1cd75c6b1c5f3a8.tar.gz
The wording for publicinbox.nntpserver was awkward, too, and I
took this as opportunity to hopefully clarify it and favor
"hostname" for Internet addresses, because we already use
"address" to mean "email address" in the config.
-rw-r--r--Documentation/public-inbox-config.pod8
-rw-r--r--Documentation/public-inbox-v1-format.pod2
2 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/public-inbox-config.pod b/Documentation/public-inbox-config.pod
index a36680d9..24a4a5bb 100644
--- a/Documentation/public-inbox-config.pod
+++ b/Documentation/public-inbox-config.pod
@@ -220,12 +220,12 @@ Default: none; only for L<public-inbox-watch(1)> users
 
 =item publicinbox.nntpserver
 
-Set this to point to the address of the L<public-inbox-nntpd(1)>
+Set this to point to the hostname of the L<public-inbox-nntpd(1)>
 instance.  This is used to advertise the existence of the NNTP
-presnce in the L<PublicInbox::WWW> HTML interface.
+endpoint in the L<PublicInbox::WWW> HTML interface.
 
-Multiple values are allowed for servers with multiple
-addresses or mirrors.
+Multiple values are allowed for instances with multiple hostnames
+or mirrors.
 
 Default: none
 
diff --git a/Documentation/public-inbox-v1-format.pod b/Documentation/public-inbox-v1-format.pod
index c960913d..507c9451 100644
--- a/Documentation/public-inbox-v1-format.pod
+++ b/Documentation/public-inbox-v1-format.pod
@@ -131,7 +131,7 @@ Automatically updated by L<public-inbox-mda(1)>,
 L<public-inbox-learn(1)> and L<public-inbox-watch(1)>.
 
 This directory can always be regenerated with L<public-inbox-index(1)>.
-If lost or damaaged, there is no need to back it up unless the
+If lost or damaged, there is no need to back it up unless the
 CPU/memory cost of regenerating it outweighs the storage/transfer cost.
 
 Since SCHEMA_VERSION 15 and the development of the v2 format,