That all looks good, but in a practical application does it really matter. I would suspect that provided the application does not interfere with another class or namespace it "shouldn't" make a difference. It would be an obvious problem if you duplicated the class name of an already existent class, such as in the example, Microsoft.Office ~ I don't see that being a problem while being used on a small scale, but it has broader implications on a large scale deployment.
The info is a good rule to follow, at least then you won't have to try and guess if the naming convention is what is creating your problem.