X-Git-Url: https://git.exim.org/exim.git/blobdiff_plain/dd80338c6a23ab8a6af2875256f9077479f055b3..2506b3e03ffd4617cec535b45ae1f8cb5db5e799:/doc/doc-docbook/spec.xfpt

diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt
index 76bdd1396..3da27cdea 100644
--- a/doc/doc-docbook/spec.xfpt
+++ b/doc/doc-docbook/spec.xfpt
@@ -28220,7 +28220,7 @@ There are good and bad examples at the end of the next section.
 
 
 
-.section "The PLAIN authentication mechanism" "SECID172"
+.subsection "The PLAIN authentication mechanism" "SECID172"
 .cindex "PLAIN authentication mechanism"
 .cindex authentication PLAIN
 .cindex "binary zero" "in &(plaintext)& authenticator"
@@ -28304,7 +28304,7 @@ always fails if its second argument is empty. However, the second way of
 writing the test makes the logic clearer.
 
 
-.section "The LOGIN authentication mechanism" "SECID173"
+.subsection "The LOGIN authentication mechanism" "SECID173"
 .cindex "LOGIN authentication mechanism"
 .cindex authentication LOGIN
 The LOGIN authentication mechanism is not documented in any RFC, but is in use
@@ -28352,7 +28352,7 @@ the password conform to the Exim syntax. At the LDAP level, the password is an
 uninterpreted string.
 
 
-.section "Support for different kinds of authentication" "SECID174"
+.subsection "Support for different kinds of authentication" "SECID174"
 A number of string expansion features are provided for the purpose of
 interfacing to different ways of user authentication. These include checking
 traditionally encrypted passwords from &_/etc/passwd_& (or equivalent), PAM,