Merge branch 'update21' into live

[enc-live.git] / en / index.html

diff --git a/en/index.html b/en/index.html
index e8f713879ad14354255bfc298ca111f41e86bad2..10c0f9cfcc8e97886152e3f89bdfad31c8e70f8d 100644 (file)
--- a/en/index.html
+++ b/en/index.html
@@ -835,7 +835,7 @@ takes a few hours for them to match each other when a new key is uploaded.</p>
 <p>Just in case you lose your key, or it gets compromised, you want to generate a certificate  and choose to save it in a safe place on your computer for now (please refer to <a href="#step-6c"> step 6.C</a> for how to best store your revocation cerficate safely). This step is essential for your email self-defense, as you'll learn more about in <a href="#section5">Section 5</a>.</p> 
  
 <p># Copy your keyID <text style="color:#2f5faa; font-family: monospace;">gnupg --list-key [your@email]</text> will list your public ("pub") key information, including your keyID, which is a unique list of numbers and letters. Copy this keyID, so you can use it in the following command.</p>
-<p># Upload your key to a server: <text style="color:#2f5faa; font-family: monospace;">gpg --output revoke.asc [keyID]</text></p>
+<p># Generate a revocation certificate: <text style="color:#2f5faa; font-family: monospace;">gpg --output revoke.asc [keyID]</text></p>
 <p># It will prompt you to give a reason for revocation, we recommend to use <text style="color:#2f5faa; font-family: monospace;">1 "key has been compromised"</text></p>
 <p># You don't have to fill in a reason, but you can, then press enter for an empty line, and comfirm your selection.</p>