Clarify signed embedding uses session-based auth, not JWT (cube-js#10574)

Generated-By: mintlify-agent

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>

Author: mintlify[bot]

docs-mintlify/embedding/index.mdx

@@ -18,7 +18,7 @@ Iframe embedding supports [dashboards](/analytics/dashboards), [analytics chat](
 
 **Authentication options:**
 - **[Private embedding](/embedding/private-embedding)** – For internal use cases where users authenticate with their Cube accounts
-- **[Signed embedding](/embedding/signed-embedding)** – For customer-facing applications using JWT tokens for seamless authentication
+- **[Signed embedding](/embedding/signed-embedding)** – For customer-facing applications using secure, server-generated sessions for authentication
 
 ## React component-based embedding
 

docs-mintlify/embedding/signed-embedding.mdx

@@ -9,7 +9,7 @@ description: Signed embedding is available on Premium and Enterprise plans.
   Signed embedding is available on [Premium and Enterprise plans](https://cube.dev/pricing).
 </Info>
 
-Signed embedding is designed for **external, customer-facing analytics**. It uses JWT tokens for seamless authentication, making it ideal for:
+Signed embedding is designed for **external, customer-facing analytics**. It uses secure, server-generated sessions for authentication, making it ideal for:
 
 - Embedding analytics in your SaaS application for customers
 - White-label analytics solutions