[latex3-commits] [latex3/latex2e] develop: Fix typos in ltnews (e66d8f38)

[github at latex-project.org]

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

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

commit e66d8f3859315a2c6c57d568fa1a7b57287867be
Author: Joseph Wright <joseph.wright at morningstar2.co.uk>
Date:   Thu May 25 10:33:56 2023 +0100

    Fix typos in ltnews


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

e66d8f3859315a2c6c57d568fa1a7b57287867be
 base/doc/ltnews37.tex | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/base/doc/ltnews37.tex b/base/doc/ltnews37.tex
index c905da3a..5b2a55dd 100644
--- a/base/doc/ltnews37.tex
+++ b/base/doc/ltnews37.tex
@@ -412,9 +412,9 @@ but \emph{after} the \cs{@bsphack} command has done its spacing magic and it is
 
 \subsection{Performance in checking file existence}
 
-The additon of hooks, etc., to file operations had a side-effect in that
+The addition of hooks, etc., to file operations had a side-effect in that
 multiple checks were made that the file existed. In larger documents using
-lots of files, these filesystem operations caused non-trivial performance
+lots of files, these file system operations caused non-trivial performance
 impact. We now cache the existence of files, such that these repeated filesystem
 calls are avoided.
 
@@ -487,7 +487,7 @@ the warning less noisy in this case we added a new \texttt{nowarn} key
 that redirects the overwriting warning to the transcript file. We
 think that some record of the action is still required to help with
 debugging, thus it is not completely silenced. The warning that
-nothing gets written, because the file aready exists (and the
+nothing gets written, because the file already exists (and the
 \texttt{force} key was not used), is not altered and still shows up on
 the terminal.
 %
@@ -565,7 +565,7 @@ group (i.e., any local changes would immediately be revoked, breaking,
 for example, \pkg{wrapfig} in that special situation).
 %
 This got fixed with the 2022-11 PL1 hotfix, so was already corrected in
-the previous release, but only now documented in a newletter.
+the previous release, but only now documented in the newsletter.
 %
 \githubissue{967}
 
@@ -672,7 +672,7 @@ user guide, but both are worth a re-read by experienced \LaTeX{} users.
 
 In some situations it is necessary to find out the exact release dates
 for older version of the \LaTeX{} format, for example, when you need
-to use different code in a package depending on the availablilty of a
+to use different code in a package depending on the availability of a
 certain feature and you therefore want to use
 \cs{IfFormatAtLeastTF}\texttt\{\meta{date}\texttt\} or the
 rather horrible construction \verb/\@ifl at t@r\fmtversion{/\meta{date}\texttt\},
@@ -734,7 +734,7 @@ for the decade to come.
 
 To cover what we thought worth describing today, the book nearly
 doubled in size. The print edition is therefore produced as a
-two-volume set and sold as a bundle. Both volumes come as hardcover
+two-volume set and sold as a bundle. Both volumes come as hard-cover
 with ribbons to easily mark pages in the book.
 
 To give you an idea of what is covered in the third edition you can