Ok, ok. You're right. I edited the page by hand to have the right. Since it's a tagged release, it's unlikely we'll rebuild that portion of the site. If we do this fix will be overwritten. Hopefully we'll have an updated release of Texen by then and this issue will be moot.
Commenting more for the Velocity dev community below...
This may be academic, but still pondering what the right process is to track changes to the docs. An unchanging "tag" for the release means that the docs can never be rebuilt on the site. Maybe we should be deploying from a branch (e.g. the VELOCITY_1.5 branch) so that doc fixes are source controlled?
Henning's suggested an alternative approach in the past, which is to pull the docs out of the release cycle entirely. I'm beginning to see the point, though I worry about losing synchronicity with feature changes.