Order in which autoloader checks things - Moved to implementation
Technique -> Requirements
By rewording the steps later on in the Technique section this no longer looks like pseudo-code to autoloader developers, and instead just looks like a relevant chunk of information that any type of user is interested in - but still prescribes what the autoloader devs should be doing.
Explain what the autoloader is actually up to here
Fix example class name formatting
Expanded a little on what that example was.
Grouped all examples together in a new Examples section
Example Technique, Example Resource Organization and Example Implementation are all together, in one big happy WE ARE NOT PART OF THE SPEC ITSELF family.
Before the 3.3 Example Technique was part of 3. Specification. It's hard to say its not part of the specification when its in the same damn heading.
Corresponding was vague
Merge pull request #211 from philsturgeon/psr4

Technique -> Requirements