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/guides/integrate/actions/migrate-from-v1.mdx

@@ -6,7 +6,7 @@ sidebar_label: Migrate from V1 to V2
 
 This guide helps existing users understand the shift from Actions V1 (Embedded) to V2 (Webhook), and provides guidance for new users on how to work with Actions V2.
 
-<Callout type="caution">
+<Callout type="warn">
 Deprecation Notice
 Actions V1 APIs are planned to be sunsetted in ZITADEL V5. While a definitive V5 release date is not yet available, this is the final timeline for V1 API removal. Actions V1 will receive no new features, and all new implementations must use V2.
 </Callout>

apps/docs/content/guides/integrate/identity-providers/openldap.mdx

@@ -20,7 +20,7 @@ You have to spin up your own local ZITADEL.
 The easiest way to do so is [by following the Docker Compose installation guide](/self-hosting/deploy/compose).
 </Callout>
 
-<Callout type="caution">
+<Callout type="warn">
 Beware that these example settings neither supports LDAPS nor StartTLS.
 We highly recommend to enable LDAPS or StartTLS in your production setup.
 Otherwise, your users passwords are sent in clear text through the wire.