Updating naming convention of mixin styles to match Nerdery standards
Merge pull request #4 from anthonyLukes/feature/mixinNaming

Updating naming convention of mixin styles to match mix-in standards.

Extensions to an object should follow a single ancestry chain. Two sub-classes of an object should not appear on the same object if they are of a different ancestry chain. For these types of scenarios, we have mixins.

Mixins are a type of class extension that do not create a sub-class, but rather can be added to (mixed with) any super or sub-class of object. If a type of object has many variations that cannot be elegantly defined into discrete sub-classes, mixins may be the best solution. Mixins are generally an undesirable way to write CSS and should only be used when that is the best option available - usually when a design lacks consistency. Often is is better to create more base classes than to try and shoehorn everything into a single object with a lot of mixins.

We indicate an object mixin by prefixing the name with "mix-" and the base class name, followed by the mixin extension name (camelCased).