Use \citetitle and \programopt as appropriate.
diff --git a/Doc/lib/libstdtypes.tex b/Doc/lib/libstdtypes.tex
index 39c9290..6ae216b 100644
--- a/Doc/lib/libstdtypes.tex
+++ b/Doc/lib/libstdtypes.tex
@@ -302,14 +302,14 @@
There are three sequence types: strings, lists and tuples.
Strings literals are written in single or double quotes:
-\code{'xyzzy'}, \code{"frobozz"}. See Chapter 2 of the \emph{Python
-Reference Manual} for more about string literals. Lists are
-constructed with square brackets, separating items with commas:
-\code{[a, b, c]}. Tuples are constructed by the comma operator (not
-within square brackets), with or without enclosing parentheses, but an
-empty tuple must have the enclosing parentheses, e.g.,
-\code{a, b, c} or \code{()}. A single item tuple must have a trailing
-comma, e.g., \code{(d,)}.
+\code{'xyzzy'}, \code{"frobozz"}. See Chapter 2 of the
+\citetitle[../ref/ref.html]{Python Reference Manual} for more about
+string literals. Lists are constructed with square brackets,
+separating items with commas: \code{[a, b, c]}. Tuples are
+constructed by the comma operator (not within square brackets), with
+or without enclosing parentheses, but an empty tuple must have the
+enclosing parentheses, e.g., \code{a, b, c} or \code{()}. A single
+item tuple must have a trailing comma, e.g., \code{(d,)}.
\indexii{sequence}{types}
\indexii{string}{type}
\indexii{tuple}{type}
@@ -629,7 +629,8 @@
\subsubsection{Classes and Class Instances \label{typesobjects}}
\nodename{Classes and Instances}
-See Chapters 3 and 7 of the \emph{Python Reference Manual} for these.
+See Chapters 3 and 7 of the \citetitle[../ref/ref.html]{Python
+Reference Manual} for these.
\subsubsection{Functions \label{typesfunctions}}
@@ -667,7 +668,8 @@
calling \code{\var{m}.im_func(\var{m}.im_self, \var{arg-1},
\var{arg-2}, \textrm{\ldots}, \var{arg-n})}.
-See the \emph{Python Reference Manual} for more information.
+See the \citetitle[../ref/ref.html]{Python Reference Manual} for more
+information.
\subsubsection{Code Objects \label{bltin-code-objects}}
@@ -689,7 +691,8 @@
\stindex{exec}
\bifuncindex{eval}
-See the \emph{Python Reference Manual} for more information.
+See the \citetitle[../ref/ref.html]{Python Reference Manual} for more
+information.
\subsubsection{Type Objects \label{bltin-type-objects}}
@@ -715,9 +718,10 @@
\subsubsection{The Ellipsis Object \label{bltin-ellipsis-object}}
-This object is used by extended slice notation (see the \emph{Python
-Reference Manual}). It supports no special operations. There is
-exactly one ellipsis object, named \code{Ellipsis} (a built-in name).
+This object is used by extended slice notation (see the
+\citetitle[../ref/ref.html]{Python Reference Manual}). It supports no
+special operations. There is exactly one ellipsis object, named
+\constant{Ellipsis} (a built-in name).
It is written as \code{Ellipsis}.
@@ -868,9 +872,9 @@
\subsubsection{Internal Objects \label{typesinternal}}
-See the \emph{Python Reference Manual} for this information. It
-describes code objects, stack frame objects, traceback objects, and
-slice objects.
+See the \citetitle[../ref/ref.html]{Python Reference Manual} for this
+information. It describes code objects, stack frame objects,
+traceback objects, and slice objects.
\subsection{Special Attributes \label{specialattrs}}