[latex3-commits] [latex3/latex2e] ltmarks-multicol: more doc updates from reviews (9612044db)

[github at latex-project.org]

Repository : https://github.com/latex3/latex2e
On branch  : ltmarks-multicol
Link       : https://github.com/latex3/latex2e/commit/9612044db94f3bc94f263eb11ae8a49a11158663

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

commit 9612044db94f3bc94f263eb11ae8a49a11158663
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date:   Mon Nov 18 11:15:52 2024 +0100

    more doc updates from reviews


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

9612044db94f3bc94f263eb11ae8a49a11158663
 base/doc/ltnews41.tex | 2 +-
 base/ltmarks.dtx      | 6 +++---
 base/ltpage.dtx       | 4 ++--
 base/lttagging.dtx    | 6 +++---
 4 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/base/doc/ltnews41.tex b/base/doc/ltnews41.tex
index 18f21f940..e38df10d8 100644
--- a/base/doc/ltnews41.tex
+++ b/base/doc/ltnews41.tex
@@ -151,7 +151,7 @@
 
 \LaTeX{}'s legacy mechanism only supported two classes (left and right
 marks) and setting the left mark (with \cs{markboth}) always altered
-the state of the right mark as well, i.e., there were far from
+the state of the right mark as well, i.e., they were far from
 independent. For generating running headers with \enquote{chapter
   titles} on the left and \enquote{section titles} on the right they
 work reasonably well but without much flexibility, e.g., \cs{leftmark}
diff --git a/base/ltmarks.dtx b/base/ltmarks.dtx
index 829b5324b..caabd8385 100644
--- a/base/ltmarks.dtx
+++ b/base/ltmarks.dtx
@@ -374,7 +374,7 @@
 %
 %   The situation starts getting rather complex if you allow for
 %   multiple columns the way they are supported by the
-%   \pkg{multicol} package. In that case you might have a varying
+%   \pkg{multicol} package. In this case you might have a variable
 %   number of \enquote{columns} on a single page to be shipped
 %   out. And even if not, then a \env{multicols} might start or end in
 %   the middle of the page; in either case, the regions \texttt{column} and
@@ -389,7 +389,7 @@
 %   more than one \env{multicols} on the current page then in the output routine 
 %   only the columns of the last one will be accessible.
 %
-%   These provisions covers a number of layouts and use cases out of the box, but
+%   These provisions cover, out of the box, a number of layouts and use cases, but
 %   obviously not all. However, more cases can be supported by storing away
 %   mark information during the processing.  Here is the full
 %   algorithm:
@@ -787,7 +787,7 @@
 %    the output routine as well.
 %
 %    It collects all the top-level marks from inside the \meta{source}
-%    and then it adds suitable \cs{mark_insert:nn} in the two token
+%    and then  adds suitable \cs{mark_insert:nn} commands  to each of the two token
 %    lists. These token lists can then be executed at the right place
 %    to reinsert the marks, e.g., directly after the box. This is, for
 %    example, going to be used\footnote{Probably not before 2025, though.}
diff --git a/base/ltpage.dtx b/base/ltpage.dtx
index f474a0f86..25bb5a5a2 100644
--- a/base/ltpage.dtx
+++ b/base/ltpage.dtx
@@ -281,8 +281,8 @@
 %<latexrelease>                 {\markboth}{Make commands robust}%
 %<latexrelease>
 %    \end{macrocode}
-%    Using \cs{kernel at make@fragile} doesn't really work if there a
-%    more redefinitions later on, so we do have to repeat the above
+%    Using \cs{kernel at make@fragile} doesn't really work if there are
+%    more redefinitions later on, so we have to repeat the above
 %    definition first and then undo it (or use \cs{def} directly).
 %    \begin{macrocode}
 %<latexrelease>%\kernel at make@fragile\markboth
diff --git a/base/lttagging.dtx b/base/lttagging.dtx
index f79438147..1196af95f 100644
--- a/base/lttagging.dtx
+++ b/base/lttagging.dtx
@@ -195,8 +195,8 @@
 %
 %    Dummy definitions in the kernel.
 %    These definitions will get updated in \pkg{tagpdf}.
-%    The default in the kernel is just to get rid of the first argument,
-%    the second is preserved if present:
+%    The default in the kernel is simply to get rid of the first argument, while
+%    the second argument is preserved if present:
 % \changes{v1.0k}{2024/10/21}{Changed behavior of two argument tagging sockets when disabled.}
 % \changes{v1.0k}{2024/10/21}{Added expandable variants}
 %    \begin{macrocode}
@@ -542,7 +542,7 @@
 %
 % \begin{socketdecl}{tagsupport/page at sofar}
 %
-%  This socket is declared andused in the \pkg{multicol} output routines.
+%  This socket is declared and used in the \pkg{multicol} output routines.
 %  Only listed for reference.
 %    \begin{macrocode}
 %\NewSocket{tagsupport/page at sofar}{0}