Diff from to

# File py-and-sty.dtx

 \ST@pausedfalse
 %    \end{macrocode}
 % Set up the file stuff, which will get run at the beginning of the
-% document, after we know what's happening with the |final| option.
+% document, after we know what's happening with the |final| option.
 % First, we open the |.sage| file:
 %    \begin{macrocode}
 \AtBeginDocument{\@ifundefined{ST@final}{%
 %    \end{macrocode}
 % \end{macro}
 %
-% \begin{macro}{\percent}
+% \begin{macro}{\percent}
 % A macro that inserts a percent sign. This is more-or-less stolen from the
 % \textsf{Docstrip} manual; there they change the catcode inside a group
 % and use |gdef|, but here we try to be more \LaTeX y and use
 %\end{center}
 % Observe that we are using a Python script to write \LTX code which
 % writes Python code which writes \LTX code. Crazy!
-%
+%
 % Here's the wrapper command which does whatever magic we need to get
 % two optional arguments.
 %    \begin{macrocode}
      \gdef\ST@rerun{x}}
 \fi}
 %    \end{macrocode}
-% \autoref{f:stig} makes this a bit clearer.
+% \autoref{f:stig} makes this a bit clearer.
 % \begin{figure}
 %   \centering
 %   \begin{tikzpicture}
 % \end{macro}
 %
 % \begin{macro}{\ST@endsfbl}
-% The companion to |\ST@beginsfbl|.
+% The companion to |\ST@beginsfbl|.
 %    \begin{macrocode}
 \newcommand{\ST@endsfbl}{%
 \ST@wsf{except:^^J
   def blockend(self):
     self.progress('end')
 %    \end{macrocode}
-% \end{macro}
-% \end{macro}
+% \end{macro}
+% \end{macro}
 %
 % \begin{macro}{plot}
 % \phantomsection\label{plotfn}
 % \end{macro}
 %
 % \begin{macro}{goboom}
+% \phantomsection\label{macro:goboom}
 % When a chunk of Sage code blows up, this function bears the bad news
 % to the user. Normally in Python the traceback is good enough for
 % this, but in this case, we start with a |.sage| file (which is
 % \#2861}.
 % \changes{v2.0.2}{2008/04/21}{Make sure sys.exit sees a Python integer}
 % \end{macro}
-%
+%
 % \begin{macro}{endofdoc}
 % When we're done processing, we have some cleanup tasks. We
 % want to put the MD5 sum of the |.sage| file that produced the |.sout|
 % changed.
 %
 % How do we include line numbers for our error messages but still allow
-% a program to discover a genuine'' change to the |.sage| file?
+% a program to discover a genuine'' change to the |.sage| file?
 %
 % The answer is to only find the MD5 sum of \emph{part} of the |.sage|
 % file. By design, the source file line numbers only appear in calls to

 % \endinput
 %</python>
-% Local Variables:
+% Local Variables:
 % mode: doctex
 % TeX-master: "sagetexpackage"
-% End:
+% End: