diff --git a/docs/api_stability.txt b/docs/api_stability.txt index 508336e0ef..3fd793b0fd 100644 --- a/docs/api_stability.txt +++ b/docs/api_stability.txt @@ -101,7 +101,7 @@ change: .. _caching: ../cache/ .. _custom template tags and libraries: ../templates_python/ .. _database lookup: ../db_api/ -.. _django-admin utility: ../django_admin/ +.. _django-admin utility: ../django-admin/ .. _fastcgi integration: ../fastcgi/ .. _flatpages: ../flatpages/ .. _generic views: ../generic_views/ diff --git a/docs/legacy_databases.txt b/docs/legacy_databases.txt index 3228f58bb7..ca3927e52f 100644 --- a/docs/legacy_databases.txt +++ b/docs/legacy_databases.txt @@ -52,7 +52,7 @@ Once you've cleaned up your models, name the file ``models.py`` and put it in the Python package that holds your app. Then add the app to your ``INSTALLED_APPS`` setting. -.. _django-admin.py documentation: ../django_admin/ +.. _django-admin.py documentation: ../django-admin/ Install the core Django tables ============================== diff --git a/docs/model-api.txt b/docs/model-api.txt index 7fe099e022..b71668e37f 100644 --- a/docs/model-api.txt +++ b/docs/model-api.txt @@ -1924,7 +1924,7 @@ order in which they're executed. The only thing you can assume is that, by the time your custom data files are executed, all the database tables already will have been created. -.. _`manage.py documentation`: ../django_admin/#sqlcustom-appname-appname +.. _`manage.py documentation`: ../django-admin/#sqlcustom-appname-appname Database-backend-specific SQL data ---------------------------------- diff --git a/docs/settings.txt b/docs/settings.txt index 63b5cceef9..45bdfa573d 100644 --- a/docs/settings.txt +++ b/docs/settings.txt @@ -59,7 +59,7 @@ Use the ``--settings`` command-line argument to specify the settings manually:: django-admin.py runserver --settings=mysite.settings -.. _django-admin.py: ../django_admin/ +.. _django-admin.py: ../django-admin/ On the server (mod_python) -------------------------- @@ -102,7 +102,7 @@ between the current settings file and Django's default settings. For more, see the `diffsettings documentation`_. -.. _diffsettings documentation: ../django_admin/#diffsettings +.. _diffsettings documentation: ../django-admin/#diffsettings Using settings in Python code ============================= @@ -462,7 +462,7 @@ A tuple of strings designating all applications that are enabled in this Django installation. Each string should be a full Python path to a Python package that contains a Django application, as created by `django-admin.py startapp`_. -.. _django-admin.py startapp: ../django_admin/#startapp-appname +.. _django-admin.py startapp: ../django-admin/#startapp-appname INTERNAL_IPS ------------ diff --git a/docs/testing.txt b/docs/testing.txt index 5b27ae6484..a135734144 100644 --- a/docs/testing.txt +++ b/docs/testing.txt @@ -404,7 +404,7 @@ In this example, any JSON fixture called ``mammals``, and any fixture named ``birds`` will be installed. See the documentation on `loading fixtures`_ for more details on defining and installing fixtures. -.. _`loading fixtures`: ../django_admin/#loaddata-fixture-fixture +.. _`loading fixtures`: ../django-admin/#loaddata-fixture-fixture This flush/load procedure is repeated for each test in the test case, so you can be certain that the outcome of a test will not be affected by diff --git a/docs/tutorial01.txt b/docs/tutorial01.txt index e768af693e..7657bc7bf7 100644 --- a/docs/tutorial01.txt +++ b/docs/tutorial01.txt @@ -124,7 +124,7 @@ It worked! Full docs for the development server are at `django-admin documentation`_. -.. _django-admin documentation: ../django_admin/ +.. _django-admin documentation: ../django-admin/ Database setup -------------- @@ -400,7 +400,7 @@ as you like, and it will only ever create the tables that don't exist. Read the `django-admin.py documentation`_ for full information on what the ``manage.py`` utility can do. -.. _django-admin.py documentation: ../django_admin/ +.. _django-admin.py documentation: ../django-admin/ Playing with the API ====================