Update

[elisp/semi.git] / emy.texi

diff --git a/emy.texi b/emy.texi
index 8dc36fe..8e41389 100644 (file)
--- a/emy.texi
+++ b/emy.texi
@@ -201,6 +201,22 @@ Unbuttonize article (@code{mime-preview-unbuttonize}).
 
 @end table
 
+@table @code
+
+@item C-c C-t C-h
+@kindex C-c C-t C-h (MIME-View)
+@findex mime-preview-toggle-header
+
+Toggle display of entity header.
+
+@item C-c C-t C-c
+@kindex C-c C-t C-c (MIME-View)
+@findex mime-preview-toggle-content
+
+Toggle display of entity body.
+
+@end table
+
 @node Changing Entity Button
 @section How buttons look like
 
@@ -215,7 +231,7 @@ You can customize where to add buttons and where to not with
 to change content of the button. It must be an alist of type or
 type/subtype vs. keywords.
 
-Three legal keywords are:
+Three valid keywords are:
 
 @table @code
 @item before
@@ -258,7 +274,7 @@ This means you will have buttons around message/* and
 multipart/alternative, and before application/*.
 
 @node How to deal with broken MUA
-@section Illegal MIME messages
+@section Invalid MIME messages
 
 Some MUAs send totally broken MIME messages.  According to the standard,
 it's perfectly fine for EMY not to grok those message.  However, EMY