diff --git a/locale/en/help.xml b/locale/en/help.xml
index a26247486..c17fdec0b 100644
--- a/locale/en/help.xml
+++ b/locale/en/help.xml
@@ -150,13 +150,6 @@
         </tip>
     </entry>
 
-    <entry id="pgp-compose-attach-pubkey">
-        <title>PGP: Preferences: Attach Public Key</title>
-        <para>
-            If selected then a copy of your PGP public key, if it exists, will be attached to the outgoing message. You can set the default behavior via the PGP Preferences screen.
-        </para>
-    </entry>
-
     <entry id="pgp-option-reply-pubkey">
         <title>PGP: Preferences: Validate PGP Public Keys When Replying</title>
         <para>
@@ -190,6 +183,10 @@
         <para>
             This option will first digitally sign your message and then will encrypt the resulting output with a passphrase. See the &quot;PGP Encrypt Message with passphrase&quot; and &quot;PGP Sign Message&quot; entries for further information.
         </para>
+        <heading>Attach Public Key</heading>
+        <para>
+            If selected then a copy of your PGP public key, if it exists, will be attached to the outgoing message. You can set the default behavior via the PGP Preferences screen.
+        </para>
         <heading>S/MIME Encrypt Message</heading>
         <para>
             This option will encrypt the current message, using S/MIME and the recipient's certificate, and then send it. You MUST have the certificate of the recipient stored in your addressbook or else this option will fail. If you have the certificate for the recipient in your addressbook and are still receiving errors, verify that the e-mail address in the recipient field matches the e-mail address where the certificate is stored. The encrypted data will be attached to the outgoing message.