## docs/keysigning-help

### changeset 3:aa9f4b501eaf tip

spell checked
author meillo@marmaro.de Wed, 18 Feb 2009 18:02:39 +0100 1d91fadb416f keysigning-help.tex references.bib 2 files changed, 5 insertions(+), 5 deletions(-) [+]
line diff
     1.1 --- a/keysigning-help.tex	Wed Feb 18 17:33:03 2009 +0100
1.2 +++ b/keysigning-help.tex	Wed Feb 18 18:02:39 2009 +0100
1.3 @@ -36,7 +36,7 @@
1.4
1.5  \section{Introduction}
1.6
1.7 -This document tries to help people in organizing a keysiging event. It should be seen as concrete suggestions for how to do things that are already described by the keysigning method in general. The method defines how to organize the keysigning, this document makes concrete suggestions \emph{how} to do things. This document also shows how to generate WOT graphs.
1.8 +This document tries to help people in organizing a Keysigning event. It should be seen as concrete suggestions for how to do things that are already described by the keysigning method in general. The method defines how to organize the keysigning, this document makes concrete suggestions \emph{how} to do things. This document also shows how to generate WOT graphs.
1.9
1.10
1.11
1.12 @@ -78,7 +78,7 @@
1.13
1.14  \section{Participant list}
1.15
1.16 -You have to generate a list that contains the public keys of all participants. A script to do this automatically with nice formating is available \cite{keylist}. The script is not perfect, but sufficient.
1.17 +You have to generate a list that contains the public keys of all participants. A script to do this automatically with nice formatting is available \cite{keylist}. The script is not perfect, but sufficient.
1.18
1.19  {\tt\small
1.20  \begin{verbatim}
1.21 @@ -89,7 +89,7 @@
1.22
1.23  The script generates a public key list from all keys in the keyring (first argument). This list can get prepended by the contents of text files (all further arguments).
1.24
1.25 -A general header is demanded by good style. Descriptions of what the participants need to do are highly recommended in order to support unexperienced participants. Fields to insert the checksums should be provided anyway. Examples for the here included files can be found at \cite{keylist}.
1.26 +A general header is demanded by good style. Descriptions of what the participants need to do are highly recommended in order to support inexperienced participants. Fields to insert the checksums should be provided anyway. Examples for the here included files can be found at \cite{keylist}.
1.27
1.28  %Figure \ref{fig:keylist} shows a sample participant list.
1.29
1.30 @@ -157,7 +157,7 @@
1.31
1.32  Receiving keys, signing them, and sending the signatures back to the key owners can be a wasteful job, especially if may people took part in a keysigning event.
1.33
1.34 -The nice tool \texttt{caff} \cite{signing-party} is a great helper. It automates the whole process, from key retrival, to signing, to sending the signatures. (An MTA is required to send signatures.)
1.35 +The nice tool \texttt{caff} \cite{signing-party} is a great helper. It automates the whole process, from key retrieval, to signing, to sending the signatures. (An MTA is required to send signatures.)
1.36
1.37
1.38

     2.1 --- a/references.bib	Wed Feb 18 17:33:03 2009 +0100
2.2 +++ b/references.bib	Wed Feb 18 18:02:39 2009 +0100
2.3 @@ -35,7 +35,7 @@
2.4  }
2.5
2.6  @misc{signing-party,
2.7 -	author = {Various contributers},
2.8 +	author = {Various contributors},
2.9  	title = {\textit{PGP Tools}},
2.10  	note = {\url{http://pgp-tools.alioth.debian.org}\,},
2.11  }