<Para>
Binary distributions come in “bundles,” one bundle per file called
-<Literal><bundle>-<platform>.tar.gz</Literal>. (See the building guide (<XRef LinkEnd="pre-supposed-doc-tools">) for the definition of a platform.) Suppose that you untar a binary-distribution bundle, thus:
+<Literal><bundle>-<platform>.tar.gz</Literal>. (See the building guide for the definition of a platform.) Suppose that you untar a binary-distribution bundle, thus:
</Para>
<Para>
option, so you can see exactly what pathnames it's using.
If things don't work as expected, check the list of known pitfalls in
-the building guide (<XRef LinkEnd="pre-supposed-doc-tools">.
+the building guide.
</Para>
</ListItem>
</Sect1>
-<Sect1><Title>Installing on Windows</Title>
+<Sect1 id="sec-install-windows"><Title>Installing on Windows</Title>
<Para>
Getting the Glasgow Haskell Compiler (GHC) to run on Windows platforms can
</Para>
</Answer>
+</QandAEntry>
+
<QandAEntry>
<Question>
work, as it needs version 3.0. You should unpack Jade into <Filename>\Jade</Filename>, along with the entities, DocBook into <Filename>\docbook</Filename>, and the DocBook stylesheets into <Filename>\docbook\stylesheets</Filename> (so they actually end up in <Filename>\docbook\stylesheets\docbook</Filename>).
</Para>
+</Sect2>
+
<Sect2>
<Title>Installing the DocBook tools from source</Title>
you start getting file not found errors when making the test for
<Command>hyperref</Command>, you can abort at that point and proceed
straight to <Command>make install</Command>, or enter them as
-<Filename>../<Emphasis>filename</Emphasis></Filename>.)
+<Filename>../</Filename><Emphasis>filename</Emphasis>.)
</Para>
<Para>
</Sect3>
-<Sect3>
+<Sect3 id="sec-scheduling-policy">
<Title>Scheduling policy for concurrent/parallel threads
<IndexTerm><Primary>Scheduling—concurrent/parallel</Primary></IndexTerm>
<IndexTerm><Primary>Concurrent/parallel scheduling</Primary></IndexTerm></Title>