This is an automated email from the ASF dual-hosted git repository.

sfirke pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/superset.git


The following commit(s) were added to refs/heads/master by this push:
     new db5edb3a42 chore(docs): add closing ::: to caution tag (#28236)
db5edb3a42 is described below

commit db5edb3a424e8cc9976c0b8b714119b55336fd93
Author: Sam Firke <[email protected]>
AuthorDate: Fri Apr 26 14:38:58 2024 -0400

    chore(docs): add closing ::: to caution tag (#28236)
---
 docs/docs/configuration/configuring-superset.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/docs/configuration/configuring-superset.mdx 
b/docs/docs/configuration/configuring-superset.mdx
index 8dde5757e7..9e28d3e78a 100644
--- a/docs/docs/configuration/configuring-superset.mdx
+++ b/docs/docs/configuration/configuring-superset.mdx
@@ -99,9 +99,9 @@ SECRET_KEY = 'YOUR_OWN_RANDOM_GENERATED_SECRET_KEY'
 
 You can generate a strong secure key with `openssl rand -base64 42`.
 
-:::caution Your secret key will be used for securely signing session cookies
-and encrypting sensitive information stored in Superset's application metadata 
database.
-  Make sure you are changing this key for your deployment with a strong key.
+:::caution Use a strong secret key
+This key will be used for securely signing session cookies and encrypting 
sensitive information stored in Superset's application metadata database.
+Your deployment must use a complex, unique key. :::
 
 #### Rotating to a newer SECRET_KEY
 

Reply via email to