From 3f49d91463fcb74611d8b3eb19f5b68c6aae6812 Mon Sep 17 00:00:00 2001 From: Justin Turner Arthur Date: Tue, 19 Feb 2013 17:03:33 -0600 Subject: [PATCH] Fixes typo introduced by django/django@08dc90bccf7c4ffa8b04064d74b54c1150af5ff9. This is described in Trac ticket:19855. --- docs/howto/legacy-databases.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/howto/legacy-databases.txt b/docs/howto/legacy-databases.txt index 67bce7e976..6846e4b2df 100644 --- a/docs/howto/legacy-databases.txt +++ b/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