commit

diff --git a/en/index.html b/en/index.html
index 17b07304002b8a3ff6a78809a1e23913c1d0710f..d91fb0fc6c3f4424400f77abb5bb6aaf3e37dcb3 100644 (file)
--- a/en/index.html
+++ b/en/index.html
@@ -438,7 +438,7 @@
                                <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
                                <div id="step-sign_real_keys" class="step">
                                        <div class="main">
-                                               <h3><em>Important:</em> check people's identification before signing their keys</h3>
+                                               <h3>Identifying keys: Fingerprints and IDs</h3>
                                                <p>People's public keys are usually identified by their key fingerprint, which is a string of digits like F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8 (for Edward's key). You can see the fingerprint for your public key, and other public keys saved on your computer, by going to Enigmail &rarr; Key Management in your email program's menu, then right clicking on the key and choosing Key Properties. It's good practice to share your fingerprint wherever you share your email address, so that people can double-check that they have the correct public key when they download yours from a keyserver.</p>
 
 <p class="notes">You may also see public keys referred to by their key ID, which is simply the last 8 digits of the fingerprint, like C09A61E8 for Edward. The key ID is visible directly from the Key Management window. This key ID is like a person's first name (it is a useful shorthand but may not be unique to a given key), whereas the fingerprint actually identifies the key uniquely without the possibility of confusion. If you only have the key ID, you can still look up the key (as well as its fingerprint), like you did in Step 3, but if multiple options appear, you'll need the fingerprint of the person to whom you are trying to communicate to verify which one to use.</p>