This was actually reported to use about 5 times last month.
Thanks very much for pointing it out, instead of just letting the error stand. As you know, we don't like inaccurate information -- ESPECIALLY NOT FROM OUR OWN SITE! (Egads!) This was fixed a few days ago. It was a content migration error, between the old site and new one. It was actually correct until at least October 2011. No idea when the wrong information was swapped. It could have been that was for several months now. Doh!
I posted this semi-embarassing email here to thank vkmestari and others who report errors. We appreciate the assist.