From 1ec2933434f22e7ebc5184e90fe864c56f8d6452 Mon Sep 17 00:00:00 2001
From: Mikaela Suomalainen <mikaela.suomalainen@outlook.com>
Date: Tue, 31 Jul 2012 10:05:59 +0300
Subject: [PATCH] GPG guide: add example keyid with 0xLONG format.

---
 articles/guides/GPG/GPG.html    | 2 ++
 articles/guides/GPG/GPG.html.md | 4 ++++
 2 files changed, 6 insertions(+)

diff --git a/articles/guides/GPG/GPG.html b/articles/guides/GPG/GPG.html
index a15e74b..f7b2b67 100644
--- a/articles/guides/GPG/GPG.html
+++ b/articles/guides/GPG/GPG.html
@@ -114,6 +114,8 @@ encrypt-to KEYID</code></pre>
 <p>keyid-format 0xLONG</p>
 </blockquote>
 <p>So keyids are shown in the longest format, including 0x prefix, which marks them as hexadecimanls.</p>
+<p>Example outputs from --list-keys and gpg --fingerprint after setting 0xLONG as keyid format.</p>
+<p>After you set 0xLONG as keyid-format, keys appear like 0x4DB53CFE82A46728 instead of 82A46728.</p>
 <blockquote>
 <p>charset UTF-8</p>
 </blockquote>
diff --git a/articles/guides/GPG/GPG.html.md b/articles/guides/GPG/GPG.html.md
index eb08540..81e0b18 100644
--- a/articles/guides/GPG/GPG.html.md
+++ b/articles/guides/GPG/GPG.html.md
@@ -176,6 +176,10 @@ So everything what you encrypt is also encrypted to you.
 
 So keyids are shown in the longest format, including 0x prefix, which marks them as hexadecimanls.
 
+Example outputs from --list-keys and gpg --fingerprint after setting 0xLONG as keyid format.
+
+After you set 0xLONG as keyid-format, keys appear like 0x4DB53CFE82A46728 instead of 82A46728.
+
 > charset UTF-8
 
 So UTF-8 is used as default character set and most of characters can be used.