copyedits by bb

base/doc/ltnews35.tex

@@ -151,7 +151,7 @@ \section{Introduction}
 As usual, we also added a number of smaller improvements and bug
 fixes in various components of core \LaTeX{}. Perhaps the most
 interesting ones (for some users) are direct support for floating
-point arithmetic (via \cs{fpeval} see below) and the ability to
+point arithmetic (via \cs{fpeval}; see below) and the ability to
 properly color parts of math formulas without introducing spacing
 problems. For this we now offer the command \cs{mathcolor}; see the
 description near the end of the newsletter.  There is also a new major
@@ -182,14 +182,14 @@ \section{Document metadata interface}
 \cs{documentclass} and will issue an error if found later.
 
 
-At this point in time we only provide the bare command in the format,
+At this point in time we provide only the bare command in the format,
 the actual processing of the key/value is defined externally and the
 necessary code will be loaded if the command is used. This scheme is
 chosen for two reasons: by adding the command in the kernel it is
 available to everybody without the need to load a special package
 using \cs{RequirePackage}. The actual processing, though, is external
 so that we can easily extend the code (e.g., offering additional keys
-or changing the internal processing) while the above mentioned project
+or changing the internal processing) while the above-mentioned project
 is progressing. Both together allows users to immediately benefit from
 intermediate results produced as part of the project, as well as
 offering the \LaTeX{} Project Team the flexibility to enable such
@@ -215,7 +215,7 @@ \section{The \pkg{latex-lab} bundle}
 code that is going to be available only through a
 \cs{DocumentMetadata} declaration and that is\Dash most
 importantly\Dash work under development and subject to
-change without further notice. This means, that commands and interfaces provided there may
+change without further notice. This means that commands and interfaces provided there may
 get altered or removed again after some public testing.  The code can
 be accessed through the \cs{DocumentMetadata} key \texttt{testphase}.
 Currently supported values are \texttt{phase-I} and \texttt{phase-II}
@@ -224,11 +224,11 @@ \section{The \pkg{latex-lab} bundle}
 \begin{verbatim}
   \DocumentMetadata{testphase=phase-II}
 \end{verbatim}
-you currently enable tagging for paragraphs and footnotes, more
+you currently enable tagging for paragraphs and footnotes; more
 document elements will follow soon.
 
 For more detailed testing it is also possible to pass other values to
-\texttt{testphase}, for example, the first incarnation of a template
+\texttt{testphase}; for example, the first incarnation of a template
 design interface based on \pkg{l3keys} can be accessed through the
 value \texttt{prototype}, thus
 \begin{verbatim}
@@ -292,7 +292,7 @@ \section{A new mark mechanism for \LaTeX{}}
   It provides arbitrary many, fully independent named marks, that
   can be allocated and from that point onwards used.
 \item
-  It offers access for each such marks to retrieve its top,
+  It offers access for each such mark to retrieve its top,
   first, and bottom value separately.
 \item
   Furthermore, the mechanism is augmented to give access to marks
@@ -327,10 +327,14 @@ \section{A key/value approach to option handling}
 \ProcessKeyOptions
 \end{verbatim}
 will now automatically pick up the package name as the key \emph{family},
-unless explicitly given as an optional argument.
+%unless explicitly given as an optional argument.
+unless explicitly given as an optional argument:
 \begin{verbatim}
 \ProcessKeyOptions[family]
 \end{verbatim}
+%% bb -- Aren't these both the same?  If "family" is given specifically
+%%       as the option, how does the command without option differ?
+%%       Could be made mor clear.
 
 To support creating key options for this mechanism, the new command
 \cs{DeclareKeys} has been added. This works using the same general
@@ -382,9 +386,11 @@ \subsection{Floating point and integer calculations}
 offers a rich syntax allows for extensive calculations whereas the
 other three commands are essentially thin wrappers for \cs{numexpr},
 \cs{dimexpr}, and \cs{glueexpr} \Dash therefore inheriting some syntax
