From 5c6ce1c7d035ad412e9bdec6cf385c06ffd5680e Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Wed, 31 Oct 2012 12:23:06 -0700 Subject: [PATCH] Spelling fixes. --- doc/lispref/loading.texi | 2 +- doc/lispref/variables.texi | 2 +- doc/misc/cl.texi | 3 +-- src/w32proc.c | 2 +- src/xterm.c | 2 +- 5 files changed, 5 insertions(+), 6 deletions(-) diff --git a/doc/lispref/loading.texi b/doc/lispref/loading.texi index 6a18bea2977..79fd352adfb 100644 --- a/doc/lispref/loading.texi +++ b/doc/lispref/loading.texi @@ -615,7 +615,7 @@ specified by an autoload object: @defun autoload-do-load autoload &optional name macro-only This function performs the loading specified by @var{autoload}, which -whould be an autoload object. The optional argument @var{name}, if +should be an autoload object. The optional argument @var{name}, if non-@code{nil}, should be a symbol whose function value is @var{autoload}; in that case, the return value of this function is the symbol's new function value. If the value of the optional argument diff --git a/doc/lispref/variables.texi b/doc/lispref/variables.texi index 580dd8258df..88b7909126e 100644 --- a/doc/lispref/variables.texi +++ b/doc/lispref/variables.texi @@ -2033,7 +2033,7 @@ itself be a valid @var{place} form. For example, @code{(setf (nthcdr @c to standard Common Lisp. @c FIXME I don't think is a particularly good way to do it, -@c but these macros are introduced before gvs are. +@c but these macros are introduced before generalized variables are. The macros @code{push} (@pxref{List Variables}) and @code{pop} (@pxref{List Elements}) can manipulate generalized variables, not just lists. @code{(pop @var{place})} removes and returns the first diff --git a/doc/misc/cl.texi b/doc/misc/cl.texi index d01798497da..10735420534 100644 --- a/doc/misc/cl.texi +++ b/doc/misc/cl.texi @@ -991,7 +991,7 @@ has been made. @xref{Obsolete Setf Customization}. @c FIXME should this be in lispref? It seems self-evident. @c Contrast with the cl-incf example later on. -@c Here it really only serves as a constrast to wrong-order. +@c Here it really only serves as a contrast to wrong-order. The @code{setf} macro takes care to evaluate all subforms in the proper left-to-right order; for example, @@ -5129,4 +5129,3 @@ defined later. @printindex vr @bye - diff --git a/src/w32proc.c b/src/w32proc.c index d45d9879a24..a0ff96e593c 100644 --- a/src/w32proc.c +++ b/src/w32proc.c @@ -519,7 +519,7 @@ term_timers (void) void init_timers (void) { - /* GetThreadTimes is not avaiulable on all versions of Windows, so + /* GetThreadTimes is not available on all versions of Windows, so need to probe for its availability dynamically, and call it through a pointer. */ s_pfn_Get_Thread_Times = NULL; /* in case dumped Emacs comes with a value */ diff --git a/src/xterm.c b/src/xterm.c index 8b005873f4d..f8420d13a32 100644 --- a/src/xterm.c +++ b/src/xterm.c @@ -3448,7 +3448,7 @@ x_focus_changed (int type, int state, struct x_display_info *dpyinfo, struct fra /* Don't stop displaying the initial startup message for a switch-frame event we don't need. */ - /* When run as a deamon, Vterminal_frame is always NIL. */ + /* When run as a daemon, Vterminal_frame is always NIL. */ if ((NILP (Vterminal_frame) || EQ (Fdaemonp(), Qt)) && CONSP (Vframe_list) && !NILP (XCDR (Vframe_list))) -- 2.39.2