* doc/lispref/functions.texi (Advising Functions): Tweak markup.

diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index b7148b921865eb766c86cb2ef89cc9634baed1d2..40a07339b2f2804ec90d617713a7e3f22852d584 100644 (file)
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -1,5 +1,7 @@
 2014-02-28  Xue Fuqiao  <xfq@gnu.org>
 
+       * functions.texi (Advising Functions): Tweak markup.
+
        * display.texi (Defining Faces): Doc fix for `face-spec-set'.
 
        * elisp.texi (Top):

diff --git a/doc/lispref/functions.texi b/doc/lispref/functions.texi
index b38eab2649af823aa4de4034a10f166806f695a4..cd7131564ea29cd0fc65cbead4709290c44909d4 100644 (file)
--- a/doc/lispref/functions.texi
+++ b/doc/lispref/functions.texi
@@ -1170,9 +1170,9 @@ there are many different ways to do it.  The added function is also called an
 @emph{advice}.
 
 The function cell of a symbol can be manipulated similarly, but since it can
-contain other things than a plain function, you have to use @var{advice-add}
-and @var{advice-remove} instead, which
-@c use @var{add-function} and @var{remove-function} internally, but
+contain other things than a plain function, you have to use @code{advice-add}
+and @code{advice-remove} instead, which
+@c use @code{add-function} and @code{remove-function} internally, but
 know how to handle cases such as when the function cell holds a macro rather
 than function, or when the function is autoloaded so the advice's activation
 needs to be postponed.