From 5d0fc131538a86bc5898c850b6e46122d2f04c8b Mon Sep 17 00:00:00 2001
From: Sarah Boyce <42296566+sarahboyce@users.noreply.github.com>
Date: Tue, 7 Apr 2026 12:16:21 +0200
Subject: [6.0.x] Clarified "Add another question" as the plus sign button.

Backport of 746f5fd23e50589ef3ad27b1dad46b569f600fa0 from main.
---
 docs/intro/tutorial07.txt | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/intro/tutorial07.txt b/docs/intro/tutorial07.txt
index b7638e365c..1a1db1db66 100644
--- a/docs/intro/tutorial07.txt
+++ b/docs/intro/tutorial07.txt
@@ -109,12 +109,12 @@ the database. Django knows that a :class:`~django.db.models.ForeignKey` should
 be represented in the admin as a ``<select>`` box. In our case, only one
 question exists at this point.
 
-Also note the "Add another question" link next to "Question." Every object with
-a ``ForeignKey`` relationship to another gets this for free. When you click
-"Add another question", you'll get a popup window with the "Add question" form.
-If you add a question in that window and click "Save", Django will save the
-question to the database and dynamically add it as the selected choice on the
-"Add choice" form you're looking at.
+Also note the "Add another question" button (displayed as a plus sign) to the
+right of the "Question" field. Every ``ForeignKey`` relationship gets this
+button for free. When you click this button, you'll get a popup window with the
+"Add question" form. If you add a question in that window and click "Save",
+Django will save the question to the database and dynamically add it as the
+selected choice on the "Add choice" form you're looking at.
 
 But, really, this is an inefficient way of adding ``Choice`` objects to the
 system. It'd be better if you could add a bunch of Choices directly when you
-- 
cgit v1.3