For proper document structure, add section titles to the converted
description lists.
Amend preceding sentences as well.
Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
toolsoftrade/toolsoftrade.tex | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/toolsoftrade/toolsoftrade.tex b/toolsoftrade/toolsoftrade.tex
index ea65d6b99b29..5a38d957c19f 100644
--- a/toolsoftrade/toolsoftrade.tex
+++ b/toolsoftrade/toolsoftrade.tex
@@ -1262,7 +1262,7 @@ which includes program counter and stack.
The thread API is shown in
\cref{lst:toolsoftrade:Thread API}, and members are described in the
-following sections.
+following section.
\begin{listing}
\begin{VerbatimL}[numbers=none,xleftmargin=2pt]
@@ -1277,6 +1277,8 @@ void wait_all_threads(void)
\label{lst:toolsoftrade:Thread API}
\end{listing}
+\subsubsection{API Members}
+
\begin{description}[style=nextline]
\item[\tco{create_thread()}]
The \apipf{create_thread()} primitive creates a new thread,
@@ -1389,7 +1391,7 @@ as in this case they are all \co{NULL}, which is not very interesting.
A good starting subset of the Linux kernel's locking API is shown in
\cref{lst:toolsoftrade:Locking API},
-each API element being described in the following sections.
+each API element being described in the following section.
This book's CodeSamples locking API closely follows that of the Linux kernel.
\begin{listing}
@@ -1403,6 +1405,8 @@ void spin_unlock(spinlock_t *sp);
\label{lst:toolsoftrade:Locking API}
\end{listing}
+\subsubsection{API Members}
+
\begin{description}[style=nextline]
\item[\tco{spin_lock_init()}]
@@ -2524,6 +2528,8 @@ init_per_thread(name, v)
not they were C static variables!
}\QuickQuizEnd
+\subsubsection{API Members}
+
\begin{description}[style=nextline]
\item[\tco{DEFINE_PER_THREAD()}]
--
2.25.1
