From 8c78cba47f78f6b56ca1948b108f0f37965f387d Mon Sep 17 00:00:00 2001
From: Aymeric Augustin <aymeric.augustin@m4x.org>
Date: Tue, 24 Dec 2013 23:48:22 +0100
Subject: [PATCH] Copy-edited previous commit.
Thanks Tim for the review.
---
docs/ref/settings.txt | 2 +-
docs/releases/1.7.txt | 7 +++----
2 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt
index d82f68a2a4..e9b98fb711 100644
--- a/docs/ref/settings.txt
+++ b/docs/ref/settings.txt
@@ -1297,7 +1297,7 @@ application. :ref:` Learn more about applications </ref/applications>`.
.. admonition:: Use the application registry for introspection
Your code should never access :setting:`INSTALLED_APPS` directly. Use the
- app registry, :attr:`~django.apps.apps`, instead.
+ app registry, :attr:`django.apps.apps`, instead.
.. admonition:: Application labels must be unique
diff --git a/docs/releases/1.7.txt b/docs/releases/1.7.txt
index ab2aa3442b..5aba3ca096 100644
--- a/docs/releases/1.7.txt
+++ b/docs/releases/1.7.txt
@@ -66,12 +66,11 @@ known as the "app cache" dealt with both installed applications and models.
The models module was used as an identifier for applications in many APIs.
As the concept of :doc:`Django applications </ref/applications>` matured, this
-code showed some shortcomings. It was refactored into an "app registry" where
-models modules no longer have a central role models and where it's possible to
+code showed some shortcomings. It has been refactored into an "app registry"
+where models modules no longer have a central role and where it's possible to
attach configuration data to applications.
-Not only does this prepare the ground for further improvements, but it also
-brings some concrete improvements:
+Improvements thus far include:
* It is possible to omit ``models.py`` entirely if an application doesn't
have any models.