Skip to content

Commit f35cc22

Browse files
committed
PEP 504: Fix Sphinx reference warnings
For #4087. The problematic footnotes are actually referenced, the syntax is just slightly incorrect.
1 parent 8e4a7b6 commit f35cc22

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

peps/pep-0504.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -177,7 +177,7 @@ This is reflected in regular notifications of data breaches involving personally
177177
identifiable information [#breaches]_, as well as with failures to take
178178
security considerations into account when new systems, like motor vehicles
179179
[#uconnect]_, are connected to the internet. It's also the case that a lot of
180-
the programming advice readily available on the internet [#search] simply
180+
the programming advice readily available on the internet [#search]_ simply
181181
doesn't take the mathematical arcana of computer security into account.
182182
Compounding these issues is the fact that defenders have to cover *all* of
183183
their potential vulnerabilities, as a single mistake can make it possible to
@@ -277,7 +277,7 @@ generator towards explicitly calling ``random.ensure_repeatable()``.
277277
Avoiding the introduction of a userspace CSPRNG
278278
-----------------------------------------------
279279

280-
The original discussion of this proposal on python-ideas[#csprng]_ suggested
280+
The original discussion of this proposal on python-ideas [#csprng]_ suggested
281281
introducing a cryptographically secure pseudo-random number generator and using
282282
that by default, rather than defaulting to the relatively slow system random
283283
number generator.

0 commit comments

Comments
 (0)