Browse files

Fixed #15827 - Documented that OneToOneField in Profile should be nam…

…ed 'user'; thanks lawgon.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 367e51e commit 127f1e4190265a3caf1a0dba6071582256feb2af @timgraham timgraham committed May 4, 2011
Showing with 2 additions and 2 deletions.
  1. +2 −2 docs/topics/auth.txt
@@ -467,8 +467,8 @@ profile" -- for this purpose.
To make use of this feature, define a model with fields for the
additional information you'd like to store, or additional methods
you'd like to have available, and also add a
-:class:`~django.db.models.Field.OneToOneField` from your model to the
-:class:`~django.contrib.auth.models.User` model. This will ensure only
+:class:`~django.db.models.Field.OneToOneField` named ``user`` from your model
+to the :class:`~django.contrib.auth.models.User` model. This will ensure only
one instance of your model can be created for each

0 comments on commit 127f1e4

Please sign in to comment.