From 17a28de8bf05d314426ed6498e2690baac129b58 Mon Sep 17 00:00:00 2001
From: Laurent Bercot <ska-skaware@skarnet.org>
Date: Sun, 8 Feb 2026 04:50:57 +0000
Subject:  Doc typo fixes

---
 doc/qmail-remote.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'doc')

diff --git a/doc/qmail-remote.html b/doc/qmail-remote.html
index 1cfc91a..d8d3c99 100644
--- a/doc/qmail-remote.html
+++ b/doc/qmail-remote.html
@@ -55,7 +55,7 @@ where this version of <tt>qmail-remote</tt> is installed.
  <li> If the underlying OS and <a href="//skarnet.org/software/skalibs/">skalibs</a>
 support IPv6, then this <tt>qmail-remote</tt> does as well, and uses IPv4 and IPv6
 addresses indiscriminately when connecting to an MX. </li>
- <li> It speaks ESMTP and will use STARTTLS if the server supports it. </li>
+ <li> It will use STARTTLS if the server supports it. </li>
  <li> All its DNS resolutions are done in parallel, which eliminates some
 pathological cases where the original <tt>qmail-remote</tt> can hang around doing
 nothing for a <em>long</em> time. </li>
@@ -105,7 +105,7 @@ This is useful in certain setups requiring client authentication. </dd>
  <dd> This file must be used in conjunction with <tt>clientcert</tt>. It contains
 the path to the private key used to sign the client certificate. Note that access
 to the private key file should be as restricted as possible, but the <tt>qmailr</tt>
-user (or whatever user <tt>qmail-smtpc</tt> runs as) must be able to read it. </dd>
+user (or whatever user <tt>qmail-remote</tt> runs as) must be able to read it. </dd>
 
  <dt> <tt>tlsstrictness</tt> </dt>
  <dd> This file contains an integer representing the strictness level expected of
-- 
cgit v1.3.1