X-Git-Url: https://git.exim.org/users/heiko/exim.git/blobdiff_plain/261dc43e32f6039781ca92535e56f5caaa68b809..0929ce9ca518b6987b63cf8659338ca434e07d9b:/doc/doc-src/FAQ.src

diff --git a/doc/doc-src/FAQ.src b/doc/doc-src/FAQ.src
index 461b1a608..9280e0314 100644
--- a/doc/doc-src/FAQ.src
+++ b/doc/doc-src/FAQ.src
@@ -1,4 +1,3 @@
-## $Cambridge: exim/doc/doc-src/FAQ.src,v 1.8 2009/11/05 19:37:00 nm4 Exp $
 ##
 ## This file is processed by Perl scripts to produce an ASCII and an HTML
 ## version. Lines starting with ## are omitted. The markup used with paragraphs
@@ -851,7 +850,7 @@ A0044: Exim has been unable to create a file in its spool area in which to
 
        If you are running Exim with an alternate configuration file using a
        command such as \"exim -C altconfig..."\, remember that the use of -C
-       takes away Exim's root privilege, unless \\TRUSTED_CONFIG_PREFIX_FILE\\
+       takes away Exim's root privilege, unless \\TRUSTED_CONFIG_LIST\\
        is set in \(Local/Makefile)\ and the corresponding file contains a
        prefix which matches the alternative configuration file being used.
 
@@ -1155,7 +1154,7 @@ A0065: When Exim is called with -C, it passes on -C to any instances of itself
        includes the case where Exim re-execs itself to regain root privilege.
        Thus it can't write to the spool.
 
-       The fix for this is to use the \\TRUSTED_CONFIG_PREFIX_LIST\\ build-time
+       The fix for this is to use the \\TRUSTED_CONFIG_LIST\\ build-time
        option. This defines a file containing a list of 'trusted' prefixes for
        configuration files. Any configuration file specified with -C, if it
        matches a prefix listed in that file, will be used without dropping root
@@ -2317,7 +2316,7 @@ A0310: If a DNS lookup returns no MXs, Exim looks for an address record, in
 
 
 Q0311: When a DNS lookup for MX records fails to complete, why doesn't Exim
-       send the messsage to the host defined by the A record?
+       send the message to the host defined by the A record?
 
 A0311: The RFCs are quite clear on this. Only if it is known that there are no
        MX records is an MTA allowed to make use of the A record. When an MX