- add version annotation for HIGHEST_PROTOCOL

- cleaned up some markup

diff --git a/Doc/lib/libpickle.tex b/Doc/lib/libpickle.tex
index cd184f493c485ab8aa5fed81245fd6cc343c4f68..aee148e328c7f96095ae990f76de73866ee746f8 100644 (file)
--- a/Doc/lib/libpickle.tex
+++ b/Doc/lib/libpickle.tex
@@ -164,6 +164,7 @@ following constant:
 \begin{datadesc}{HIGHEST_PROTOCOL}
 The highest protocol version available.  This value can be passed
 as a \var{protocol} value.
+\versionadded{2.3}
 \end{datadesc}
 
 The \module{pickle} module provides the
@@ -253,14 +254,13 @@ including (but not necessarily limited to) \exception{AttributeError},
 \exception{EOFError}, \exception{ImportError}, and \exception{IndexError}.
 \end{excdesc}
 
-The \module{pickle} module also exports two callables\footnote{In the
+The \module{pickle} module also exports two callables,\footnote{In the
 \module{pickle} module these callables are classes, which you could
-subclass to customize the behavior.  However, in the \module{cPickle}
-modules these callables are factory functions and so cannot be
-subclassed.  One of the common reasons to subclass is to control what
-objects can actually be unpickled.  See section~\ref{pickle-sub} for
-more details.}, \class{Pickler} and
-\class{Unpickler}:
+subclass to customize the behavior.  However, in the
+\refmodule{cPickle} module these callables are factory functions and
+so cannot be subclassed.  One common reason to subclass is to control
+what objects can actually be unpickled.  See section~\ref{pickle-sub}
+for more details.} \class{Pickler} and \class{Unpickler}:
 
 \begin{classdesc}{Pickler}{file\optional{, protocol\optional{, bin}}}
 This takes a file-like object to which it will write a pickle data