SVN commit 504394 by englich:

Fixes.


 M  +4 -4      Mainpage.dox  


--- trunk/kdenonbeta/kdom/xpath/Mainpage.dox #504393:504394
@@ -121,7 +121,7 @@
  * built-in datatypes XPath 2.0 uses.
  * - <a href="http://www.w3.org/TR/xslt20/">XSL Transformations (XSLT) Version 2.0</a> -- useful to have a
  * look at a major use case of XPath 2.0.
- * - <a href="http://www.w3.org/TR/xquery-xpath-parsing/">Building a Tokenizer for XPath or XQuery</a> -- useful
+ * - <a href="http://www.w6.org/TR/xquery-xpath-parsing/">Building a Tokenizer for XPath or XQuery</a> -- useful
  * if one is working on the scanner/parser
  *
  * In addition, these articles and papers can be of interest:
@@ -139,13 +139,13 @@
  * are relatively similar from an object oriented perspective, and that both
  * projects uses a naming close to the specifications, means they are
  * relatively similar in overall. Studying how Saxon have solved problems
- * can be an eye opener, and can be a good idea instead of jumping into the
- * unknown deep. Of course, it is a wise move to study prior art, instead of
+ * can be an eye opener, and a good idea instead of jumping into the
+ * unknown deep. Of course, it is wise to study prior art, instead of
  * reinventing the wheel.
  *
  * Saxon's API documentation can be found <a href="http://www.saxonica.com/documentation/javadoc/">here</a>,
  * and its source can be downloaded on its <a href="http://sourceforge.net/projects/saxon">Sourceforge
- * project page</a>. As of this writing, the latest version is @c 8.5.1.
+ * project page</a>.
  *
  * @subsection KXPATH_joining_CodingStyle Coding Style
  *