!section chapter names {
The leafnames of the textfiles describing chapters must begin
with a pair of digits. These digits must make up consecutive
numbers, and they indicate the ordering of the chapters.
Thus
!code {
         01Starter  02Main 03Pudding
}
will produce three chapters: __Starter__, __Main__, __Pudding__ - in that order.
So 99 chapters is the maximum.
}

!section sections {
Chapter files consist of __sections__. A section has the form
!code {
  &#33;section {<em>body</em>}
}
or
!code {
  &#33;section <em>heading</em> {<em>body</em>}
}
where the arguments are text. If there is a heading it is automatically
listed as a link on the contents page. Sections cannot be nested.
They may contain html tags. }

!section images {
An image may be placed in a section with an expression
!code {
  &#33;img <em>image</em>
}
followed by a space or newline, where __image__ is the
pathname of a file of type gif, jpeg or png relative
to the target directory. Note that RISC OS, not Unix, filename conventions
apply. The width and height attributes of the image are calculated
automatically by Bind. You must put the images into the target directory.}

!section links {
A link may be placed in a section with an expression
!code {
  &#33;link <em>url</em> { <em>link_text</em> }
}
where the first argument is the url and the second is the text of
the link. The link_text can contain images.
}

!section code {
Code can be displayed within a section in preformatted form using
the forms:
!code {
  &#33;code {<em>code_text</em>}
  &#33;code @<em>filename</em>
}
Code sections cannot be nested, nor may they contain images or links. The filename is
relative to the source directory. The contents of the file will have certain characters
converted to html entities.
}

!section citation {
Within sections text can be cited by sandwiching it between double
underscores:
!code {
   special &#95;&#95;emphasis&#95;&#95;
}
}