Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Fix typo in legacy database howto (English) #739

Merged
merged 1 commit into from

2 participants

@JustinTArthur

Has:

This servers as an explicit opt-in to give your nascent Django project write access to your precious data on a model by model basis.

Should read:

This serves as an explicit opt-in to give your nascent Django project write access to your precious data on a model by model basis.

@timgraham timgraham merged commit 9dde0dc into django:master
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Feb 19, 2013
  1. @JustinTArthur
This page is out of date. Refresh to see the latest.
Showing with 1 addition and 1 deletion.
  1. +1 −1  docs/howto/legacy-databases.txt
View
2  docs/howto/legacy-databases.txt
@@ -70,7 +70,7 @@ If you wanted to modify existing data on your ``CENSUS_PERSONS`` SQL table
with Django you'd need to change the ``managed`` option highlighted above to
``True`` (or simply remove it to let it because ``True`` is its default value).
-This servers as an explicit opt-in to give your nascent Django project write
+This serves as an explicit opt-in to give your nascent Django project write
access to your precious data on a model by model basis.
.. versionchanged:: 1.6
Something went wrong with that request. Please try again.