X-Git-Url: https://vcs.fsf.org/?a=blobdiff_plain;f=doc%2Fdoc-misc%2FRFC.conform;h=1ddd5b33d586ebe9941febe663ab5a6c48726e34;hb=5ffbf3a3b9bbc8ebc7a0b29bf753febe283f5fa9;hp=bcd7e4001cee1f36886020072c84938d3504ad83;hpb=8a330e5a9133a14ea43b648ae8c5dedcaf7ca3f7;p=exim.git

diff --git a/doc/doc-misc/RFC.conform b/doc/doc-misc/RFC.conform
index bcd7e4001..1ddd5b33d 100644
--- a/doc/doc-misc/RFC.conform
+++ b/doc/doc-misc/RFC.conform
@@ -98,7 +98,7 @@ enclosed in <> characters, so a header such as
 
   From: @a,@b:c@d
 
-is syntactally invalid. Exim does not enforce this restriction.
+is syntactically invalid. Exim does not enforce this restriction.
 
 
 1.6 Local parts [3.4.1]
@@ -243,7 +243,7 @@ MTA for the same message.
 [Multihomed host addresses should not be randomized.]
 
 Exim does randomize a list of several addresses for a single host, because
-caching in resolvers will defeat the round-robinning that many namerservers
+caching in resolvers will defeat the round-robinning that many nameservers
 use. (Note: this is not the same as randomizing equal-valued MX records. That
 is required by the RFC.)
 
@@ -372,13 +372,13 @@ It is possible to specify exception lists of hosts and/or networks for which
 this check does not apply.
 
 
-2.18 Format of delivery error messages [3.7]
+2.17 Format of delivery error messages [3.7]
 --------------------------------------------
 
 [Standard report formats should be used if possible.]
 
-Exim's delivery failure reports do not conform to the format described in RFC
-1894.
+Exim's delivery failure reports are MIME format, and might be RFC1894
+conformant, but this has not been verified.
 
 
 ## End ##