# HG changeset patch
# User Richard M. Stallman <rms@gnu.org>
# Date 1195962574 0
# Node ID 52972c3aa85ec769450c6c2f3e4c4c4de9f44ca3
# Parent  1aadc9bdea814d401fee5269c0ba3c013e7c7dfa
(Eval During Expansion): Minor cleanup.

diff -r 1aadc9bdea81 -r 52972c3aa85e doc/lispref/macros.texi
--- a/doc/lispref/macros.texi	Sun Nov 25 03:49:12 2007 +0000
+++ b/doc/lispref/macros.texi	Sun Nov 25 03:49:34 2007 +0000
@@ -623,7 +623,7 @@
 
   Another problem with calling @code{eval} in a macro definition is that
 it probably won't do what you intend in a compiled program.  The
-byte-compiler runs macro definitions while compiling the program, when
+byte compiler runs macro definitions while compiling the program, when
 the program's own computations (which you might have wished to access
 with @code{eval}) don't occur and its local variable bindings don't
 exist.