[latex3-commits] [git/LaTeX3-latex3-latex3] master: Clean up sectioning in l3kernel [ci skip] (a87ff9e)

[Bruno Le Floch]

Repository : https://github.com/latex3/latex3
On branch  : master
Link       : https://github.com/latex3/latex3/commit/a87ff9ed2c03ae6f14cbd3465a727aba457af1c8

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

commit a87ff9ed2c03ae6f14cbd3465a727aba457af1c8
Author: Bruno Le Floch <bruno at le-floch.fr>
Date:   Sun Apr 29 13:08:48 2018 -0400

    Clean up sectioning in l3kernel [ci skip]


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

a87ff9ed2c03ae6f14cbd3465a727aba457af1c8
 l3kernel/l3luatex.dtx |    8 +++-----
 l3kernel/l3quark.dtx  |    4 +---
 l3kernel/l3regex.dtx  |   18 ++++++++----------
 3 files changed, 12 insertions(+), 18 deletions(-)

diff --git a/l3kernel/l3luatex.dtx b/l3kernel/l3luatex.dtx
index 2d177ee..af5342e 100644
--- a/l3kernel/l3luatex.dtx
+++ b/l3kernel/l3luatex.dtx
@@ -47,16 +47,14 @@
 %
 % \begin{documentation}
 %
-% \section{Breaking out to \Lua{}}
-%
 % The \LuaTeX{} engine provides access to the \Lua{} programming language,
 % and with it access to the \enquote{internals} of \TeX{}. In order to use
 % this within the framework provided here, a family of functions is
-% available. When used with \pdfTeX{} or \XeTeX{} these raise an
+% available. When used with \pdfTeX{}, \pTeX{}, \upTeX{} or \XeTeX{} these raise an
 % error: use \cs{sys_if_engine_luatex:T} to avoid this. Details on using
 % \Lua{} with the \LuaTeX{} engine are given in the \LuaTeX{} manual.
 %
-% \subsection{\TeX{} code interfaces}
+% \section{Breaking out to \Lua{}}
 %
 % \begin{function}[EXP, added = 2015-06-29]{\lua_now_x:n, \lua_now:n}
 %   \begin{syntax}
@@ -123,7 +121,7 @@
 %   \end{texnote}
 % \end{function}
 %
-% \subsection{Lua interfaces}
+% \section{Lua interfaces}
 %
 % As well as interfaces for \TeX{}, there are a small number of Lua functions
 % provided here.
diff --git a/l3kernel/l3quark.dtx b/l3kernel/l3quark.dtx
index d10e6ce..d043f5b 100644
--- a/l3kernel/l3quark.dtx
+++ b/l3kernel/l3quark.dtx
@@ -47,13 +47,11 @@
 %
 % \begin{documentation}
 %
-% \section{Introduction to quarks and scan marks}
-%
 % Two special types of constants in \LaTeX3 are \enquote{quarks} and
 % \enquote{scan marks}. By convention all constants of type quark
 % start out with |\q_|, and scan marks start with |\s_|.
 %
-% \subsection{Quarks}
+% \section{Quarks}
 %
 % Quarks are control sequences that expand to themselves and should
 % therefore \emph{never} be executed directly in the code.
diff --git a/l3kernel/l3regex.dtx b/l3kernel/l3regex.dtx
index 41a9008..fa2cb16 100644
--- a/l3kernel/l3regex.dtx
+++ b/l3kernel/l3regex.dtx
@@ -50,8 +50,6 @@
 %   {\begin{itemize}\def\\{\char`\\}\def\makelabel##1{\hss\llap{\ttfamily##1}}}
 %   {\end{itemize}}
 %
-% \section{Regular expressions}
-%
 % The \pkg{l3regex} package provides regular expression testing,
 % extraction of submatches, splitting, and replacement, all acting
 % on token lists. The syntax of regular expressions is mostly a subset
@@ -96,7 +94,7 @@
 % giving us access to the name of the environment when doing
 % replacements.
 %
-% \subsection{Syntax of regular expressions}
+% \section{Syntax of regular expressions}
 %
 % We start with a few examples, and encourage the reader to apply
 % \cs{regex_show:n} to these regular expressions.
@@ -382,7 +380,7 @@
 % true match is |{acbc3}|, with first submatch |{bc}|, but |\K| resets
 % the beginning of the match to the last position where it appears.
 %
-% \subsection{Syntax of the replacement text}
+% \section{Syntax of the replacement text}
 %
 % Most of the features described in regular expressions do not make
 % sense within the replacement text.  Backslash introduces various
@@ -457,7 +455,7 @@
 % \end{verbatim}
 % results in \cs{l_my_tl} holding |first,\emph{second},first,first|.
 %
-% \subsection{Pre-compiling regular expressions}
+% \section{Pre-compiling regular expressions}
 %
 % If a regular expression is to be used several times,
 % it is better to compile it once rather than doing it
@@ -510,7 +508,7 @@
 %   the second branch is not anchored to the beginning of the match.
 % \end{function}
 %
-% \subsection{Matching}
+% \section{Matching}
 %
 % All regular expression functions are available in both |:n| and |:N|
 % variants. The former require a \enquote{standard} regular expression,
@@ -552,7 +550,7 @@
 %   results in \cs{l_foo_int} taking the value $5$.
 % \end{function}
 %
-% \subsection{Submatch extraction}
+% \section{Submatch extraction}
 %
 % \begin{function}[noTF, added = 2017-05-26]
 %   {\regex_extract_once:nnN, \regex_extract_once:NnN}
@@ -635,7 +633,7 @@
 %   is left in the input stream.
 % \end{function}
 %
-% \subsection{Replacement}
+% \section{Replacement}
 %
 % \begin{function}[noTF, added = 2017-05-26]
 %   {\regex_replace_once:nnN,\regex_replace_once:NnN}
@@ -664,7 +662,7 @@
 %   locally to \meta{tl~var}.
 % \end{function}
 %
-% \subsection{Constants and variables}
+% \section{Constants and variables}
 %
 % \begin{variable}[added = 2017-12-11]{\l_tmpa_regex, \l_tmpb_regex}
 %   Scratch regex for local assignment. These are never used by
@@ -680,7 +678,7 @@
 %   code and so should only be used for short-term storage.
 % \end{variable}
 %
-% \subsection{Bugs, misfeatures, future work, and other possibilities}
+% \section{Bugs, misfeatures, future work, and other possibilities}
 %
 % The following need to be done now.
 % \begin{itemize}