From dae6a9f701cf7b66b6b5ec76a0934ec2b87a03fc Mon Sep 17 00:00:00 2001 From: Cameron Gregor Date: Thu, 9 Mar 2023 08:19:10 +1100 Subject: [PATCH] docs: typo 'admnistrators' in security.mdx (#23166) --- docs/docs/security.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/security.mdx b/docs/docs/security.mdx index e868de6a9..b73e6db57 100644 --- a/docs/docs/security.mdx +++ b/docs/docs/security.mdx @@ -148,7 +148,7 @@ a certain resource type or policy area. You can check possible directives It's extremely important to correclty configure a Content Security Policy when deploying Superset to prevent many types of attacks. For that matter, Superset provides the ` TALISMAN_CONFIG` key in `config.py` -where admnistrators can define the policy. When running in production mode, Superset will check for the presence +where administrators can define the policy. When running in production mode, Superset will check for the presence of a policy and if it's not able to find one, it will issue a warning with the security risks. For environments where CSP policies are defined outside of Superset using other software, administrators can disable the warning using the `CONTENT_SECURITY_POLICY_WARNING` key in `config.py`.