X-Git-Url: https://vcs.fsf.org/?p=exim.git;a=blobdiff_plain;f=doc%2Fdoc-misc%2FRFC.conform;h=1ddd5b33d586ebe9941febe663ab5a6c48726e34;hp=91683cf9e4de5b9305913d91638e00ec4beb18f3;hb=b09c17939112f84e689a9c1343f00ca84610325d;hpb=4045b3d360f9b5c45cbaba294ea6ababd58c4724

diff --git a/doc/doc-misc/RFC.conform b/doc/doc-misc/RFC.conform
index 91683cf9e..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.)