changeset 96367:25423ee77a10

American English spelling fix.
author Glenn Morris <rgm@gnu.org>
date Fri, 27 Jun 2008 02:29:47 +0000
parents f6d8a6067020
children 3b1e90875bee
files lisp/ChangeLog.13 lisp/org/org-table.el lisp/progmodes/cc-awk.el
diffstat 3 files changed, 4 insertions(+), 4 deletions(-) [+]
line wrap: on
line diff
--- a/lisp/ChangeLog.13	Fri Jun 27 02:27:38 2008 +0000
+++ b/lisp/ChangeLog.13	Fri Jun 27 02:29:47 2008 +0000
@@ -11224,7 +11224,7 @@
 	(server-execute, server-return-error): New functions extracted from
 	server-process-filter.
 	(server-execute-continuation): New functions.
-	(server-process-filter): Restructure so that all arguments are analysed
+	(server-process-filter): Restructure so that all arguments are analyzed
 	first and then acted upon in a subsequent stage.  This way
 	server-goto-toplevel can be executed later, when we know if
 	it's necessary.
--- a/lisp/org/org-table.el	Fri Jun 27 02:27:38 2008 +0000
+++ b/lisp/org/org-table.el	Fri Jun 27 02:29:47 2008 +0000
@@ -1864,7 +1864,7 @@
 		     (string-match "^[a-zA-Z][a-zA-Z0-9]*$" field))
 	      (push (cons field v) org-table-local-parameters)
 	      (push (list field line col) org-table-named-field-locations))))
-      ;; Analyse the line types
+      ;; Analyze the line types
       (goto-char beg)
       (setq org-table-current-begin-line (org-current-line)
 	    org-table-current-begin-pos (point)
--- a/lisp/progmodes/cc-awk.el	Fri Jun 27 02:27:38 2008 +0000
+++ b/lisp/progmodes/cc-awk.el	Fri Jun 27 02:29:47 2008 +0000
@@ -28,7 +28,7 @@
 ;; integration of AWK Mode.
 ;; It is organised thusly, the sections being separated by page breaks:
 ;;   1. The AWK Mode syntax table.
-;;   2. Regular expressions for analysing AWK code.
+;;   2. Regular expressions for analyzing AWK code.
 ;;   3. Indentation calculation stuff ("c-awk-NL-prop text-property").
 ;;   4. Syntax-table property/font-locking stuff, including the
 ;;      font-lock-keywords setting.
@@ -710,7 +710,7 @@
   ;;
   ;; ANCHOR-STATE-/DIV identifies whether a / at ANCHOR would have been a
   ;; division sign (value t) or a regexp opener (value nil).  The idea is that
-  ;; we analyse the line from ANCHOR up till point to determine what the / at
+  ;; we analyze the line from ANCHOR up till point to determine what the / at
   ;; point is.
   ;;
   ;; The result is what ANCHOR-STATE-/DIV (see above) is where point is left.