[Gpg4win-commits] r521 - in trunk/doc: . manual

[scm-commit@wald.intevation.org]

Author: jan
Date: 2007-09-10 14:34:03 +0200 (Mon, 10 Sep 2007)
New Revision: 521

Modified:
   trunk/doc/ChangeLog
   trunk/doc/manual/novices.tex
Log:
* manual/novices.tex: Some minor improvements. By Geo Kocheril.


Modified: trunk/doc/ChangeLog
===================================================================
--- trunk/doc/ChangeLog	2007-09-07 21:48:16 UTC (rev 520)
+++ trunk/doc/ChangeLog	2007-09-10 12:34:03 UTC (rev 521)
@@ -1,3 +1,7 @@
+2007-09-10  Jan-Oliver Wagner  <jan-oliver.wagner at intevation.de>
+
+	* manual/novices.tex: Some minor improvements. By Geo Kocheril.
+
 2007-09-07  Jan-Oliver Wagner  <jan-oliver.wagner at intevation.de>
 
 	* website/build-history.awk: Added a link for each release to

Modified: trunk/doc/manual/novices.tex
===================================================================
--- trunk/doc/manual/novices.tex	2007-09-07 21:48:16 UTC (rev 520)
+++ trunk/doc/manual/novices.tex	2007-09-10 12:34:03 UTC (rev 521)
@@ -161,11 +161,11 @@
 which you are reading right now,
 
 \item \textbf{the manual "Gpg4win for Advanced Users"} in PDF-Format,
-which can be found on your hard drive after you have installed Gpg4win,
-
+which can be found on your hard drive after you have installed Gpg4win or on
+the project homepage,
 \item \textbf{the exercise robot Adele,} which allows you to practice
 the \Email{} en- and decryption process (an internet connection is
-required). 
+required).
 \end{itemize}
 
 
@@ -597,7 +597,8 @@
 
 \textbf{
 In order to exchange secure \Email{}s, each party must have access to
-the public key of the other party. 
+the public key of the other party. Naturally the receiver needs also a
+software that can handle with the keys like the Gpg4win modules do.
 }
 
 In order to send someone encrypted \Email{}s, you must have their
@@ -1006,8 +1007,8 @@
 Chapter 10 of the advanced manual also discusses ways to attach a
 signature to \Email{} messages. This is the equivalent of attaching an
 electronic seal to your message, allowing the recipient to verify
-whether the \Email{} has been altered during transmission (and that it
-came from you).
+whether the \Email{} has been altered during transmission
+and that the \Email{} definitely came from you).
 
 The signature verification process is simple. For this, you
 need the sender's public key on your Gpg4win-"key ring" (see
@@ -1172,7 +1173,7 @@
 \end{center}
 
 This opens the GnuPG Preferences Window. You can add your key in the
-"Encrypt to this key" field using your \Email{} address.
+"Encrypt to this key" field using your (corresponding) \Email{} address.
 
 \Email{} programs which directly support GnuPG will also feature this
 option.