summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Lord <davidism@gmail.com>2022-03-11 14:37:22 -0800
committerDavid Lord <davidism@gmail.com>2022-03-11 14:37:22 -0800
commit5962edeb271d93687eb93f32d53ffe53f86871e0 (patch)
tree962dfce5bd6b225a67774a893830ab90f8f11911
parent681f8de8421183cf4ed35547c723cb0a3d9a2955 (diff)
parentaa3d688a15aece0a0de0b59f94dda870c724bc87 (diff)
downloadjinja2-3.0.x.tar.gz
Merge branch '2.11.x' into 3.0.x3.0.x
-rw-r--r--docs/faq.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/faq.rst b/docs/faq.rst
index dd78217..3e1af52 100644
--- a/docs/faq.rst
+++ b/docs/faq.rst
@@ -95,7 +95,7 @@ means that you will less likely have an XSS problem it also causes a huge
amount of extra processing in the template engine which can cause serious
performance problems. As Python doesn't provide a way to mark strings as
unsafe Jinja has to hack around that limitation by providing a custom
-string class (the :class:`Markup` string) that safely interacts with safe
+string class (the :class:`~markupsafe.Markup` string) that safely interacts with safe
and unsafe strings.
With explicit escaping however the template engine doesn't have to perform