Lout 3.21.

git-svn-id: http://svn.savannah.nongnu.org/svn/lout/trunk@11 9365b830-b601-4143-9ba8-b4a8e2c3339c

1 files changed, 11 insertions, 11 deletions

diff --git a/doc/expert/pre_head b/doc/expert/pre_head
index eb3d397..14e2871 100644
--- a/doc/expert/pre_head
+++ b/doc/expert/pre_head
@@ -17,15 +17,15 @@ component looks exactly like it would have done as an ordinary
 component; the difference is in whether the component is printed at all,
 and if so where.
 @PP
-Every ordinary component of every galley has associated with it a
-sequence of zero or more header components.  Whenever a new target
-is attached to which does not itself occupy an entire component
-of its galley, copies of the header components associated with the
+Every non-header component of every galley has associated with it a
+sequence of zero or more header components.  Whenever a galley attaches
+to a target, and the target does not itself occupy an entire component
+of the enclosing galley, copies of the header components associated with the
 first ordinary component to be promoted into that target are
 promoted into it first.
 @PP
-The condition `which does not itself occupy an entire component
-of its galley' ensures that, for example, when part of a section
+The condition `and the target does not itself occupy an entire component
+of the enclosing galley' ensures that, for example, when part of a section
 has header components, these are not printed where the section is
 promoted into its chapter, but rather where the chapter is promoted
 onto pages.  If the target occupies the whole component, then the
@@ -37,7 +37,7 @@ components of each ordinary component determined?'  By default,
 the header components of one component are the same as those
 of the previous component.  We can show this graphically as
 follows:
-@ID lines @Break @Eq {
+@ID @OneRow lines @Break @Eq {
 C sub i : H sub 1 , H sub 2 ,..., H sub n
 "/"
 C sub i+1 : H sub 1 , H sub 2 ,..., H sub n
@@ -48,7 +48,7 @@ then its successor component @E { C sub i+1 } has header component
 sequence @E { H sub 1 , H sub 2 ,..., H sub n } also.'  Using this
 notation, we may now define the four symbols that affect header
 component sequences:
-@ID lines @Break @Eq {
+@ID @OneRow lines @Break @Eq {
 C sub i : H sub 1 , H sub 2 ,..., H sub n
 "/"
 gap `` @@BeginHeaderComponent `` H sub n+1
@@ -66,7 +66,7 @@ exactly as it would have been had it occurred alone at that point,
 rather than after @@BeginHeaderComponent.
 @PP
 Next comes @@EndHeaderComponent:
-@ID lines @Break @Eq {
+@ID @OneRow lines @Break @Eq {
 C sub i : H sub 1 , H sub 2 ,..., H sub n , H sub n+1
 "/"
 @@EndHeaderComponent
@@ -82,7 +82,7 @@ used in matching (possibly nested) pairs, to introduce and subsequently
 retract a header component.
 @PP
 Next comes @@SetHeaderComponent:
-@ID lines @Break @Eq {
+@ID @OneRow lines @Break @Eq {
 C sub i : H sub 1 , H sub 2 ,..., H sub n
 "/"
 gap `` @@SetHeaderComponent `` H sub n+1
@@ -93,7 +93,7 @@ C sub i+1 : H sub n+1
 set.header.component.sym @Index { @@SetHeaderComponent symbol }
 and replaces them by one of its own.  Finally we have
 @@ClearHeaderComponent:
-@ID lines @Break @Eq {
+@ID @OneRow lines @Break @Eq {
 C sub i : H sub 1 , H sub 2 ,..., H sub n
 "/"
 @@ClearHeaderComponent