diff --git a/source/conf.py b/source/conf.py
index 22b0e5e36..4516880ec 100644
--- a/source/conf.py
+++ b/source/conf.py
@@ -148,6 +148,8 @@
# Ignore while StackOverflow is blocking GitHub CI. Ref:
# https://github.com/pypa/packaging.python.org/pull/1474
r"https://stackoverflow\.com/.*",
+ # Cloudflare challenge blocks automated link checking.
+ r"https://clickpy\.clickhouse\.com/$",
r"https://pyscaffold\.org/.*",
r"https://anaconda\.org",
r"https://www\.cisa\.gov/sbom",
diff --git a/source/overview.rst b/source/overview.rst
index 70ef2d058..d7b3efdaf 100644
--- a/source/overview.rst
+++ b/source/overview.rst
@@ -279,7 +279,7 @@ A similar model involves installing an alternative Python
distribution, but does not support arbitrary operating system-level
packages:
-* `ActiveState ActivePython `_
+* `ActiveState ActivePython `_
* `WinPython `_
.. _bringing-your-own-python:
diff --git a/source/specifications/inline-script-metadata.rst b/source/specifications/inline-script-metadata.rst
index 6fa832a3e..f9df2f0f5 100644
--- a/source/specifications/inline-script-metadata.rst
+++ b/source/specifications/inline-script-metadata.rst
@@ -70,6 +70,17 @@ and the regular expression, the text specification takes precedence.
Tools MUST NOT read from metadata blocks with types that have not been
standardized by this specification.
+Note that the specification only requires that *top-level* comment blocks are
+recognised as containing metadata. However, parsing Python code is non-trivial,
+and therefore:
+
+* Tools MAY choose to do a simple textual scan, rather than a full Python parse.
+* As a result of the previous point, the behaviour of scripts that contain data
+ that looks like metadata within another Python construct such as a multi-line
+ string is tool-dependent and should not be relied on.
+* The canonical regular expression provided above is an example of an
+ implementation that does a simple textual scan.
+
script type
-----------