-peculiars and limitations in expressiveness.
+%peculiars and limitations in expressiveness.
+peculiarities and limitations in expressiveness.
+%  \newcommand\calulateheight[1]{%
 \begin{verbatim}
-  \newcommand\calulateheight[1]{%
+  \newcommand\calculateheight[1]{%
     \setlength\textheight{\dimeval{\topskip
           + \baselineskip * \inteval{#1-1}}}}
 \end{verbatim}
@@ -398,7 +404,7 @@ \subsection{CamelCase commands for changing arguments to csnames}
 
 It is sometimes helpful to \enquote{construct} a command name on the
 fly rather than providing it as a single \cs{...} token. For these
-kind of tasks the \LaTeX3 programming layer offers a general mechanism
+kinds of tasks the \LaTeX3 programming layer offers a general mechanism
 (in form of \cs{exp\_args:N...} and
 \cs{cs\_generate\_variant:Nn}). However, when declaring new
 document-level commands with \cs{NewDocumentCommand} or
@@ -500,12 +506,12 @@ \subsection{Starred command version for \cs{ref}, \cs{Ref} and \cs{pageref}}
 \subsection{Preparation for supporting PDF in backends}
 
 At the current point in time, basic support for PDF in
-backends is not part of \LaTeX{} core; it is provided by external
+backends is not part of \LaTeX{} core; it is provided by an external
 package like \pkg{hyperref}.
 At some time in the future that work will be placed
 into the kernel but for now it is separate and has to be
 explicitly loaded in the document. To enable class and package authors
-to support PDF specific task like the creation of link targets without
+to support PDF-specific tasks like the creation of link targets without
 having to test first if \pkg{hyperref} has been loaded, dummy versions of
 the commands \cs{MakeLinkTarget}, \cs{LinkTargetOn}, \cs{LinkTargetOff} and
 \cs{NextLinkTarget} are provided.
@@ -523,7 +529,7 @@ \subsection{\cs{protected} UTF-8 character definitions}
 \cs{text\string_lowercase:n} in place of the \TeX-primitive \cs{lowercase}.
 A similar change will be made in the \pkg{textcase} package.
 
-Note for technical reasons these low level character handling changes
+Note: for technical reasons these low level character handling changes
 will not be rolled back if the format version is rolled back using the
 \pkg{latexrelease} package rollback mechanism.
 %
@@ -539,7 +545,7 @@ \subsection{A small update to \cs{obeylines} and \cs{obeyspaces}}
   \let\par=\cr \obeylines \halign{...
 \end{verbatim}
 However, redefining \cs{par} like this is not really a great idea in \LaTeX{},
-because it may lead to all kind of problems. We have therefore changed
+because it may lead to all kinds of problems. We have therefore changed
 the commands to use an indirection: the active characters now execute
 \cs{obeyedline} and \cs{obeyedspace}, which in turn do what the
 hardwired solution did before.
@@ -582,7 +588,7 @@ \subsection{\pkg{doc} upgraded to version~3}
 Given that most documentation is nowadays viewed on screen,
 \pkg{hyperref} support is added and by default enabled (suppress it
 with option \option{nohyperref} or alternatively with
-\option{hyperref}\texttt{=false}) so the internal cross-reference are
+\option{hyperref}\texttt{=false}) so the internal cross-references are
 properly resolved including those from the index back into the
 document.
 
@@ -634,7 +640,7 @@ \subsection{Lua\TeX\ callback improvements}
 Additionally the return value \texttt{true} for \texttt{list}
 callbacks is now handled internally and no longer passed on to the
 engine. This simplifies the handling of these callbacks and makes it
-easier to provide consistent interfaces for user defined \texttt{list}
+easier to provide consistent interfaces for user-defined \texttt{list}
 callbacks.
 
 
@@ -665,7 +671,7 @@ \subsection{Cleanup of the Unicode declaration interface}
 exception though: \cs{DeclareUnicodeAccent} required an explicit
 encoding argument.  This inconsistency has now been removed and the
 encoding name is always implicit. To avoid a breaking change for a few
-packages on CTAN \cs{DeclareUnicodeAccent} still accepts three
+packages on CTAN, \cs{DeclareUnicodeAccent} still accepts three
 arguments if the second argument is \texttt{TU} or
 \cs{UnicodeEncodingName}. Once all packages have been updated this
 code branch will get removed.
@@ -681,7 +687,7 @@ \subsection{Cleanup of the Unicode declaration interface}
 \subsection{New hook: \hook{include/excluded}}
 
 A few releases ago we introduced a number of file hooks for different
-types of files, see~\cite{35:ltnews32} and in
+types of files; see~\cite{35:ltnews32} and in
 particular~\cite{35:ltfilehook-doc}.
 %
 The hooks for \cs{include} files now got an addition: if such a file
@@ -708,7 +714,7 @@ \subsection{Input support for normalized angle brackets}
 \section{Bug fixes}
 
 \subsection{Using \cs{DeclareUnicodeCharacter} with C1 control points}
-An error in the UTF-8 handling for non-Unicode \TeX, has prevented
+An error in the UTF-8 handling for non-Unicode \TeX\ has prevented
 \cs{DeclareUnicodeCharacter} being used with characters in the range
 hex 80 to 9F, this has been corrected in this release.
 %
@@ -868,9 +874,9 @@ \section{Changes to packages in the \pkg{graphics} category}
 \subsection{Color in formulas}
 
 While it is possible to color parts of a formula using \cs{color}
-commands the approach is fairly cumbersome. For example, to color an
+commands the approach is fairly cumbersome. For example, to color a
 summation sign, but not its limits, you need four \cs{color} commands and
-some seemingly unnecessary set of braces to get coloring and spacing
+some seemingly unnecessary sets of braces to get coloring and spacing
 right:
 \begin{verbatim}
 \[ X = \color{red} \sum
@@ -881,7 +887,7 @@ \subsection{Color in formulas}
    \color{black}    % without it the x_i is red
    x_i           \]
 \end{verbatim}
-Leave out any of the \cs{color} commands or any of the \verb={{...}}=
+Leaving out any of the \cs{color} commands or any of the \verb={{...}}=
 will give you a wrong result instead of the desired
 \[ X = \color{red} \sum
     _{{\color{black} i=1}} % without {{ the superscript is misplaced
@@ -928,7 +934,7 @@ \subsection{\pkg{multicol}: Fix \cs{newcolumn}}
 
 The recently added \cs{newcolumn} didn't work properly if used in
 vertical mode, where it behaved like \cs{columnbreak}, i.e., spreading
-the column material out instead running the column short.
+the column material out instead of running the column short.
 %
 \sxissue{q/624940}