The customisation section required some changes as it's not often
necessary to override the root application instance to change URLs or
views of subapps.

Those documents lived in ref/, but really aren't reference documents.
Topics/ is a more appropriate place for them.

With details of new prices/availability structure.

* Better wordings for the individual steps
* Mentioned necessary copying of migrations directory
* Fixed wrong prerequisites in examples
* Glossary typo fixed

The mailing list raised the issue of having to include the models.py to
replace a Form. The docs weren't clear, so I've taken the opportunity
to:

* merge 'INSTALLED_APPS' section and 'models.py & admin.py'.
* change misc wordings and add clarifications

It's a great idea, but confusing when empty. Replaced by links to
how_to_customise_models which contains some explanations.

Attempt at making it clearer what needs to be done for what kind of
customisation. Created a new topic that lines out the prepatory
steps that need to be taken, and moved duplicate information from the
how-tos into the new topic.

The old howto included out-dated info on how to translate Oscar. That
has been replaced by a link to the Transifex project.
It was the only howto left under the Contributing headline, which really
shouldn't be there (as there's an entirely different section in the docs
for contributing). As it is more of a topic anyway, and will hopefully
soon include documentation on translation style etc., it was turned into
a topic.

To set a base for upcoming docs changes, the docs directory structure
has been streamlined to follow a simplified version of Django's docs.

The old _draft folder has been removed. Both files from there and the
current docs that don't fit nicely into the new structure are in _old/
for the moment.