No I like it as it is. Simple and straight to the point. And since browse could apply to a variety of things while browseClass is very specific, similarl to what Ben is saying.��
I would prefer it for example if I wanted to browse the metaclass of Object to have
Object class browse��
while for the instance side a
Object browse��
would do, That gives browse message a context sensitive/dependant meaning which for me is what OO is all about while your browseClass goes against the same principle. On other hand I have an allergy to camel case anyway :D