Edit GeoDjango Tutorial for consistency and style.

[shepdl]

There are a few grammatical problems with consistency and style in the GeoDjango Tutorial. Nothing factually wrong, but some changes would make it easier to read, I think. Also, there is at least one empty section ("Google.")

[Claude Paroz]

We welcome any improvements to the docs, but please then provide a patch with your suggestions. It is worth nothing having open tickets with too general statements like this. Do you plan to provide a patch soon?

[Claude Paroz]

Once again, we'd really appreciate any patch aimed to improve GeoDjango docs. I'm just setting this ticket as needinfo because the current description is too vague in its current state.

[shepdl]

My apologies. I added this as part of something I was working on at a hackathon, had a bunch of trouble with Git (my own fault) so I couldn't commit the patch, and then went out of town for a week. I'll provide this soon.

[Tim Graham]

Thanks for this, however, don't close a ticket until a core developer commits it. You can put a link to your pull request in the ticket and check the "Has Patch" box so people can find it for review.

​https://github.com/django/django/pull/531

[Claude Paroz]

Thanks, this looks very good (as seen by a non-native speaker). I'd still like a quick review by a native English speaker before the commit, if possible.

[Tim Graham]

Left a few trivial comments, English looks fine to me.

[Tim Graham <timograham@…>]

In 8e5573e99abd5351dfbd6de1214662ecf7f6c9ba:

Fixed #19243 - Edited GeoDjango Tutorial for consistency and style.

[Tim Graham <timograham@…>]

In 187441602c992fe8e97e32a7a53cc433cf06dd46:

[1.5.X] Fixed #19243 - Edited GeoDjango Tutorial for consistency and style.

Backport of 8e5573e99a from master