"converting an app" documentation fixes and clarifications

[carl@…]

16:29 < carljm> andrewgodwin: is it just me, or should "committed... into the database" actually be "committed... into the _code_base" here: http://south.aeracode.org/docs/convertinganapp.html
16:30 < andrewgodwin> carljm: it should be VCS, or codebase, yes 
16:30 < andrewgodwin> let me fix that now
16:31 < carljm> andrewgodwin: i was going to make a patch, but while you're fixing that, i think that page should mention that you want to do this converting business _before_ you start making model changes
16:31 < carljm> (presuming you have model changes you want reflected on other deployments)
16:31 < carljm> that seems to be a common gotcha, people making the changes to their models and only then thinking about migrations

The other thing that could use slightly more explanation on this page is why you have to fake the initial migration on existing instances: because the initial migration creates all the tables, so any database instances that had that app synced before it used south will already have those tables in their current state.

[andrew]

Fixed in [ef8e3fd3a82d].