[Emacs-diffs] /srv/bzr/emacs/trunk r110751: Spelling fixes.

[Paul Eggert]

------------------------------------------------------------
revno: 110751
committer: Paul Eggert <address@hidden>
branch nick: trunk
timestamp: Wed 2012-10-31 12:23:06 -0700
message:
  Spelling fixes.
modified:
  doc/lispref/loading.texi
  doc/lispref/variables.texi
  doc/misc/cl.texi
  src/w32proc.c
  src/xterm.c

=== modified file 'doc/lispref/loading.texi'
--- a/doc/lispref/loading.texi  2012-10-30 00:29:37 +0000
+++ b/doc/lispref/loading.texi  2012-10-31 19:23:06 +0000
@@ -615,7 +615,7 @@
 
 @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
 address@hidden, 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

=== modified file 'doc/lispref/variables.texi'
--- a/doc/lispref/variables.texi        2012-10-30 07:54:17 +0000
+++ b/doc/lispref/variables.texi        2012-10-31 19:23:06 +0000
@@ -2033,7 +2033,7 @@
 @c to standard Common Lisp.
 
 @c FIXME I don't think is a particularly good way to do it,
address@hidden but these macros are introduced before gvs are.
address@hidden 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

=== modified file 'doc/misc/cl.texi'
--- a/doc/misc/cl.texi  2012-10-31 07:25:18 +0000
+++ b/doc/misc/cl.texi  2012-10-31 19:23:06 +0000
@@ -991,7 +991,7 @@
 
 @c FIXME should this be in lispref?  It seems self-evident.
 @c Contrast with the cl-incf example later on.
address@hidden Here it really only serves as a constrast to wrong-order.
address@hidden 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 @@
 @printindex vr
 
 @bye
-

=== modified file 'src/w32proc.c'
--- a/src/w32proc.c     2012-10-28 17:42:52 +0000
+++ b/src/w32proc.c     2012-10-31 19:23:06 +0000
@@ -519,7 +519,7 @@
 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 */

=== modified file 'src/xterm.c'
--- a/src/xterm.c       2012-10-21 14:53:28 +0000
+++ b/src/xterm.c       2012-10-31 19:23:06 +0000
@@ -3448,7 +3448,7 @@
 
           /* 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)))