Oh, thanks for letting us know. This article indeed needs an update.
What specific issue with CBQoS do you have?
Looking at why we have a widespread issue of not receiving CBQoS stats in our environment. We had an instance back in August where a broken counter was causing an issue (a reboot fixed), but I'm thinking a mass reboot project isn't necessarily needed across our environment.
I'd warn you that you have multiple spots throughout your knowledgebase that needs updating, not just CBQoS. Do I notify you on individual instances or would a general post to Thwack suffice?