Updated documentation.

diff --git a/docs/awstats_compare.html b/docs/awstats_compare.html
index 132a4018fb126b110a09a4a7fb5d1cb582daf72b..c7373032a42bd22cb0a2d880872a164069dd75b3 100644 (file)
--- a/docs/awstats_compare.html
+++ b/docs/awstats_compare.html
@@ -113,7 +113,7 @@
 \r
 </table>\r
 <br>\r
-<font style="font: 7pt arial,helvetica,verdana">\r
+<font style="font: 8pt arial,helvetica,verdana">\r
 * This number is not really the number of browsers detected. All browsers (known and unknown) can be detected by products\r
 that support user agent listing (AWStats,Analog,Webalizer,HitBox). The 'browser detection feature' and number is the number of known browsers for which different\r
 versions/ids of same browser are grouped by default in one browser name.<br>\r
@@ -126,14 +126,14 @@ So, if you have only 2000 visits a month, products with no robot detection capab
 Those rules are updated with AWStats updates.\r
 But AWStats has also an algorithm to detect keywords of unknown search engines with unknown url syntax rules. <br>\r
 <br>\r
-**** Other log analyzers have poor (or not at all) robots, search engines, os or\r
-browsers detection capabilities and few features (no or poor visits count, bad filter rules, etc...).<br>\r
-It is not possible to add all AWStats features to other log analyzers, so don't forget that benchmarks\r
-results are for 'different features' (for this benchmark, I did just complete Webalizer and Analog robots\r
-or search engines databases with part of AWStats database. So Webalizer config file was\r
-completed with this <a href="http://awstats.sourceforge.net/files/webalizeradd.txt">file</a>, Analog config file was\r
-completed with this <a href="http://awstats.sourceforge.net/files/analogadd.txt">file</a>.\r
-Note that without this very light add (using default conf file), Webalizer speed is 3 times faster, Analog is 15% faster).<br>\r
+**** Most log analyzers have poor (or not at all) robots, search engines, os or browsers
+detection capabilities and less features (no or poor visits count, no filter rules, etc...).<br>
+It is not possible to add all AWStats features to other log analyzers, so don't forget that benchmarks
+results are for 'different features'. For this benchmark, I did just complete Webalizer and Analog robots
+or search engines databases with part of AWStats database. So Webalizer config file was
+completed with this <a href="http://awstats.sourceforge.net/files/webalizeradd.txt">file</a>, Analog config file was
+completed with this <a href="http://awstats.sourceforge.net/files/analogadd.txt">file</a>.
+Note that without this very light add (using default conf file), Webalizer speed is 3 times faster, Analog is 15% faster).<br>
 Benchmark was made on a combined (XLF/CLF) log record on an Athlon 1GHz.<br>\r
 You must keep in mind that all this times are without reverse DNS lookup. DNS lookup speed depends on your system, network and\r
 Internet but not on the log analyzer you use. For this reason, DNS lookup is disabled in all log analyzer benchmarks.\r