From: SeongJae Park <sj38.park@xxxxxxxxx>
A few sentences in ppcmem.tex are using ``\co{}'', which can be
shortenized with \qco{}. Use the shorter one.
Signed-off-by: SeongJae Park <sj38.park@xxxxxxxxx>
---
formal/ppcmem.tex | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/formal/ppcmem.tex b/formal/ppcmem.tex
index 62a45383..9acd4dba 100644
--- a/formal/ppcmem.tex
+++ b/formal/ppcmem.tex
@@ -65,8 +65,8 @@ discusses the implications.
An example PowerPC litmus test for PPCMEM is shown in
\cref{lst:formal:PPCMEM Litmus Test}.
The ARM interface works the same way, but with \ARM\ instructions
-substituted for the Power instructions and with the initial ``PPC''
-replaced by ``ARM''.
+substituted for the Power instructions and with the initial \qco{PPC}
+replaced by \qco{ARM}.
\begin{listing}
\begin{fcvlabel}[ln:formal:PPCMEM Litmus Test]
@@ -98,8 +98,8 @@ exists @lnlbl[assert:b]
\end{listing}
\begin{fcvref}[ln:formal:PPCMEM Litmus Test]
-In the example, \clnref{type} identifies the type of system (``ARM'' or
-``PPC'') and contains the title for the model.
+In the example, \clnref{type} identifies the type of system (\qco{ARM} or
+\co{PPC}) and contains the title for the model.
\Clnref{altname} provides a place for an
alternative name for the test, which you will usually want to leave
blank as shown in the above example.
@@ -412,7 +412,7 @@ These tools do have some intrinsic limitations:
\item These tools are not much good for complex data structures, although
it is possible to create and traverse extremely simple linked
lists using initialization statements of the form
- ``\co{x=y; y=z; z=42;}''.
+ \qco{x=y; y=z; z=42;}.
\item These tools do not handle memory mapped I/O or device registers.
Of course, handling such things would require that they be
formalized, which does not appear to be in the offing.
--
2.17.1
