[seahorse/wip/userdocs: 229/229] Start reworking on the help.

[Ekaterina Gerasimova <egerasimov src gnome org>]

commit a3b4f0b59e07df4b6535a7533d72863eebfe2f9c
Author: Aruna Sankaranarayanan <arunasank src gnome org>
Date:   Mon Mar 10 16:21:40 2014 +0530

    Start reworking on the help.
    
    Review bits and pieces

 help/C/introduction.page            |   12 +++++-------
 help/C/passwords-stored-create.page |    4 ++--
 help/C/pgp-create.page              |   26 +++++++++++++-------------
 help/C/pgp-delete.page              |   16 ++++++++--------
 4 files changed, 28 insertions(+), 30 deletions(-)
---
diff --git a/help/C/introduction.page b/help/C/introduction.page
index a24bdea..ecda37f 100644
--- a/help/C/introduction.page
+++ b/help/C/introduction.page
@@ -23,9 +23,8 @@
       <years>2013</years>
     </credit>
 
-    <desc><app>Passwords and Keys</app> helps you to create and manage PGP and
-    SSH keys. You can also use it to save passwords that are difficult to
-    remember.</desc>
+    <desc>Use <app>Passwords and Keys</app> to create and manage PGP and SSH
+    keys and to save passwords that are difficult to remember.</desc>
   </info>
 
   <title>Introduction</title>
@@ -38,10 +37,9 @@
 
   <list>
     <item>
-      <p>Copy and <link xref="passwords-stored-create">save</link>
-      passwords that are difficult to remember. You can also
-      <link xref="keyring-create">create keyrings</link> to group
-      related passwords.</p>
+      <p>Copy and <link xref="passwords-stored-create">save</link> passwords
+      that are difficult to remember. To group related passwords,
+      <link xref="keyring-create">create keyrings</link></p>
     </item>
     <item>
       <p><link xref="pgp-create">Create</link> and
diff --git a/help/C/passwords-stored-create.page b/help/C/passwords-stored-create.page
index 521453d..a490ddb 100644
--- a/help/C/passwords-stored-create.page
+++ b/help/C/passwords-stored-create.page
@@ -22,8 +22,8 @@
   <title>Store your passwords</title>
 
   <p><app>Passwords and Keys</app> automatically stores passwords for certain
-  GNOME applications in the <gui>Login</gui> keyring. You can also manually
-  store other passwords that you wish to remember.</p>
+  GNOME applications in the <gui>Login</gui> keyring. Additionally, you can
+  store any other password you want to remember.</p>
 
   <steps>
     <title>To create a new stored password:</title>
diff --git a/help/C/pgp-create.page b/help/C/pgp-create.page
index f6767a1..76b920c 100644
--- a/help/C/pgp-create.page
+++ b/help/C/pgp-create.page
@@ -23,10 +23,12 @@
       <years>2013</years>
     </credit>
 
-    <desc>Create GnuPG keys for encrypting and signing emails.</desc>
+    <desc>Create and use GnuPG keys for encrypting and signing emails.</desc>
   </info>
 
-  <title>Create a new PGP key</title>
+  <title>Create PGP keys</title>
+
+  <p>To make a new PGP key:</p>
 
   <steps>
     <item>
@@ -40,9 +42,8 @@
       <p>Enter your full name in the <gui>Full Name</gui> field.</p>
     </item>
     <item>
-      <p>Optionally, add your email address and a comment to describe the key.
-      Your date of birth, the purpose of creating the key, etc. make for good
-      descriptions.</p>
+      <p>Optionally, add your email address and a comment to describe the
+      key.</p>
     </item>
     <item>
       <p>Press <gui>Create</gui>.</p>
@@ -78,24 +79,23 @@
     <title>Key type</title>
       <p>Depending on your needs, create keys that can be used for signing only
       or for both encryption and signing. The RSA and DSA-Elgamal algorithms
-      generate equally secure keys. Similarly, your sign-only key can be either
-      RSA or DSA.</p>
+      generate equally secure keys.</p>
     </item>
     <item>
     <title>Key Strength</title>
       <p>The key strength is measured in terms of the size of the key in bits.
       It is difficult and more time consuming to break a strong key, but strong
-      keys also slow down the encryption and signing process. You should choose
+      keys will slow down the encryption and signing process. You should choose
       your key strength in <app>Passwords and Keys</app> depending on how long
       you want to use the key. A small key is sufficient for short term use
-      while a large key will remain secure for a long period of time.</p>
+      while a large key is more suitable for long term use.</p>
     </item>
     <item>
     <title>Expiration Date</title>
-      <p>When a key expires, it can no longer be used to sign or encrypt. In
-      <app>Passwords and Keys</app>, you can either set your key to
-      <gui style="checkbox">Never Expire</gui>, or select an expiration date
-      and time for it.</p>
+      <p>When a key <link xref="pgp-expired">expires</link>, you can no longer
+      use it to sign or encrypt. In <app>Passwords and Keys</app>, you can
+      either set your key to <gui style="checkbox">Never Expire</gui>, or
+      select an expiration date and time for it.</p>
     </item>
   </terms>
 
diff --git a/help/C/pgp-delete.page b/help/C/pgp-delete.page
index 2121111..5eef790 100644
--- a/help/C/pgp-delete.page
+++ b/help/C/pgp-delete.page
@@ -25,7 +25,7 @@
 
   <p>If you are no longer communicating with someone, you can delete the copy
   of their GnuPG key on your computer using <app>Passwords and Keys</app>. You
-  can also permanently delete a key you own, provided it has never been
+  can also permanently delete a key you own as long it has never been
   published on a key server. Deleting a GnuPG key deletes both the public key
   and the secret key.</p>
 
@@ -50,13 +50,13 @@
   <note style="important">
     <p>When you delete a GnuPG key that has been published on a key server, you
     only delete the secret key in the GnuPG keypair because a copy of the
-    public key will still be present on some key server. This means that
-    someone can <link xref="pgp-retrieve-remote">retrieve</link> the public key
-    from a key server and use it to encrypt messages to you but you will not be
-    able to decrypt those messages with the corresponding secret key. To
-    prevent the published key from being used, retrieve it and revoke it. The
-    revoked key can then be <link xref="pgp-sync">synced</link> with a key
-    server to prevent people from retrieving and using it.</p>
+    public key will still be present on some key server. This means that your
+    public key can still be <link xref="pgp-retrieve-remote">retrieved</link>
+    from a key server and used to encrypt messages to you, even though the
+    secret key has been deleted. To prevent such a key from being used,
+    retrieve and revoke it. The revoked key can then be
+    <link xref="pgp-sync">synced</link> with a key server to prevent people
+    from retrieving and using it.</p>
     <!-- or when you <link xref="misc-key-revoke">revoke</link> it.- No
     revoking feature yet for SSH keys/PGP master keys-->
   </note>