[latex3-commits] [git/LaTeX3-latex3-latex2e] develop: fix couple of typos [ci skip] (45fb4e03)

[Frank Mittelbach]

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

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

commit 45fb4e03aa5494215c9b06e8ffd6f87e84557f72
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date:   Sat Feb 5 15:50:17 2022 +0100

    fix couple of typos [ci skip]


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

45fb4e03aa5494215c9b06e8ffd6f87e84557f72
 base/doc/ltnews35.tex | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/base/doc/ltnews35.tex b/base/doc/ltnews35.tex
index e798d4c2..d4daf171 100644
--- a/base/doc/ltnews35.tex
+++ b/base/doc/ltnews35.tex
@@ -193,7 +193,7 @@ and also in the documentation of the \pkg{pdfmanagement-testphase} package.
 
 \section{New or improved commands}
 
-\subsection{A kevyal approach to option handling}
+\subsection{A keyval approach to option handling}
 
 The classical \LaTeXe{} method for handling options, using \cs{ProcessOptions},
 treats each entry in the list as a string. Many package authors have sought to
@@ -217,7 +217,7 @@ unless explicitly given as an optional argument.
 A version which does not consider global options,
 \cs{ProcessKeyPackageOptions}, is also available.
 
-To support creating key options in for this mechanism, the new command
+To support creating key options for this mechanism, the new command
 \cs{DeclareKeys} has been added. This works using the same general
 approach as \pkg{l3keys} or \pkg{pgfkeys}: each key has one or more
 \emph{properties} which define its behavior.
@@ -455,7 +455,7 @@ in the range U+01C4 to U+01CC.
 
 When declaring encoding specific commands for the Unicode (TU)
 encoding some declarations (e.g., \cs{DeclareUnicodeComposite}) do not
-have an explicit argument for the the encoding name, but instead use
+have an explicit argument for the encoding name, but instead use
 the command \cs{UnicodeEncodingName} internally. There was one
 exception though: \cs{DeclareUnicodeAccent} required an explicit
 encoding argument.  This inconsistency has now been removed and the