docs: update knowledge gap from thread 1512031509387673610 (#12328)

Automatically generated PR targeting 1 files.

**Thread ID:** 1512031509387673610
**Action:** UPDATE

**AI Summary:**
> The documentation lacks clear explanation of how the 'Use new login
UI' checkbox and 'Custom base URL for the new Login UI' field work
together, including step-by-step configuration and troubleshooting
guidance.

---------

Co-authored-by: zitadel-knowledge-bot[bot] <296006658+zitadel-knowledge-bot[bot]@users.noreply.github.com>
Co-authored-by: fcoppede <[email protected]>

apps/docs/content/self-hosting/deploy/kubernetes/caching.mdx

@@ -14,7 +14,7 @@ Caching is an experimental beta feature. See the [Caches](/self-hosting/manage/c
 
 Zitadel supports Redis or any Redis-compatible store (for example, Valkey) in standalone mode. Sentinel and Redis Cluster are not supported because the cache connector expects a single endpoint and does not implement cluster routing or sentinel failover logic.
 
-<Callout type="note">
+<Callout type="info">
 Zitadel supports server-auth TLS (`rediss://` scheme) but does not support client certificates/mTLS for cache connections.
 </Callout>
 

apps/docs/content/self-hosting/manage/database/index.mdx

@@ -86,7 +86,7 @@ ZITADEL_DATABASE_POSTGRES_DSN=postgresql://zitadel:<strong-password>@<your-host>
 
 **Run setup and start**
 
-<Callout type="note">
+<Callout type="info">
 For production deployments, configure TLS to encrypt authentication traffic. See the [TLS configuration guide](/self-hosting/manage/tls_modes) for the available modes.
 </Callout>
 

apps/docs/content/self-hosting/manage/updating_scaling.mdx

@@ -65,7 +65,7 @@ when you install ZITADEL from scratch.
 **Schema bootstrapping step** (requires database owner privileges, uses the service user):
 - If they don’t exist already, it creates all schemas (`eventstore`, `projections`, `system`) and base tables.
 
-<Callout type="note">
+<Callout type="info">
 **Manual provisioning:** If you handle the provisioning step yourself (e.g. on a managed PostgreSQL service where you don’t have superuser access),
 you can skip it entirely by running only the schema bootstrapping step: