Avoid @strong{Note:}.

diff --git a/lispref/ChangeLog b/lispref/ChangeLog
index 3404bd304d8d8f5df48d23f578c55d6312a6df1b..02e1e4e54f0460b41093926bfcd7c71173bd3883 100644 (file)
--- a/lispref/ChangeLog
+++ b/lispref/ChangeLog
@@ -1,3 +1,14 @@
+2003-09-26  Richard M. Stallman  <rms@gnu.org>
+
+
+       * buffers.texi, commands.texi, debugging.texi, eval.texi: 
+       * loading.texi, minibuf.texi, text.texi, variables.texi:
+       Avoid @strong{Note:}.
+
+2003-09-26  Richard M. Stallman  <rms@gnu.org>
+
+       * keymaps.texi (Remapping Commands): Fix typo.
+
 2003-09-23  Luc Teirlinck  <teirllm@mail.auburn.edu>
 
        * processes.texi (Low-Level Network): Fix typo.

diff --git a/lispref/buffers.texi b/lispref/buffers.texi
index c811f0b00178bbcc477cf97abbddfe9664872b5e..5b1104eb058fd4cb12ea1d7d2f36aec74ee50acf 100644 (file)
--- a/lispref/buffers.texi
+++ b/lispref/buffers.texi
@@ -106,7 +106,7 @@ Emacs reads a command is the buffer that the command will apply to.
 switch visibly to a different buffer so that the user can edit it.  For
 that, you must use the functions described in @ref{Displaying Buffers}.
 
-  @strong{Note:} Lisp functions that change to a different current buffer
+  @strong{Warning:} Lisp functions that change to a different current buffer
 should not depend on the command loop to set it back afterwards.
 Editing commands written in Emacs Lisp can be called from other programs
 as well as from the command loop; it is convenient for the caller if

diff --git a/lispref/commands.texi b/lispref/commands.texi
index b60cb2b87328c74129ca2fa820f0b8d4b28d9445..4a8fe10c4c82339e046eee0ac8393a5993f664e0 100644 (file)
--- a/lispref/commands.texi
+++ b/lispref/commands.texi
@@ -2055,7 +2055,7 @@ calls that function, passing the character as an argument.
 If this is non-@code{nil}, its value specifies the current input method
 function.
 
-@strong{Note:} Don't bind this variable with @code{let}.  It is often
+@strong{Warning:} don't bind this variable with @code{let}.  It is often
 buffer-local, and if you bind it around reading input (which is exactly
 when you @emph{would} bind it), switching buffers asynchronously while
 Emacs is waiting will cause the value to be restored in the wrong

diff --git a/lispref/debugging.texi b/lispref/debugging.texi
index cc3fc7a9bd9d9261da033fa2acbf73ba58bd3d03..e98adaa22e47a63dd4157d9d3aca7ffbedcbdaeb 100644 (file)
--- a/lispref/debugging.texi
+++ b/lispref/debugging.texi
@@ -216,10 +216,10 @@ When @code{debug-on-entry} is called interactively, it prompts for
 up to invoke the debugger on entry, @code{debug-on-entry} does nothing.
 @code{debug-on-entry} always returns @var{function-name}.
 
-@strong{Note:} if you redefine a function after using
-@code{debug-on-entry} on it, the code to enter the debugger is discarded
-by the redefinition.  In effect, redefining the function cancels
-the break-on-entry feature for that function.
+@strong{Warning:} if you redefine a function after using
+@code{debug-on-entry} on it, the code to enter the debugger is
+discarded by the redefinition.  In effect, redefining the function
+cancels the break-on-entry feature for that function.
 
 @example
 @group

diff --git a/lispref/eval.texi b/lispref/eval.texi
index 5a9cb6117e2c48fec5d915c48f5b3a1abfbb22c4..165889e75ed387dcc22d30dcf592858fa27f2fed 100644 (file)
--- a/lispref/eval.texi
+++ b/lispref/eval.texi
@@ -588,11 +588,11 @@ property list.  On these occasions, use the @code{eval} function.
 specify limits to the evaluation process, or record recently returned
 values.  Loading a file also does evaluation (@pxref{Loading}).
 
