[3.12] Resolve reference warnings in faq/design.rst (GH-108148) (#108180)

Resolve reference warnings in faq/design.rst (GH-108148)
(cherry picked from commit 92815cc7cf3df8ab702c7cea4efaef349a4b0480)

Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>

diff --git a/Doc/faq/design.rst b/Doc/faq/design.rst
index 11d01374dc1e79166bb1060672d4a70da38bb978..ae02c443e5938bf43220b9c28cf27814638f1db3 100644 (file)
--- a/Doc/faq/design.rst
+++ b/Doc/faq/design.rst
@@ -584,9 +584,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:`list.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:`list.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 ba976bc50cf2015a0319be2e02247b0073c7e340..5a28274cff6c4f91dde6b3f4761c3cf766dce50a 100644 (file)
--- a/Doc/tools/.nitignore
+++ b/Doc/tools/.nitignore
@@ -25,7 +25,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