*** empty log message ***

1 files changed, 16 insertions, 15 deletions

diff --git a/lispref/intro.texi b/lispref/intro.texi
index 10c3763822a..34a6ae12fac 100644
--- a/lispref/intro.texi
+++ b/lispref/intro.texi
@@ -343,7 +343,7 @@ the ``copyright'' line and a pointer to where the full notice is found.
 
 @smallexample
 @var{one line to give the program's name and an idea of what it does.}
-Copyright (C) 19@var{yy}  @var{name of author}
+Copyright (C) @var{year}  @var{name of author}
 
 This program is free software; you can redistribute it and/or
 modify it under the terms of the GNU General Public License
@@ -366,7 +366,7 @@ If the program is interactive, make it output a short notice like this
 when it starts in an interactive mode:
 
 @smallexample
-Gnomovision version 69, Copyright (C) 19@var{yy} @var{name of author}
+Gnomovision version 69, Copyright (C) @var{year} @var{name of author}
 Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
 type `show w'.  This is free software, and you are welcome
 to redistribute it under certain conditions; type `show c' 
@@ -521,7 +521,7 @@ worry about it; this manual is self-contained.
 
 @pindex cl
   A certain amount of Common Lisp emulation is available via the
-@file{cl} library @xref{Top,, Common Lisp Extension, cl, Common Lisp
+@file{cl} library.  @xref{Top,, Common Lisp Extension, cl, Common Lisp
 Extensions}.
 
   Emacs Lisp is not at all influenced by Scheme; but the GNU project has
@@ -556,10 +556,9 @@ addressed as ``you''.  ``The user'' is the person who uses Lisp
 programs, including those you write.
 
 @cindex fonts
-  Examples of Lisp code appear in this font or form: @code{(list 1 2
-3)}.  Names that represent metasyntactic variables, or arguments to a
-function being described, appear in this font or form:
-@var{first-number}.
+  Examples of Lisp code are formatted like this: @code{(list 1 2 3)}.
+Names that represent metasyntactic variables, or arguments to a function
+being described, are formatted like this: @var{first-number}.
 
 @node nil and t
 @subsection @code{nil} and @code{t}
@@ -685,13 +684,13 @@ the echo area.
 @subsection Buffer Text Notation
 @cindex buffer text notation
 
-  Some examples show modifications to text in a buffer, with ``before''
-and ``after'' versions of the text.  These examples show the contents of
-the buffer in question between two lines of dashes containing the buffer
-name.  In addition, @samp{@point{}} indicates the location of point.
-(The symbol for point, of course, is not part of the text in the buffer;
-it indicates the place @emph{between} two characters where point is
-currently located.)
+  Some examples describe modifications to the contents of a buffer, by
+showing the ``before'' and ``after'' versions of the text.  These
+examples show the contents of the buffer in question between two lines
+of dashes containing the buffer name.  In addition, @samp{@point{}}
+indicates the location of point.  (The symbol for point, of course, is
+not part of the text in the buffer; it indicates the place
+@emph{between} two characters where point is currently located.)
 
 @example
 ---------- Buffer: foo ----------
@@ -900,7 +899,9 @@ emacs-build-time
 The value of this variable is the version of Emacs being run.  It is a
 string such as @code{"20.3.1"}.  The last number in this string is not
 really part of the Emacs release version number; it is incremented each
-time you build Emacs in any given directory.
+time you build Emacs in any given directory.  A value with three numeric
+components, such as @code{"20.3.9.1"}, indicates an unreleased test
+version.
 @end defvar
 
   The following two variables have existed since Emacs version 19.23: