Yeah; in this case, the initial mistake at publishing appears to be an honest mistake. As the specs lined up and the tech marketing guys were told that nothing changed on that hardware, they kept the same ROP specs they''d already been using in their marketing materials.
I have to admit that back when I was publishing specs like these, I made that mistake myself a few times.
However, it's what happened next that's a bit odd: I find it difficult to believe that it took 4 months for it to come to the attention of the company -- and it came from an external source. There's usually some engineer that spends a lot of time reading slashdot and looking up the specs of the products he's worked on -- and they'd likely flag it up. I'd expect 2-month turn-around until the company management realized the mistake.
The next bit that often happens is asking engineering "Is the change significant in any way?" to which the answer is "no." So marketing is either not even told of the mistake, or told that it's there, but not worth updating the documentation or issuing any sort of an update.
I find it really odd that they didn't even bother to change it on the website and queue it up for the next round of distribution.
What this really makes me wonder though, is how often this happens with products held to this standard, and nobody notices....