[latex3-commits] [git/LaTeX3-latex3-latex2e] master: spelling and other minor adjustments (1b8dc87)

[David Carlisle]

Repository : https://github.com/latex3/latex2e
On branch  : master
Link       : https://github.com/latex3/latex2e/commit/1b8dc87e10b10ab0d3d0b6758d18cf3c28300572

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

commit 1b8dc87e10b10ab0d3d0b6758d18cf3c28300572
Author: David Carlisle <d.p.carlisle at gmail.com>
Date:   Sat Mar 31 18:39:32 2018 +0100

    spelling and other minor adjustments


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

1b8dc87e10b10ab0d3d0b6758d18cf3c28300572
 doc/ltnews28.tex |   13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/doc/ltnews28.tex b/doc/ltnews28.tex
index 97a7eaf..13a785f 100644
--- a/doc/ltnews28.tex
+++ b/doc/ltnews28.tex
@@ -95,7 +95,7 @@ all. For example to obtain an ``\"a'' one would enter \verb=\"a=, and to
 typeset a ``\ss'' the command \verb=\ss=. Furthermore fonts at that
 time had 128 glyphs inside, holding the \acro{ascii} characters, some
 accents to build composite glyphs from a letter and an accent, and a
-few special symbols such as parantheses, etc.
+few special symbols such as parentheses, etc.
 
 With 8-bit \TeX{} engines such as \hologo{pdfTeX} this situation changed
 somewhat: it was now possible to process 8-bit files, i.e., files that
@@ -103,7 +103,7 @@ could encode 256 different characters. However, 256 is still a fairly
 small number and with this limitation it is only possible to encode a
 few languages and for other languages one would need to change the
 encoding (i.e., interpret the character positions 0--255 in a
-different way). The first code points 0--127 where essentially normed
+different way). The first code points 0--127 were essentially normed
 (corresponding to \acro{ascii}) while the second half 128--255 would
 vary by holding different accented characters to support a certain set
 of languages.
@@ -114,13 +114,13 @@ files and as long as two computers used the same encoding it was
 interpreted and processed correctly.
 
 But different computers may have used different encodings and given
-that a computer file is simply a sequence of bytes with no indication for
-which encoding is was destined chaos could easily happen and
+that a computer file is simply a sequence of bytes with no indication
+which encoding is intended, chaos could easily happen and
 happened. For example, the German word ``Gr\"o\ss e'' (height) entered on a
 German keyboard could show up as ``Gr\v T\`ae'' on a diferent
 computer using a different encoding by default.
 
-So in summmary the situation wasn't at all well and it was clear in
+So in summmary the situation wasn't at all good and it was clear in
 the early nienties that \LaTeXe{} (that was being developed to provide
 a \LaTeX{} version usable across the world) had to provide a solution
 to this issue.
@@ -244,7 +244,8 @@ earlier than this release.
   website~\cite{Mittelbach:TB39-2}.
 
 
-\section{Integration of \pkg{remreset} and \pkg{chngcntr} packages 
+\section[Integration of \pkg{remreset} and \pkg{chngcntr} packages]
+         {Integration of \pkg{remreset} and \pkg{chngcntr} packages 
          into the kernel}
 
 With the optional argument to \cs{newcounter} \LaTeX{} offers to