From c377278f64a42dc1275175bb43ad9608d4ea283f Mon Sep 17 00:00:00 2001
From: Wen Bo Xie <wenbox323@gmail.com>
Date: Tue, 25 Nov 2025 16:19:02 +0800
Subject: [PATCH] updates

---
 .../content/guides/integrations/platform-as-a-service.mdx     | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/apps/docs/content/guides/integrations/platform-as-a-service.mdx b/apps/docs/content/guides/integrations/platform-as-a-service.mdx
index 45d5e87f3c1..9bc3fa98e66 100644
--- a/apps/docs/content/guides/integrations/platform-as-a-service.mdx
+++ b/apps/docs/content/guides/integrations/platform-as-a-service.mdx
@@ -242,7 +242,7 @@ It will not affect:
 
 ### Add seed data
 
-<Admonition type="warning" title="Do not use production data in branches!">
+<Admonition type="caution" title="Do not use production data in branches!">
 
 It's important that the data in development branches is NOT production data, especially for non-developers who don't understand the implications of working with data. Security and side-effects (e.g. emailing all production users) are two reasons why this is important.
 
@@ -366,7 +366,7 @@ The user is redirected to a Supabase UI:
 4.  Review the Project transfer details
 5.  Confirm the OAuth integration and the Project transfer for the selected Organization
 
-<Admonition type="warning" title="Remove custom configuration before transferring project">
+<Admonition type="caution" title="Remove custom configuration before transferring project">
 
 Before transferring the project to your user's org, make sure to remove any custom configuration that you do not want your user's project to retain.