[latex3-commits] [latex3/latex2e] develop: doc updates by bb (b6dafe89)

[github at latex-project.org]

Repository : https://github.com/latex3/latex2e
On branch  : develop
Link       : https://github.com/latex3/latex2e/commit/b6dafe892c46a73147d2fe40ba3dfa349841486c

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

commit b6dafe892c46a73147d2fe40ba3dfa349841486c
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date:   Mon Oct 30 19:44:05 2023 +0100

    doc updates by bb


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

b6dafe892c46a73147d2fe40ba3dfa349841486c
 base/doc/ltnews38.tex | 15 +++++++--------
 1 file changed, 7 insertions(+), 8 deletions(-)

diff --git a/base/doc/ltnews38.tex b/base/doc/ltnews38.tex
index 918a2028..aa1f9524 100644
--- a/base/doc/ltnews38.tex
+++ b/base/doc/ltnews38.tex
@@ -193,7 +193,7 @@ which cells are header cells, etc.).
 Having all issues and discussions related to the project in a single
 place instead of being spread across multiple repositories such as
 \texttt{latex2e}, \texttt{latex3}, \texttt{tagpdf}, \texttt{hyperref},
-\texttt{pdfresources}, etc., help people to find information easily
+\texttt{pdfresources}, etc., helps people to find information easily
 and report any issue related to the project without needing to know in which
 code repository the problematic code resides.
 
@@ -230,7 +230,7 @@ below them). But at any time in the document only one such placement
 code can be in force. Or consider the extra code needed for making
 \LaTeX{} documents accessible (e.g., adding tags to the PDF
 output). Such code is either there (perhaps in alternative versions)
-or not at all, but it can not have code from other packages added at
+or not at all, but it cannot have code from other packages added at
 the same point interfering with the algorithm.
 
 For these use cases we now introduce the concept of sockets and plugs.
@@ -286,7 +286,7 @@ representations of the \emph{current page number} and the
 \emph{current \textup{\cs{ref}} value} set by \cs{refstepcounter}
 declarations~\cite[p.~209]{38:Lamport}.  (These declarations are
 issued, for example, by sectioning commands, by numbered environments
-like \env{equation}, and by \cs{item} in an \env{enumerate} or a
+like \env{equation}, and by \cs{item} in an \env{enumerate} or
 similar environment.)
 
 These two recorded values can then be accessed and typeset (from
@@ -430,7 +430,6 @@ the start and end in the format
 L3 programming layer <YYYY-MM-DD>
 \end{verbatim}
 just after the line which identifies the format (\texttt{LaTeX2e}, etc.).
-
 %
 \githubissue{1004}
 
@@ -466,9 +465,9 @@ This will now produce a warning and act like the default \texttt{c} alignment.
 
 Some time ago we revised the definition of active characters in \pdfTeX{} to
 allow the full range of UTF-8 codepoints to be used in for example labels,
-file names, etc. However, |~| was not changed at that point as it is active
-independent of the engine in use. This has how be corrected: the definition
-of |~| is an engine-protected one which gives the string version of the
+file names, etc. However, \verb|~| was not changed at that point as it is active
+independent of the engine in use. This has now been corrected: the definition
+of \verb|~| is an engine-protected one which gives the string version of the
 character if used inside a csname.
 
 
@@ -554,7 +553,7 @@ usage but the package didn't take over a change made 1992 in
 \pkg{array} which adjusted the handling of the strut inserted at the
 begin of p-columns. As a consequence there are a number of
 inconsistencies in the output of p-columns between \pkg{tabular} and
-\pkg{longtable}. This has been corrected, \pkg{longtable} uses now for
+\pkg{longtable}. This has been corrected; \pkg{longtable} now uses for
 the strut the same definition as \pkg{array}.
 %
 \githubissue{1128}