Skip to content

Commit 746f5fd

Browse files
committed
Clarified "Add another question" as the plus sign button.
1 parent 7dc826b commit 746f5fd

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

docs/intro/tutorial07.txt

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -109,12 +109,12 @@ the database. Django knows that a :class:`~django.db.models.ForeignKey` should
109109
be represented in the admin as a ``<select>`` box. In our case, only one
110110
question exists at this point.
111111

112-
Also note the "Add another question" link next to "Question." Every object with
113-
a ``ForeignKey`` relationship to another gets this for free. When you click
114-
"Add another question", you'll get a popup window with the "Add question" form.
115-
If you add a question in that window and click "Save", Django will save the
116-
question to the database and dynamically add it as the selected choice on the
117-
"Add choice" form you're looking at.
112+
Also note the "Add another question" button (displayed as a plus sign) to the
113+
right of the "Question" field. Every ``ForeignKey`` relationship gets this
114+
button for free. When you click this button, you'll get a popup window with the
115+
"Add question" form. If you add a question in that window and click "Save",
116+
Django will save the question to the database and dynamically add it as the
117+
selected choice on the "Add choice" form you're looking at.
118118

119119
But, really, this is an inefficient way of adding ``Choice`` objects to the
120120
system. It'd be better if you could add a bunch of Choices directly when you

0 commit comments

Comments
 (0)