Some semantic fixes.
diff --git a/Doc/lib/compiler.tex b/Doc/lib/compiler.tex
index f0926e7..d4f4124 100644
--- a/Doc/lib/compiler.tex
+++ b/Doc/lib/compiler.tex
@@ -103,8 +103,7 @@
construct. The root of the tree is \class{Module} object.
The abstract syntax offers a higher level interface to parsed Python
-source code. The \ulink{\module{parser}}
-{http://www.python.org/doc/current/lib/module-parser.html}
+source code. The \refmodule{parser}
module and the compiler written in C for the Python interpreter use a
concrete syntax tree. The concrete syntax is tied closely to the
grammar description used for the Python parser. Instead of a single
diff --git a/Doc/lib/email.tex b/Doc/lib/email.tex
index ea12705..0f49f8a 100644
--- a/Doc/lib/email.tex
+++ b/Doc/lib/email.tex
@@ -239,7 +239,7 @@
The \module{email} package was originally prototyped as a separate
library called
-\ulink{\module{mimelib}}{http://mimelib.sf.net/}.
+\ulink{\texttt{mimelib}}{http://mimelib.sf.net/}.
Changes have been made so that
method names are more consistent, and some methods or modules have
either been added or removed. The semantics of some of the methods
diff --git a/Doc/lib/libwinreg.tex b/Doc/lib/libwinreg.tex
index 365fd32..4dae883 100644
--- a/Doc/lib/libwinreg.tex
+++ b/Doc/lib/libwinreg.tex
@@ -151,7 +151,7 @@
An application should only call \function{FlushKey()} if it requires absolute
certainty that registry changes are on disk.
- \emph{If you don't know whether a \function{FlushKey()} call is required, it
+ \note{If you don't know whether a \function{FlushKey()} call is required, it
probably isn't.}
\end{funcdesc}