* Minor wording change
* Reference the doctest.DocTestSuite() conversion tool.
diff --git a/Doc/lib/libunittest.tex b/Doc/lib/libunittest.tex
index 5350edc..b5976c6 100644
--- a/Doc/lib/libunittest.tex
+++ b/Doc/lib/libunittest.tex
@@ -91,7 +91,7 @@
\end{seealso}
-\subsection{Minimal example \label{minimal-example}}
+\subsection{Basic example \label{minimal-example}}
The \module{unittest} module provides a rich set of tools for
constructing and running tests. This section demonstrates that a
@@ -387,7 +387,7 @@
\end{verbatim}
You can place the definitions of test cases and test suites in the
-same modules as the code they are to test (e.g.\ \file{widget.py}),
+same modules as the code they are to test (such as \file{widget.py}),
but there are several advantages to placing the test code in a
separate module, such as \file{widgettests.py}:
@@ -516,6 +516,12 @@
\end{verbatim}
\end{funcdesc}
+In some cases, the existing tests may have be written using the
+\module{doctest} module. If so, that module provides a
+\class{DocTestSuite} class that can automatically build
+\class{unittest.TestSuite} instances from the existing test code.
+\versionadded{2.3}
+
\subsection{TestCase Objects
\label{testcase-objects}}