[latex3-commits] [git/LaTeX3-latex3-latex2e] marks-debug: a bit documentation cleanup along the way (777b5e74)

[Frank Mittelbach]

Repository : https://github.com/latex3/latex2e
On branch  : marks-debug
Link       : https://github.com/latex3/latex2e/commit/777b5e741635885c60cfebef1d0f49e7caf61d01

>---------------------------------------------------------------

commit 777b5e741635885c60cfebef1d0f49e7caf61d01
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date:   Thu Apr 14 11:04:49 2022 +0200

    a bit documentation cleanup along the way


>---------------------------------------------------------------

777b5e741635885c60cfebef1d0f49e7caf61d01
 base/ltmarks.dtx | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/base/ltmarks.dtx b/base/ltmarks.dtx
index e1f3096e..a076ecd8 100644
--- a/base/ltmarks.dtx
+++ b/base/ltmarks.dtx
@@ -165,7 +165,7 @@
 %
 %   If used in vertical mode it obeys \LaTeX{}'s internal
 %   \texttt{@nobreak} switch, i.e., it does not introduce a
-%   breakbpoint if used after a heading. If used in horizontal mode it
+%   breakpoint if used after a heading. If used in horizontal mode it
 %   doesn't handle spacing (like, for example, \cs{index} or
 %   \cs{label} does, so it should be attached to material that is
 %   typeset.
@@ -326,13 +326,13 @@
 %
 %
 %
-% \subsubsection{Debugging mark code}
+% \subsection{Debugging mark code}
 %
 %
-% \begin{function}{\DebugsMarksOn,\DebugMarksOff,
+% \begin{function}{\DebugMarksOn,\DebugMarksOff,
 %                  \mark_debug_on:,\mark_debug_off:}
 %   \begin{syntax}
-%     \cs{DebugsMarksOn} ...  \cs{DebugMarksOff}
+%     \cs{DebugMarksOn} ...  \cs{DebugMarksOff}
 %   \end{syntax}
 %
 %    Commands to turn the debugging of mark code on or off. The
@@ -415,10 +415,10 @@
 %   can't be shown using this interface.
 %
 %   The commands are fully expandable, because this is how they have
-%   been always defined in \LaTeX{}. However, this is , of course,
+%   been always defined in \LaTeX{}. However, this is of course
 %   only true if the content of the mark they return is itself
 %   expandable and does not contain any fragile material. Given that
-%   this can't be guranteed for arbitrary content a programmer using
+%   this can't be guaranteed for arbitrary content, a programmer using
 %   them in this way should use \cs{protected at edef} and \emph{not}
 %   \cs{edef} to avoid bad surprises as far as this is possible.
 % \end{function}
@@ -1162,7 +1162,7 @@
 %
 %
 %
-% \subsection{Tracing the mark structures}
+% \subsection{Debugging the mark structures}
 %    
 %  Code and commands in this section are not final, it needs more
 %  experimentation to see what kind of tracing information is going to
@@ -1209,10 +1209,10 @@
 %
 %    
 %  \begin{macro}{\DebugMarksOn,\DebugMarksOff}
-%
+%    CamelCase commands for debugging.
 %    \begin{macrocode}
-\cs_new_protected:Npn \DebugMarksOn  { \mark_debug_on:  }
-\cs_new_protected:Npn \DebugMarksOff { \mark_debug_off: }
+\cs_new_eq:NN \DebugMarksOn   \mark_debug_on: 
+\cs_new_eq:NN \DebugMarksOff  \mark_debug_off:
 %    \end{macrocode}
 %  \end{macro}
 %
@@ -1340,7 +1340,7 @@
 %    \texttt{previous-page}.
 %
 %    The \cs{@outputbox} is normally in \cs{vbox} in \LaTeX{} but we
-%    can't take that for granted (an \texttt{amsmath} test document
+%    can't take that for granted (an \pkg{amsmath} test document
 %    changed it to an \cs{hbox} just to trip me up) so we are a little
 %    careful with unpack now.
 %    \begin{macrocode}
@@ -1509,7 +1509,7 @@
 %    We keep the interface commands around even if we roll back in
 %    case they are used in packages that don't roll back. Not likely
 %    to do a lot of good, but then there is not much we can do, but
-%    this at least then goesn't give errors.
+%    this at least then doesn't give errors.
 %    \begin{macrocode}
 %<latexrelease>\DeclareRobustCommand \NewMarkClass[1]{}
 %<latexrelease>\DeclareRobustCommand \InsertMark[2]{}