diff options
author | Alexandre Rostovtsev <tetromino@gmail.com> | 2011-08-15 21:38:28 +0800 |
---|---|---|
committer | Rodrigo Moya <rodrigo@gnome-db.org> | 2011-09-14 20:08:49 +0800 |
commit | 4728c6f6c0d0a9b35457af020c2301f26f2f8efb (patch) | |
tree | 35fbd0db9a566c2df896293c8879c7453eebcfd6 /help/C/mail-encryption-gpg-create-key.page | |
parent | 71a1a5f186eec5e102fdb55aaf0cccaa40d54409 (diff) | |
download | gsoc2013-evolution-4728c6f6c0d0a9b35457af020c2301f26f2f8efb.tar gsoc2013-evolution-4728c6f6c0d0a9b35457af020c2301f26f2f8efb.tar.gz gsoc2013-evolution-4728c6f6c0d0a9b35457af020c2301f26f2f8efb.tar.bz2 gsoc2013-evolution-4728c6f6c0d0a9b35457af020c2301f26f2f8efb.tar.lz gsoc2013-evolution-4728c6f6c0d0a9b35457af020c2301f26f2f8efb.tar.xz gsoc2013-evolution-4728c6f6c0d0a9b35457af020c2301f26f2f8efb.tar.zst gsoc2013-evolution-4728c6f6c0d0a9b35457af020c2301f26f2f8efb.zip |
Bug #656537 - Fix mallard relaxng validation errors in help pages
Diffstat (limited to 'help/C/mail-encryption-gpg-create-key.page')
-rw-r--r-- | 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 a99004abc5..e7997e2819 100644 --- a/help/C/mail-encryption-gpg-create-key.page +++ b/help/C/mail-encryption-gpg-create-key.page @@ -22,7 +22,7 @@ <title>Creating a GPG key</title> -<note>These steps are very technical. For average users we nowadays recommend using the Seahorse application for managing GPG keys.</note> +<note><p>These steps are very technical. For average users we nowadays recommend using the Seahorse application for managing GPG 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> @@ -44,7 +44,7 @@ <p>If you want, you can upload your keys to a key server:</p> <steps> <item><p>Check your public key ID with <code>gpg --list-keys</code>. It is the string after <code>1024D</code> on the line beginning with <code>pub</code>. In the example above, it is <code>32j38dk2</code>.</p></item> -<item><p>Enter the command <code>gpg --send-keys --keyserver wwwkeys.pgp.net <varname>32j38dk2</varname></code>. Substitute your key ID for <quote>32j38dk2</quote>. You need your password to do this.</p></item> +<item><p>Enter the command <code>gpg --send-keys --keyserver wwwkeys.pgp.net 32j38dk2</code>. Substitute your key ID for <code>32j38dk2</code>. You need your password to do this.</p></item> </steps> <p>Key servers store your public keys for you so that your friends can decrypt your messages. If you choose not to use a key server, you can manually send your public key, include it in your signature file, or put it on your own Web page. However, it is easier to publish a key once, and then let people download it from a central place when they want.</p> |