[seahorse/mallard-help] Changes according to Jim's suggestions.

[Aruna Sankaranarayanan <arunasank src gnome org>]

commit 2c8f536c7ac217a335f01146143c9d6f35cb6a26
Author: Aruna Sankaranarayanan <arunasank src gnome org>
Date:   Tue Aug 13 21:44:03 2013 +0530

    Changes according to Jim's suggestions.

 help/C/about-key-strength.page          |   15 +++++++++------
 help/C/about-pgp.page                   |    2 +-
 help/C/glossary.page                    |    6 +++---
 help/C/passwords-control-access.page    |   10 +++++-----
 help/C/pgp-advanced-expiration-set.page |    5 ++---
 help/C/pgp-expired.page                 |    2 +-
 6 files changed, 21 insertions(+), 19 deletions(-)
---
diff --git a/help/C/about-key-strength.page b/help/C/about-key-strength.page
index af86952..be0482d 100644
--- a/help/C/about-key-strength.page
+++ b/help/C/about-key-strength.page
@@ -31,12 +31,15 @@
   <p>It is difficult and more time consuming to break a strong key, but
   stronger keys also 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 they key. If you are going to be using the key for a
-  very short period, a small key is sufficient while stronger keys should be
-  generated if you are going to use them for longer periods of time. It would
-  take the average computer more than 14 billion years to crack a key that is
-  2048 bits long, thus a 2048 bit key is usually sufficient for general
-  usage.</p>
+  long you want to use they key. A small key is sufficient if you are going to
+  be using it for a short period of time, but a longer key would be more secure
+  if you are going to be using it for a long period of time.</p>
+
+  <note style="tip">
+    <p>It would take the average computer more than 14 billion years to crack a
+    key that is 2048 bits long, thus a 2048 bit key is usually sufficient for
+    general usage.</p>
+  </note>
 
   <!-- stefw: I would suggest basing this page off the current
     reccomendations for key strength. The basic concepts for key
diff --git a/help/C/about-pgp.page b/help/C/about-pgp.page
index adc2267..7ec3975 100644
--- a/help/C/about-pgp.page
+++ b/help/C/about-pgp.page
@@ -5,7 +5,7 @@
 
   <info>
     <link type="guide" xref="learn-about-keys" group="first"/>
-
+    <link type="seealso" xref="about-ssh"/>
     <revision version="0.1" date="2011-10-23" status="stub"/>
     <revision pkgversion="3.9" version="0.1" date="2013-07-03" status="review"/>
 
diff --git a/help/C/glossary.page b/help/C/glossary.page
index 58e853a..89468e5 100644
--- a/help/C/glossary.page
+++ b/help/C/glossary.page
@@ -23,8 +23,8 @@
   <title>Introduction</title>
 
   <p><app>Passwords and Keys</app> helps you to generate and manage tokens that
-  can be used to protect your files and communication. Some basic terms you
-  will encounter while reading this help are:</p>
+  can be used to protect your files and communication. Here are some basic
+  terms that you will encounter while reading this help:</p>
 
   <terms>
     <item>
@@ -49,7 +49,7 @@
     </item>
     <item>
       <title>Plaintext</title>
-        <p>Any data or file that is not encrypted, and therefore understood by
+       <p>Any data or file that is not encrypted, and can therefore be read by
        anyone who can access it, is called plaintext.</p>
     </item>
     <item>
diff --git a/help/C/passwords-control-access.page b/help/C/passwords-control-access.page
index 2605e46..ba466f8 100644
--- a/help/C/passwords-control-access.page
+++ b/help/C/passwords-control-access.page
@@ -30,8 +30,8 @@
       you unlock the keyring.</p>
     </item>
     <item>
-      <p>Protect it with a password. This requires you to type the password
-      for the keyring while unlocking it.</p>
+      <p>Protect your keyring with a password. This requires you to type the
+      password for the keyring while unlocking it.</p>
     </item>
   </list>
 
@@ -43,13 +43,13 @@
     <item>
       <p>Right click on the selected keyring and select <gui>Lock</gui> or
       click the small picture of an opened lock next to the name of the
-      password keyring to lock the keyring.</p>
+      password keyring. This will lock the keyring.</p>
       <note style="info">
        <p>A locked keyring can be unlocked by right clicking on a selected
        keyring and selecting <gui>Unlock</gui> or clicking the picture of the
        closed lock next to the name of the locked keyring. If the keyring has
-       been protected with a password during
-       <link xref="passwords-keyring-create">keyring creation</link>, you will
+       been protected with a password when the keyring was
+       <link xref="passwords-keyring-create">created</link>, you will
        be prompted to enter the password while unlocking it.</p>
       </note>
     </item>
diff --git a/help/C/pgp-advanced-expiration-set.page b/help/C/pgp-advanced-expiration-set.page
index ef04b60..8964e01 100644
--- a/help/C/pgp-advanced-expiration-set.page
+++ b/help/C/pgp-advanced-expiration-set.page
@@ -34,9 +34,8 @@
       <p>Untick the <gui style="checkbox">Never Expires</gui> checkbox.</p>
     </item>
     <item>
-      <p>Choose the new expiry date and time from the drop down menus
-      displaying the date and time. You can also manually enter the expiry date
-      and time for your key.</p>
+      <p>Choose the new expiry date and time from the drop down menus. You can
+      also manually enter the expiry date and time for your key.</p>
     </item>
   </steps>
 
diff --git a/help/C/pgp-expired.page b/help/C/pgp-expired.page
index 69f4f21..2225671 100644
--- a/help/C/pgp-expired.page
+++ b/help/C/pgp-expired.page
@@ -37,7 +37,7 @@
   <p>Depending on how long you want your key to be valid, you can
   <link xref="pgp-advanced-expiration-set">set an expiration date</link> for
   it. By default, <app>Passwords and Keys</app> sets all keys to be valid
-  forever, that is the keys never expire.</p>
+  forever. That is, the keys never expire.</p>
 
   <p>The expiration date on a key can be
   <link xref="pgp-expiration-change">changed</link> anytime, even after