Technique -> Requirements

Turning the original intention into wording most folks can agree on.

There is minimal autoloader specific content and the steps are made more generic so that people do not confuse them for pseudo-code outlining sequential steps that MUST be taken to comply - which was never the suggestion, but confusing wording apparently lead to this common misconception.

There is some remaining implementation-level information, for example we absolutely have to point out that autoloaders cannot and will not throw exceptions or raise errors. We have worded it to be vague and apply to all parties, as all parties need to know this.