X-Git-Url: http://git.madism.org/?p=apps%2Fmadmutt.git;a=blobdiff_plain;f=doc%2FPGP-Notes.txt;h=f9e3b2a28d4b4979d289d1ff98a2b081e78f72ed;hp=6268b351c8eaed8184467f7784bb8e4d16658322;hb=29bfa77fef6bf9c0bba878257fc837b2e75f8256;hpb=8405d0fd3a83943d112b4a180cea3fc318a28a01

diff --git a/doc/PGP-Notes.txt b/doc/PGP-Notes.txt
index 6268b35..f9e3b2a 100644
--- a/doc/PGP-Notes.txt
+++ b/doc/PGP-Notes.txt
@@ -1,4 +1,4 @@
-User's guide - Using PGP/GnuPG with Mutt-ng
+User's guide - Using PGP/GnuPG with Madmutt
 ===========================================
 
 How do I use mutt with PGP, PGP5, or GnuPG?
@@ -9,7 +9,7 @@ three files there, pgp2.rc, pgp5.rc, and gpg.rc.  These files
 contain ready-to-use configurations for using mutt with pgp2, pgp5,
 and gpg.
 
-Include one of these files with your Mutt-ng config file (e.g. ~/.muttngrc), 
+Include one of these files with your Madmutt config file (e.g. ~/.madmuttrc), 
 and things should work out fine.
 
 You may wish to verify that all paths and  the language parameters
@@ -20,7 +20,7 @@ given to the PGP binaries match your needs.
 Frequently Asked Questions and Tips
 -----------------------------------
 
-Q: "People are sending PGP messages which Mutt-ng doesn't
+Q: "People are sending PGP messages which Madmutt doesn't
     recognize.  What can I do?"
 
 A: The new way is to leave headers alone and use mutt's
@@ -88,12 +88,12 @@ if (/^$BPGPS/:b && /^$EPGPS/:b)
 
 Q: "I don't like that PGP/MIME stuff, but want to use the
     old way of PGP-signing my mails.  Can't you include
-    that with Mutt-ng?"
+    that with Madmutt?"
 
 A: No.  Application/pgp is not really suited to a world with MIME,
    non-textual body parts and similar things.  Anyway, if you really
    want to generate these old-style attachments, include the
-   following macro in your ~/.muttngrc (line breaks for readability,
+   following macro in your ~/.madmuttrc (line breaks for readability,
    this is actually one line):
 
   macro compose S "Fpgp +verbose=0 -fast
@@ -103,7 +103,7 @@ A: No.  Application/pgp is not really suited to a world with MIME,
 
 There's a new answer, though: Set the pgp_autoinline
 configuration variable (it's a quad-option) to something different
-from "no" (that's the default).  Mutt-ng will then try to use
+from "no" (that's the default).  Madmutt will then try to use
 application/pgp whereever it makes sense.  In particular, it does
 not make any sense with multiparts, or non-ASCII or non-text bodies.
 In all other cases, PGP/MIME is used unconditionally.
@@ -147,7 +147,7 @@ BACKGROUND
 Auxiliary Programs
 ------------------
 
-Mutt-ng needs two auxiliary programs for its PGP support: pgpewrapng and
+Madmutt needs two auxiliary programs for its PGP support: pgpewrapng and
 pgpringng.
 
 
@@ -196,7 +196,7 @@ line interfaces can't be properly served by mutt's format mechanism.
 The Configuration Interface
 ---------------------------
 
-As usual within Mutt-ng, the configuration interface for the PGP
+As usual within Madmutt, the configuration interface for the PGP
 commands relies on printf-like formats.  For all PGP commands, the
 following %-sequences are defined.