[latex3-commits] [latex3/latex2e] latexlab/rcb: Typos (8d28afcb)

[github at latex-project.org]

Repository : https://github.com/latex3/latex2e
On branch  : latexlab/rcb
Link       : https://github.com/latex3/latex2e/commit/8d28afcbe3cc064f9036f2248ab2c7d82c9bfc48

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

commit 8d28afcbe3cc064f9036f2248ab2c7d82c9bfc48
Author: PhelypeOleinik <phelype.oleinik at latex-project.org>
Date:   Fri Jul 28 00:47:49 2023 -0300

    Typos


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

8d28afcbe3cc064f9036f2248ab2c7d82c9bfc48
 required/latex-lab/latex-lab-new-or-2.dtx |  2 +-
 required/latex-lab/socket-sample.tex      | 12 ++++++------
 2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/required/latex-lab/latex-lab-new-or-2.dtx b/required/latex-lab/latex-lab-new-or-2.dtx
index 9ecd54c7..fb06f8e0 100644
--- a/required/latex-lab/latex-lab-new-or-2.dtx
+++ b/required/latex-lab/latex-lab-new-or-2.dtx
@@ -79,7 +79,7 @@
 %
 %      Prior to calling the socket the output routine has already
 %      decided which floats go into which area and which get deferred.
-%      Therefore, the assumtion is that the code in the socket attaches all
+%      Therefore, the assumption is that the code in the socket attaches all
 %      areas that contain floats. If this is not done, then the order
 %      of floats is likely to be screwed up unless unused floats
 %      are moved to the defer list in an appropriate way (for now we
diff --git a/required/latex-lab/socket-sample.tex b/required/latex-lab/socket-sample.tex
index 9b26bb75..a1eea2c2 100644
--- a/required/latex-lab/socket-sample.tex
+++ b/required/latex-lab/socket-sample.tex
@@ -258,7 +258,7 @@ or, if the socket takes a number of arguments with
 In addition, one or several named chunks of code implementing different logic for this
 socket are set up, each with a declaration of the form:
 \begin{quote}
-  \cs{DeclareSocketCode}\marg{socket-name}\marg{chunk-name}\marg{code})
+  \cs{DeclareSocketCode}\marg{socket-name}\marg{chunk-name}\marg{code}
 \end{quote}
 Finally,
 one of them is assigned to the socket:
@@ -286,8 +286,8 @@ By the way:
 \item
   should it be \texttt{gassign} ? or some other verb?
 \item
-  And what about \cs{socket\_use:n} ? Should that be \texttt{:nw}
-  as wedon't really control the arguments or should we have
+  And what about \cs{socket\_use:n}? Should that be \texttt{:nw}
+  as we don't really control the arguments or should we have
   \cs{socket\_use:nn}, \cs{socket\_use:nnn}, \ldots, just to make it
   clearer how many arguments are (supposed to be) picked up?
 \end{itemize}
@@ -297,7 +297,7 @@ By the way:
 
 \section{Example and testing}
 
-From here on we scroll through errors because the example expliitly generate a few:
+From here on we scroll through errors because the example explicitly generate a few:
 \begin{verbatim}
   \scrollmode
 \end{verbatim}
@@ -390,8 +390,8 @@ because there is no dedicated runtime check that \texttt{fou} is a known socket.
 
 The reason is that if the misspelling is in the code, then this is a
 programming error in the package and for speed reasons \LaTeX{} does
-not repeately make runtime checks for coding errors unless they can or
-are likely to be user introduced.
+not repeatedly make runtime checks for coding errors unless they can or
+are likely to be user-introduced.
 
 \subsection{Performance}