Comment 38 for bug 224971

@Przemyslaw, cheers but I'm not going to that level of hassle! Surely given the website team are subscribed to this bug then this is in their domain!

My interest in this was purely as it was filed as a documentation team bug, to which end I intend to set it to invalid because it isn't really our issue. This bug is subscribed to two other teams that can deal with the issue more effectively than the doc-team can.