Add “Advanced Feature” callout to relevant docs pages

docs/_partials/advanced-feature-callout.mdx

@@ -0,0 +1,2 @@
+> [!IMPORTANT]
+> This feature or workflow is considered **advanced** - it may not be part of an official Clerk SDK or fall within typical usage patterns. The Clerk support team will do their best to assist you, but cannot guarantee a resolution for this type of advanced usage.

docs/guides/dashboard/dns-domains/proxy-fapi.mdx

@@ -3,15 +3,17 @@ title: Proxying the Clerk Frontend API
 description: Learn how to proxy the Clerk Frontend API through your domain.
 ---
 
-> [!WARNING]
-> This guide is for users who need to proxy the Frontend API for **production** (proxying does not work for Clerk development instances). If your application already uses a CNAME subdomain that is required for deploying with Clerk, then you must proxy the Frontend API using a different subdomain. Refer to the [deployment guide](/docs/guides/development/deployment/production#dns-records) on how to configure DNS records for deployment.
+<Include src="_partials/advanced-feature-callout" />
 
 Clerk supports two configuration methods for connecting to the Clerk Frontend API: CNAME and Proxy.
 
 The recommended way to connect to the Clerk Frontend API is to [set up CNAME records and use DNS](/docs/guides/development/deployment/production). However, if you're unable to use this approach, or would like more control over your integration with Clerk, you can use a proxy.
 
 When using a proxy, all requests to the Frontend API will be made through your domain. This allows you to use your own SSL certificate, and gives you more control over how you configure your application.
 
+> [!WARNING]
+> This guide is for users who need to proxy the Frontend API for **production** (proxying does not work for Clerk development instances). If your application already uses a CNAME subdomain that is required for deploying with Clerk, then you must proxy the Frontend API using a different subdomain. Refer to the [deployment guide](/docs/guides/development/deployment/production#dns-records) on how to configure DNS records for deployment.
+
 ## How to use proxying
 
 <Steps>

docs/guides/dashboard/dns-domains/satellite-domains.mdx

@@ -3,6 +3,8 @@ title: Authentication across different domains
 description: Learn how to share sessions across different domains by adding satellite domains to your application.
 ---
 
+<Include src="_partials/advanced-feature-callout" />
+
 > [!WARNING]
 > This guide addresses authentication across different domains with shared sessions. For example, `example-site.com` and `example-site-admin.com`.
 >

docs/guides/development/custom-flows/overview.mdx

@@ -5,7 +5,9 @@ description: Learn the process behind building custom sign-up and sign-in flows
 
 A **custom flow** refers to a user interface built entirely from scratch using the Clerk API.
 
-Custom flows are not recommended for most use cases as they require more development effort and are not as easy to maintain as the prebuilt components. However, if [prebuilt components](/docs/reference/components/overview) don't meet your specific needs or if you require more control over the logic, you can rebuild the existing Clerk flows using the Clerk API.
+Custom flows are considered **advanced** and are generally not recommended for most use cases. They require more development effort and are not as easy to maintain as the prebuilt components. However, if [prebuilt components](/docs/reference/components/overview) don't meet your specific needs or if you require more control over the logic, you can rebuild the existing Clerk flows using the Clerk API.
+
+**If you choose this approach, the Clerk support team will do their best to assist you, but they cannot guarantee a resolution due to the highly customized nature of custom flows.**
 
 > [!TIP]
 > The information in this guide will help you get a general understanding of custom flow concepts. To skip to code examples, choose the guide that best fits your needs from the navigation on the left.