changeset 96364:c5e50585b044

American English spelling fix.
author Glenn Morris <rgm@gnu.org>
date Fri, 27 Jun 2008 02:25:04 +0000
parents f9d35151b907
children 65532b2a1819
files lisp/ChangeLog.9 lisp/calendar/calendar.el lisp/calendar/todo-mode.el
diffstat 3 files changed, 3 insertions(+), 3 deletions(-) [+]
line wrap: on
line diff
--- a/lisp/ChangeLog.9	Fri Jun 27 02:23:35 2008 +0000
+++ b/lisp/ChangeLog.9	Fri Jun 27 02:25:04 2008 +0000
@@ -17047,7 +17047,7 @@
 	(widget-leave-text, widget-children-value-delete): Use mapc.
 	(widget-keymap): Remove XEmacs stuff.
 	(widget-field-keymap, widget-text-keymap): Define all inside defvar.
-	(widget-button-click): Don't set point at the click, but re-centre
+	(widget-button-click): Don't set point at the click, but re-center
 	if we scroll out of window.  Rewritten for images v. glyphs &c.
 	(widget-tabable-at): Use POS arg, not point.
 	(widget-beginning-of-line, widget-end-of-line)
--- a/lisp/calendar/calendar.el	Fri Jun 27 02:23:35 2008 +0000
+++ b/lisp/calendar/calendar.el	Fri Jun 27 02:25:04 2008 +0000
@@ -1415,7 +1415,7 @@
    ;; Put in the days of the month.
    (dotimes (i last)
      (setq day (1+ i))
-     ;; TODO should numbers be left-justified, centred...?
+     ;; TODO should numbers be left-justified, centered...?
      (insert (format (format "%%%dd%%s" calendar-day-digit-width) day
                      (make-string
                       (- calendar-column-width calendar-day-digit-width) ?\s)))
--- a/lisp/calendar/todo-mode.el	Fri Jun 27 02:23:35 2008 +0000
+++ b/lisp/calendar/todo-mode.el	Fri Jun 27 02:25:04 2008 +0000
@@ -209,7 +209,7 @@
 ;;     	the end of the loop and you will insert your item just before
 ;;     	that point.  If you set the threshold to, e.g. 8, it will stop
 ;;     	as soon as the window size drops below that amount and will
-;;     	insert the item in the approximate centre of that window.  I
+;;     	insert the item in the approximate center of that window.  I
 ;;     	got the idea for this feature after reading a very helpful
 ;;     	e-mail reply from Trey Jackson <trey@cs.berkeley.edu> who
 ;;     	corrected some of my awful coding and pointed me towards some