[Lxml-checkins] r51108 - in lxml/trunk: . doc

[scoder at codespeak.net]

Author: scoder
Date: Tue Jan 29 08:14:07 2008
New Revision: 51108

Modified:
   lxml/trunk/   (props changed)
   lxml/trunk/doc/performance.txt
Log:
 r3362 at delle:  sbehnel | 2008-01-29 08:13:37 +0100
 doc update


Modified: lxml/trunk/doc/performance.txt
==============================================================================
--- lxml/trunk/doc/performance.txt	(original)
+++ lxml/trunk/doc/performance.txt	Tue Jan 29 08:14:07 2008
@@ -14,9 +14,9 @@
 all software, it depends on what you do with it.  Rest assured that
 lxml is fast enough for most applications, so lxml is probably
 somewhere between 'fast enough' and 'the best choice' for yours.  Read
-this `message from a happy user`_ to see what we mean.
+these `messages from happy users`_ to see what we mean.
 
-.. _`message from a happy user`: http://permalink.gmane.org/gmane.comp.python.lxml.devel/3244
+.. _`messages from happy users`: http://thread.gmane.org/gmane.comp.python.lxml.devel/3244/focus=3244
 
 This text describes where lxml.etree (abbreviated to 'lxe') excels, gives
 hints on some performance traps and compares the overall performance to the