Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
Paul,
I think "the" in "the Section xxx" is redundant.
But please check before applying this.
2nd hunk should be the right fix.
Thanks, Akira
--
defer/rcuintro.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/defer/rcuintro.tex b/defer/rcuintro.tex
index c5f2663b..bb79ec0b 100644
--- a/defer/rcuintro.tex
+++ b/defer/rcuintro.tex
@@ -181,7 +181,7 @@ So perhaps going all the way was not too far after all!
But how can we tell when all of the pre-existing readers have in
fact completed?
-This question is the topic of the \cref{sec:defer:Waiting for Readers}.
+This question is the topic of \cref{sec:defer:Waiting for Readers}.
But first, the next section defines RCU's core API.
\subsubsection{Core RCU API}
@@ -199,7 +199,7 @@ The \apik{rcu_read_lock()} and \apik{rcu_read_unlock()} functions delimit
RCU read-side critical sections.
These may be nested, so that one \co{rcu_read_lock()}--\co{rcu_read_unlock()}
pair can be enclosed within another.
-In this case, the nested set of RCU read-side critical section act as
+In this case, the nested set of RCU read-side critical sections act as
one large critical section covering the full extent of the nested set.
The third read-side API member, \apik{rcu_dereference()}, fetches an
RCU-protected pointer.
--
2.17.1
