Minor cleanup.
diff --git a/Doc/lib/libbastion.tex b/Doc/lib/libbastion.tex
index 15bb029..7a4f932 100644
--- a/Doc/lib/libbastion.tex
+++ b/Doc/lib/libbastion.tex
@@ -1,8 +1,9 @@
\section{\module{Bastion} ---
- Providing restricted access to objects.}
-\declaremodule{standard}{Bastion}
+ Restricting access to objects}
+\declaremodule{standard}{Bastion}
\modulesynopsis{Providing restricted access to objects.}
+\moduleauthor{Barry Warsaw}{bwarsaw@python.org}
% I'm concerned that the word 'bastion' won't be understood by people
@@ -13,9 +14,9 @@
position'', or ``something that is considered a stronghold.'' It's a
suitable name for this module, which provides a way to forbid access
to certain attributes of an object. It must always be used with the
-\module{rexec} module, in order to allow restricted-mode programs access
-to certain safe attributes of an object, while denying access to
-other, unsafe attributes.
+\refmodule{rexec} module, in order to allow restricted-mode programs
+access to certain safe attributes of an object, while denying access
+to other, unsafe attributes.
% I've punted on the issue of documenting keyword arguments for now.
@@ -30,7 +31,7 @@
containing an attribute name, and returns true if access to that
attribute will be permitted; if \var{filter} returns false, the access
is denied. The default filter denies access to any function beginning
-with an underscore (\samp{_}). The bastion's string representation
+with an underscore (\character{_}). The bastion's string representation
will be \samp{<Bastion for \var{name}>} if a value for
\var{name} is provided; otherwise, \samp{repr(\var{object})} will be
used.