summaryrefslogtreecommitdiff
path: root/lispref/compile.texi
diff options
context:
space:
mode:
authorRomain Francoise <romain@orebokech.com>2006-05-07 16:02:27 +0000
committerRomain Francoise <romain@orebokech.com>2006-05-07 16:02:27 +0000
commit5a36d8349df0f59c79a310b20a0966286560f557 (patch)
tree055731cd650007b7cea0fb0896ee74faa5cd2291 /lispref/compile.texi
parentad8a840d25775bd194419743a043309e4a0799af (diff)
downloademacs-5a36d8349df0f59c79a310b20a0966286560f557.tar.gz
* commands.texi (Event Input Misc):
* compile.texi (Eval During Compile): * internals.texi (Buffer Internals): * minibuf.texi (Initial Input): * nonascii.texi (Scanning Charsets): * numbers.texi (Comparison of Numbers): * windows.texi (Textual Scrolling, Vertical Scrolling): Fix various typos.
Diffstat (limited to 'lispref/compile.texi')
-rw-r--r--lispref/compile.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/lispref/compile.texi b/lispref/compile.texi
index 1d8823a48c5..4b796697731 100644
--- a/lispref/compile.texi
+++ b/lispref/compile.texi
@@ -412,7 +412,7 @@ automatically @code{eval-and-compile}, the package is loaded both when
compiling and executing.
@code{autoload} is also effectively @code{eval-and-compile} too. It's
-recognised when compiling, so uses of such a function don't produce
+recognized when compiling, so uses of such a function don't produce
``not known to be defined'' warnings.
Most uses of @code{eval-and-compile} are fairly sophisticated.
@@ -456,7 +456,7 @@ used to load it for compiling, but not executing. For example,
The same sort of thing goes for macros or @code{defalias}es defined
locally and only for use within the file. They can be defined while
compiling, but then not needed when executing. This is good for code
-that's only a fallback for compability with other versions of Emacs.
+that's only a fallback for compatibility with other versions of Emacs.
For example.
@lisp