Revert "Updated some docs for the delayed deprecation of legacy table creation; refs #22340."

This reverts commit a2e3c9694823d6d451d6dd234e9d416600aacc68.

The deprecation was moved back to 1.9 in
61da5f3f02f34810aaa6fcddac3808318a5b95c4.

1 files changed, 2 insertions, 2 deletions

diff --git a/docs/howto/initial-data.txt b/docs/howto/initial-data.txt
index 6e7fc3ff2a..b7e00d1346 100644
--- a/docs/howto/initial-data.txt
+++ b/docs/howto/initial-data.txt
@@ -82,7 +82,7 @@ Automatically loading initial data fixtures
 .. deprecated:: 1.7
 
     If an application uses migrations, there is no automatic loading of
-    fixtures. Since migrations will be required for applications in Django 2.0,
+    fixtures. Since migrations will be required for applications in Django 1.9,
     this behavior is considered deprecated. If you want to load initial data
     for an app, consider doing it in a :ref:`data migration <data-migrations>`.
 
@@ -116,7 +116,7 @@ Providing initial SQL data
 
     If an application uses migrations, there is no loading of initial SQL data
     (including backend-specific SQL data). Since migrations will be required
-    for applications in Django 2.0, this behavior is considered deprecated.
+    for applications in Django 1.9, this behavior is considered deprecated.
     If you want to use initial SQL for an app, consider doing it in a
     :ref:`data migration <data-migrations>`.