summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Lord <davidism@gmail.com>2022-03-11 14:38:25 -0800
committerDavid Lord <davidism@gmail.com>2022-03-11 14:38:25 -0800
commit186aa82f7e385c9c796e47cec83cc289c3cbe497 (patch)
treeed2b4da00b1de45e19e18b08fac5fcfbecb04aad
parent4bbb1fb5fe5ec141d302c5baff95165887fb7338 (diff)
parent5962edeb271d93687eb93f32d53ffe53f86871e0 (diff)
downloadjinja2-186aa82f7e385c9c796e47cec83cc289c3cbe497.tar.gz
Merge branch '3.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 8584d77..ca1f9aa 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