[evolution] User Docs: Link to Seahorse User Manual

[Andre Klapper <aklapper src gnome org>]

commit 784624be2e6184c17598e4aa5691bc8a501cabac
Author: Andre Klapper <a9016009 gmx de>
Date:   Wed Aug 8 16:35:33 2012 +0200

    User Docs: Link to Seahorse User Manual

 help/C/mail-encryption-gpg-create-key.page |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/help/C/mail-encryption-gpg-create-key.page b/help/C/mail-encryption-gpg-create-key.page
index 1ced451..2d124ab 100644
--- a/help/C/mail-encryption-gpg-create-key.page
+++ b/help/C/mail-encryption-gpg-create-key.page
@@ -2,7 +2,7 @@
       type="topic" id="mail-encryption-gpg-create-key">
 
   <info>
-    <desc>Signing or encrypting messages via GPG that you send.</desc>
+    <desc>Signing or encrypting messages via GPG/OpenPGP that you send.</desc>
 
     <link type="guide" xref="mail-encryption#gpg"/>
 
@@ -22,7 +22,7 @@
 
   <title>Creating a GPG key</title>
 
-<note style="advanced"><p>These steps are very technical. For average users we nowadays recommend using the Seahorse application for managing GPG keys.</p></note>
+<note style="advanced"><p>These steps are very technical. For average users we recommend using the <link href="ghelp:seahorse#index"><app>Seahorse</app> application</link> for managing GPG/OpenPGP keys.</p></note>
 <!-- TODO:POST-3-2: Update and rewrite using Seahorse. Needs a complete rewrite once https://bugzilla.gnome.org/show_bug.cgi?id=508744 is fixed. -->
 
 <p>Before you can get or send GPG encrypted mail, you need to generate your public and private keys with GPG.</p>