diff options
Diffstat (limited to 'Master/texmf-dist/source/latex-dev/base/ltsockets.dtx')
-rw-r--r-- | Master/texmf-dist/source/latex-dev/base/ltsockets.dtx | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/Master/texmf-dist/source/latex-dev/base/ltsockets.dtx b/Master/texmf-dist/source/latex-dev/base/ltsockets.dtx index 243963f7bcc..c77c74b57f2 100644 --- a/Master/texmf-dist/source/latex-dev/base/ltsockets.dtx +++ b/Master/texmf-dist/source/latex-dev/base/ltsockets.dtx @@ -33,7 +33,7 @@ %<*driver> % \fi \ProvidesFile{ltsockets.dtx} - [2024/02/11 v0.9a LaTeX Kernel (Sockets)] + [2024/06/29 v0.9a LaTeX Kernel (Sockets)] % \iffalse % \documentclass{l3doc} @@ -87,7 +87,7 @@ % executing code for each command or environment in the document % source. Through various steps this code transforms the input and % eventually generates typeset output appearing in a \enquote{galley} -% from which individual pages are cut off in an asyncronous way. This +% from which individual pages are cut off in an asynchronous way. This % page generating process is normally not directly associated with % commands in the input\footnote{Excepts for directives such as % \cs{newpage}.} but is triggered whenever the galley has received @@ -208,7 +208,7 @@ % simply calls some instance that implements the logic and that instance % is altered by selecting a different templates and/or adjusting their % parameters. However, in many cases customization through parameters is -% overkill in such a case (or otherwise awkward, because paramerization +% overkill in such a case (or otherwise awkward, because parameterization % is better done on a higher level instead of individually for small % blocks of code) and using the template mechanism just to replace one % block of code with a different one results in a fairly high @@ -400,7 +400,7 @@ % % However, there is no requirement that sockets and % hook names have to be different. In fact, if a certain action that -% could overwise be specified as hook code has to be executed always +% could otherwise be specified as hook code has to be executed always % last (or first) one could ensure this by placing a socket (single % action) after a hook (or vice versa) and using the same name to % indicate the relationship, e.g., |