-  @strong{Note:} it is generally cleaner and more flexible to store a
-function in a data structure, and call it with @code{funcall} or
-@code{apply}, than to store an expression in the data structure and
-evaluate it.  Using functions provides the ability to pass information
-to them as arguments.
+  It is generally cleaner and more flexible to store a function in a
+data structure, and call it with @code{funcall} or @code{apply}, than
+to store an expression in the data structure and evaluate it.  Using
+functions provides the ability to pass information to them as
+arguments.
 
 @defun eval form
 This is the basic function evaluating an expression.  It evaluates

diff --git a/lispref/loading.texi b/lispref/loading.texi
index 752f0bcf7a4225dc5ec319871197d276190c0ed3..71ae09284a8ed38ed62c3652dc70345d500e736e 100644 (file)
--- a/lispref/loading.texi
+++ b/lispref/loading.texi
@@ -148,9 +148,9 @@ The function should accept one argument, just as @code{read} does.
 Normally, the variable's value is @code{nil}, which means those
 functions should use @code{read}.
 
-@strong{Note:} Instead of using this variable, it is cleaner to use
-another, newer feature: to pass the function as the @var{read-function}
-argument to @code{eval-region}.  @xref{Eval}.
+Instead of using this variable, it is cleaner to use another, newer
+feature: to pass the function as the @var{read-function} argument to
+@code{eval-region}.  @xref{Eval}.
 @end defvar
 
   For information about how @code{load} is used in building Emacs, see

diff --git a/lispref/minibuf.texi b/lispref/minibuf.texi
index 0e455a446e731ae90b00dafaeacabd03d6aa571c..114942ed78730edefcb8d5d0118d03e460c0ff8e 100644 (file)
--- a/lispref/minibuf.texi
+++ b/lispref/minibuf.texi
@@ -1110,12 +1110,13 @@ initial input.  It defaults to the current buffer's value of
 @code{default-directory}.
 
 @c Emacs 19 feature
-If you specify @var{initial}, that is an initial file name to insert in
-the buffer (after @var{directory}, if that is inserted).  In this
+If you specify @var{initial}, that is an initial file name to insert
+in the buffer (after @var{directory}, if that is inserted).  In this
 case, point goes at the beginning of @var{initial}.  The default for
 @var{initial} is @code{nil}---don't insert any file name.  To see what
-@var{initial} does, try the command @kbd{C-x C-v}.  @strong{Note:} we
-recommend using @var{default} rather than @var{initial} in most cases.
+@var{initial} does, try the command @kbd{C-x C-v}.  @strong{Please
+note:} we recommend using @var{default} rather than @var{initial} in
+most cases.
 
 If @var{predicate} is non-@code{nil}, it specifies a function of one
 argument that decides which file names are acceptable completion

diff --git a/lispref/text.texi b/lispref/text.texi
index 77a457cadd8b3b9bbd03f0bb268f48994b57cbe5..25a4c978fb90f22aba56eb372b61797f6566a3a8 100644 (file)
--- a/lispref/text.texi
+++ b/lispref/text.texi
@@ -3936,7 +3936,7 @@ made within the @code{combine-after-change-calls} body.
 @code{after-change-functions} within
 the body of a @code{combine-after-change-calls} form.
 
-@strong{Note:} If the changes you combine occur in widely scattered
+@strong{Warning:} if the changes you combine occur in widely scattered
 parts of the buffer, this will still work, but it is not advisable,
 because it may lead to inefficient behavior for some change hook
 functions.

diff --git a/lispref/variables.texi b/lispref/variables.texi
index 0a99b1c110f1cf48acf23375738c5e0774c0d92b..ab5e99e506c86cbfbeb2e68dbe9dcb6f945af4f0 100644 (file)
--- a/lispref/variables.texi
+++ b/lispref/variables.texi
@@ -1281,9 +1281,9 @@ If the variable is terminal-local, this function signals an error.  Such
 variables cannot have buffer-local bindings as well.  @xref{Multiple
 Displays}.
 
-@strong{Note:} Do not use @code{make-local-variable} for a hook
-variable.  The hook variables are automatically made buffer-local
-as needed if you use the @var{local} argument to @code{add-hook} or
+@strong{Warning:} do not use @code{make-local-variable} for a hook
+variable.  The hook variables are automatically made buffer-local as
+needed if you use the @var{local} argument to @code{add-hook} or
 @code{remove-hook}.
 @end deffn