# HG changeset patch
# User adrian
# Date 1079787956 0
# Node ID f4702ef3fd366bb30aa6c421905c85cf9eab6855
# Parent  b10161763edff43a8e4a4819e088e96bc02e545c
[xemacs-hg @ 2004-03-20 13:05:53 by adrian]
xemacs-21.5: typo fixes for src/eval.c

-------------------- ChangeLog entries follow: --------------------

src/ChangeLog addition:

2004-03-20  Adrian Aichner  <adrian@xemacs.org>

	* eval.c: Typo fixes.

diff -r b10161763edf -r f4702ef3fd36 src/ChangeLog
--- a/src/ChangeLog	Sat Mar 20 12:51:25 2004 +0000
+++ b/src/ChangeLog	Sat Mar 20 13:05:56 2004 +0000
@@ -1,3 +1,7 @@
+2004-03-20  Adrian Aichner  <adrian@xemacs.org>
+
+	* eval.c: Typo fixes.
+
 2004-03-16  Jerry James  <james@xemacs.org>
 
 	* alloc.c: Make gc_currently_forbidden readable in other files.
diff -r b10161763edf -r f4702ef3fd36 src/eval.c
--- a/src/eval.c	Sat Mar 20 12:51:25 2004 +0000
+++ b/src/eval.c	Sat Mar 20 13:05:56 2004 +0000
@@ -56,7 +56,7 @@
    The only exception is the alloc.c module, which implements the
    framework upon which this module (eval.c) works.  alloc.c works
    with creating the actual Lisp objects themselves and garbage
-   collecting them as necessary, preseting a nice, high-level
+   collecting them as necessary, presenting a nice, high-level
    interface for object creation, deletion, access, and modification.
 
    The only other exception that could be cited is the event-handling
@@ -73,7 +73,7 @@
    functions such as `command-loop-1', a Lisp function.
 
    As the Lisp engine is doing its thing, it maintains the state of
-   the engine primarily in five list-like items, with are:
+   the engine primarily in five list-like items, which are:
 
    -- the backtrace list
    -- the catchtag list