X-Git-Url: https://vcs.fsf.org/?p=exim.git;a=blobdiff_plain;f=doc%2Fdoc-txt%2FREADME.SIEVE;h=d36998fe732ead1de187e2cfaaa22d9b50ebfa63;hp=4a9950e3b2b46fa05dfae72fbba258944e6210a4;hb=6aac3239b4ce9638c2c5647684dc4ff2a6afbb42;hpb=eed2e0b119d0d3b6813f06f7431cd68a5e99d488

diff --git a/doc/doc-txt/README.SIEVE b/doc/doc-txt/README.SIEVE
index 4a9950e3b..d36998fe7 100644
--- a/doc/doc-txt/README.SIEVE
+++ b/doc/doc-txt/README.SIEVE
@@ -1,5 +1,3 @@
-$Cambridge: exim/doc/doc-txt/README.SIEVE,v 1.12 2008/01/28 12:26:31 michael Exp $
-
               Notes on the Sieve implementation for Exim
 
 Exim Filter Versus Sieve Filter
@@ -276,7 +274,7 @@ The draft does not specify how strings using MIME entities are used
 to compose messages.  As a result, different implementations generate
 different mails.  The Exim Sieve implementation splits the reason into
 header and body.  It adds the header to the mail header and uses the body
-as mail body.  Be aware, that other imlementations compose a multipart
+as mail body.  Be aware, that other implementations compose a multipart
 structure with the reason as only part.  Both conform to the specification
 (or lack thereof).