doc/concepts.tex: Don't highlight `primary' as literal, because it's not.

diff --git a/doc/concepts.tex b/doc/concepts.tex
index 89dcd8f3593a541117aff01fc6a8b28745935919..b8cdfe9ee6c6e208e9b23820055ac22ccc78b8eb 100644 (file)
--- a/doc/concepts.tex
+++ b/doc/concepts.tex
@@ -541,7 +541,7 @@ defining $N$.
 The default method combination is called the \emph{standard method
 combination}; other method combinations are useful occasionally for special
 effects.  The standard method combination accepts four direct method roles,
-called @|primary| (the default), @|before|, @|after|, and @|around|.
+called `primary' (the default), @|before|, @|after|, and @|around|.
 
 All direct methods subject to the standard method combination must have
 argument lists which \emph{match} the message's argument list:
@@ -615,7 +615,7 @@ A typical use for @|around| methods is to allow a base class to set up the
 dynamic environment appropriately for the primary methods of its subclasses,
 e.g., by claiming a lock, and restore it afterwards.
 
-The @|next_method| function provided to methods with the @|primary| and
+The @|next_method| function provided to methods with the primary and
 @|around| roles accepts the same arguments, and returns the same type, as the
 message, except that one or two additional arguments are inserted at the
 front of the argument list.  The first additional argument is always the
@@ -626,7 +626,7 @@ second additional argument; otherwise, In the former case, a variable
 of the argument pointer (so the method body can process the variable argument
 suffix itself, and still pass a fresh copy on to the next method).
 
-A method with the @|primary| or @|around| role may use the convenience macro
+A method with the primary or @|around| role may use the convenience macro
 @|CALL_NEXT_METHOD|, which takes no arguments itself, and simply calls
 @|next_method| with appropriate arguments: the receiver @|me| pointer, the
 argument pointer @|sod__master_ap| (if applicable), and the method's