From ff82da17b615c13cb4e46f251a5c0c6cdeedc633 Mon Sep 17 00:00:00 2001
From: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
Date: Sun, 20 Aug 2023 19:56:14 +0100
Subject: [3.11] Resolve reference warnings in faq/design.rst (GH-108148)
 (#108181)

---
 Doc/faq/design.rst   | 4 ++--
 Doc/tools/.nitignore | 1 -
 2 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/Doc/faq/design.rst b/Doc/faq/design.rst
index 9dbfacd..83c0152 100644
--- a/Doc/faq/design.rst
+++ b/Doc/faq/design.rst
@@ -581,9 +581,9 @@ exhaustive test suites that exercise every line of code in a module.
 An appropriate testing discipline can help build large complex applications in
 Python as well as having interface specifications would.  In fact, it can be
 better because an interface specification cannot test certain properties of a
-program.  For example, the :meth:`append` method is expected to add new elements
+program.  For example, the :meth:`!list.append` method is expected to add new elements
 to the end of some internal list; an interface specification cannot test that
-your :meth:`append` implementation will actually do this correctly, but it's
+your :meth:`!list.append` implementation will actually do this correctly, but it's
 trivial to check this property in a test suite.
 
 Writing test suites is very helpful, and you might want to design your code to
diff --git a/Doc/tools/.nitignore b/Doc/tools/.nitignore
index f36e2b8..319c777 100644
--- a/Doc/tools/.nitignore
+++ b/Doc/tools/.nitignore
@@ -24,7 +24,6 @@ Doc/c-api/typeobj.rst
 Doc/c-api/unicode.rst
 Doc/extending/extending.rst
 Doc/extending/newtypes.rst
-Doc/faq/design.rst
 Doc/faq/gui.rst
 Doc/faq/library.rst
 Doc/glossary.rst
-- 
cgit v0.12