% -> % to fix translations problems

i2p2www/pages/site/misc/benchmarks.html

@@ -248,7 +248,7 @@ speeds because time is needed to transfer data to and from memory.
 For the ciphers that specify big endian byte order, the timing data 
 listed include time needed to convert to and from little endian
 order.  For some ciphers (WAKE and SHA) this is a large fraction (up
-to 25%) of the total time.
+to 25%) of the total time.
 <LI>
 The RSA, RW, DH, MQV, and elliptic curve schemes come from the IEEE P1363
 standard. For more info see <A HREF="http://grouper.ieee.org/groups/1363/index.html">

i2p2www/pages/site/misc/jbigi.html

@@ -123,7 +123,7 @@ info, it will be something like this:
 {%- endtrans %}<pre>
 native run time:  5842ms ( 57ms each)
 java run time:   41072ms (406ms each)
-native = 14.223802103622907% of pure java time
+native = 14.223802103622907&#37; of pure java time
 </pre>
 {% trans %}If the native is indeed 5-7x faster (or more) then it looks all good. If not, please report.{% endtrans %}</li>
 <li>{% trans %}Copy <code>libjbigi.so</code> to your i2p directory{% endtrans %}</li>