Fixed #6927: Corrected documentation describing when and why the auth application creates default permissions

git-svn-id: http://code.djangoproject.com/svn/django/trunk@7388 bcc190cf-cafb-0310-a4f2-bffc1f526a37

docs/authentication.txt

@@ -819,16 +819,17 @@ Django developers are currently discussing.
 Default permissions
 -------------------
 
-Three basic permissions -- add, change and delete -- are automatically created
+When ``django.contrib.auth`` is listed in your ``INSTALLED_APPS``
-for each Django model that has a ``class Admin`` set. Behind the scenes, these
+setting, it will ensure that three default permissions -- add, change
-permissions are added to the ``auth_permission`` database table when you run
+and delete -- are created for each Django model defined in one of your
-``manage.py syncdb``.
+installed applications.
 
-Note that if your model doesn't have ``class Admin`` set when you run
+These permissions will be created when you run ``manage.py syncdb``;
-``syncdb``, the permissions won't be created. If you initialize your database
+the first time you run ``syncdb`` after adding ``django.contrib.auth``
-and add ``class Admin`` to models after the fact, you'll need to run
+to ``INSTALLED_APPS``, the default permissions will be created for all
-``manage.py syncdb`` again. It will create any missing permissions for
+previously-installed models, as well as for any new models being
-all of your installed apps.
+installed at that time. Afterward, it will create default permissions
+for new models each time you run ``manage.py syncdb``.
 
 Custom permissions
 ------------------