More doc updates for multi-frame images

* doc/emacs/files.texi (File Conveniences): Not just GIFs can be animated.

* doc/lispref/display.texi (Multi-Frame Images): Minor rephrasing.

* etc/NEWS: Related edits.

2 files changed, 8 insertions, 4 deletions

diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index 74f2eb9312b..355d0b57be5 100644
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -1,3 +1,7 @@
+2013-02-21  Glenn Morris  <rgm@gnu.org>
+
+        * display.texi (Multi-Frame Images): Minor rephrasing.
+
 2013-02-20  Glenn Morris  <rgm@gnu.org>
 
         * display.texi (GIF Images, TIFF Images): Delete these nodes.
diff --git a/doc/lispref/display.texi b/doc/lispref/display.texi
index 1e596c14233..eae6af9969d 100644
--- a/doc/lispref/display.texi
+++ b/doc/lispref/display.texi
@@ -4925,10 +4925,10 @@ integer (counting from 0) that specifies which frame is being displayed.
 This function returns non-@code{nil} if @var{image} contains more than
 one frame.  The actual return value is a cons @code{(@var{nimages}
 . @var{delay})}, where @var{nimages} is the number of frames and
-@var{delay} is the delay in seconds between them, if the image itself
-specifies a delay.  Images that are intended to be animated usually
-specify a frame delay, whereas ones that are intended to be treated as
-multiple pages do not.
+@var{delay} is the delay in seconds between them, or @code{nil}
+if the image does not specify a delay.  Images that are intended to be
+animated usually specify a frame delay, whereas ones that are intended
+to be treated as multiple pages do not.
 @end defun
 
 @defun image-current-frame image