*** empty log message ***

diff --git a/lisp/emacs-lisp/byte-run.el b/lisp/emacs-lisp/byte-run.el
index 48760d1..ecf2ed5 100644 (file)
--- a/lisp/emacs-lisp/byte-run.el
+++ b/lisp/emacs-lisp/byte-run.el
@@ -227,7 +227,7 @@ In interpreted code, this is entirely equivalent to `progn'."
 ;;   verbose     t, nil                byte-compile-verbose
 ;;   optimize    t, nil, source, byte  byte-compile-optimize
 ;;   warnings    list of warnings      byte-compile-warnings
-;;                   Legal elements: (callargs redefine free-vars unresolved)
+;;                   Valid elements: (callargs redefine free-vars unresolved)
 ;;   file-format         emacs18, emacs19      byte-compile-compatibility
 ;;
 ;; For example, this might appear at the top of a source file:

diff --git a/lisp/ffap.el b/lisp/ffap.el
index 3e62f23..aaf92eb 100644 (file)
--- a/lisp/ffap.el
+++ b/lisp/ffap.el
@@ -426,7 +426,7 @@ Returned values:
   ;; (ffap-machine-p "mathcs" 5678 nil 'ping)
   ;; (ffap-machine-p "foo.bonk" nil nil 'ping)
   ;; (ffap-machine-p "foo.bonk.com" nil nil 'ping)
-  (if (or (string-match "[^-[:alnum:].]" host) ; Illegal chars (?)
+  (if (or (string-match "[^-[:alnum:].]" host) ; Invalid chars (?)
          (not (string-match "[^0-9]" host))) ; 1: a number? 2: quick reject
       nil
     (let* ((domain

diff --git a/lisp/follow.el b/lisp/follow.el
index ea5bf96..e251d4c 100644 (file)
--- a/lisp/follow.el
+++ b/lisp/follow.el
@@ -300,7 +300,7 @@
 ;; above for an example of how to bind the keys the way you like.
 ;;
 ;; Please note that the keymap is defined the first time this file is
-;; loaded.  Also note that the only legal way to manipulate the
+;; loaded.  Also note that the only valid way to manipulate the
 ;; keymap is to use `define-key'.  Don't change it using `setq' or
 ;; similar!
 

diff --git a/lisp/isearch.el b/lisp/isearch.el
index e72df62..131bde7 100644 (file)
--- a/lisp/isearch.el
+++ b/lisp/isearch.el
@@ -1461,7 +1461,7 @@ to the barrier."
        ;; removes all bracket-sets and groups that might be in the way, as
        ;; well as partial \{\} constructs that the code below leaves behind.
        ;; Also skip over postfix operators -- though horrid,
-       ;; 'ab?\{5,6\}+\{1,2\}*' is perfectly legal.
+       ;; 'ab?\{5,6\}+\{1,2\}*' is perfectly valid.
        (while (and previous
                    (or (isearch-error-state frame)
                        (let* ((string (isearch-string-state frame))