# HG changeset patch
# User wenzelm
# Date 1207675054 -7200
# Node ID ed7f995b3c9700217043e22c5964f1e94d0f56c2
# Parent  c3e597a476fdba38dce01d119e34a720b5b6a4b6
tuned;

diff -r c3e597a476fd -r ed7f995b3c97 doc-src/System/misc.tex
--- a/doc-src/System/misc.tex	Tue Apr 08 18:30:40 2008 +0200
+++ b/doc-src/System/misc.tex	Tue Apr 08 19:17:34 2008 +0200
@@ -313,11 +313,11 @@
 
 \end{enumerate}
 
-Parsing YXML is pretty straight-forward: split the text into chunks
-separated by \emph{X}, then split each chunk into sub-chunks separated
-by \emph{Y}.  Markup chunks start with an empty sub-chunk, and a
-second empty sub-chunk indicates close of an element.  Any other chunk
-consists of plain text.
+Parsing YXML is pretty straight-forward: split the text into chunks separated
+by \emph{X}, then split each chunk into sub-chunks separated by \emph{Y}.
+Markup chunks start with an empty sub-chunk, and a second empty sub-chunk
+indicates close of an element.  Any other non-empty chunk consists of plain
+text.
 
 YXML documents may be detected quickly by checking that the first two
 characters are \emph{X\,Y}.