Merged in Reid's typo fixes.

  <li>Unnamed values are represented as an unsigned numeric value with a '%'

  prefix.  For example, %12, %2, %44.</li>

  <li>Constants, which are described in <a href="#constants">section about

  constants</a></li>

  <li>Constants, which are described in a <a href="#constants">section about

  constants</a>, below.</li>

</ol>

<p>LLVM requires that values start with a '%' sign for two reasons: Compilers

</div>

<!-- ======================================================================= -->

<div class="doc_subsection"> <a name="simpleconstants">Simple Constants</a>

</div>

<div class="doc_subsection"><a name="simpleconstants">Simple Constants</a></div>

<div class="doc_text">

  <dt><b>Integer constants</b></dt>

  <dd>Standard integers (such as '4') are constants of <a

  <dd>Standard integers (such as '4') are constants of the <a

  href="#t_integer">integer</a> type.  Negative numbers may be used with signed

  integer types.

  </dd>

of floating point constants.  For example, the form '<tt>double

0x432ff973cafa8000</tt>' is equivalent to (but harder to read than) '<tt>double

4.5e+15</tt>'.  The only time hexadecimal floating point constants are required

(and the only time that they are generated by the disassembler) is when an FP

constant has to be emitted that is not representable as a decimal floating point

number exactly.  For example, NaN's, infinities, and other special cases are

represented in their IEEE hexadecimal format so that assembly and disassembly do

not cause any bits to change in the constants.</p>

(and the only time that they are generated by the disassembler) is when a 

floating point constant must be emitted but it cannot be represented as a 

decimal floating point number.  For example, NaN's, infinities, and other 

special values are represented in their IEEE hexadecimal format so that 

assembly and disassembly do not cause any bits to change in the constants.</p>

</div>