[PATCH 09/10] memorder: Make clear the scope of READ_ONCE()/WRITE_ONCE() heavy uses

From: SeongJae Park <[email protected]>

A sentence in memorder.tex is saying READ_ONCE() and WRITE_ONCE() will
be heavily used in a section.  But, it's widely used in the chapter.
Modify the sentence to make it more clear.

Signed-off-by: SeongJae Park <[email protected]>
---
 memorder/memorder.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/memorder/memorder.tex b/memorder/memorder.tex
index bd24b14c..5c978fbe 100644
--- a/memorder/memorder.tex
+++ b/memorder/memorder.tex
@@ -668,7 +668,7 @@ even on relatively strongly ordered systems such as x86.
 	\co{READ_ONCE()} and \co{WRITE_ONCE()}
 	prevent the compiler from reordering.
 	And also from doing much else as well, so the examples in this
-	section will be making heavy use of
+	chapter will be making heavy use of
 	\co{READ_ONCE()} and \co{WRITE_ONCE()}.
 	See \cref{sec:memorder:Compile-Time Consternation}
 	for more detail on the need for \co{READ_ONCE()} and \co{WRITE_ONCE()}.
-- 
2.17.1