X-Git-Url: https://www.tinc-vpn.org/git/browse?p=tinc;a=blobdiff_plain;f=doc%2FPROTOCOL;h=3ac958497f3aef9551f0f99c97e537f9464d5ae8;hp=74741e7c188cea0b4d7ae650a01e7a94c5b45e9c;hb=HEAD;hpb=de78d79db84c486afcc353884ec1770866beb653

diff --git a/doc/PROTOCOL b/doc/PROTOCOL
index 74741e7c..3ac95849 100644
--- a/doc/PROTOCOL
+++ b/doc/PROTOCOL
@@ -12,9 +12,6 @@ This is the protocol documentation for tinc, a Virtual Private Network daemon.
    provided that the entire resulting derived work is distributed
    under the terms of a permission notice identical to this one.
 
-   $Id$
-
-
 1.  Protocols used in tinc
 -------------------------
 
@@ -36,7 +33,7 @@ is pretty basic.
 A data packet can only be sent if the encryption key, cipher and digest are
 known to both parties, and the connection is activated. If the encryption key
 is not known, a request is sent to the destination using the meta connection to
-retreive it.
+retrieve it.
 
 0   1   2   3   4   5   6   7   ...   97  98  99  100
 |     seqno     |         data        |     MAC       |
@@ -62,7 +59,7 @@ daemon and to read and write requests by hand, provided that one
 understands the numeric codes sent.
 
 The authentication scheme is described in the SECURITY2 file. After a
-succesful authentication, the server and the client will exchange all the
+successful authentication, the server and the client will exchange all the
 information about other tinc daemons and subnets they know of, so that both
 sides (and all the other tinc daemons behind them) have their information
 synchronised.