From 77ecc224b893b56c1796858623e034c1e062eca0 Mon Sep 17 00:00:00 2001
From: Henry Liu <henry.liu@daocloud.io>
Date: Tue, 2 Mar 2021 15:11:18 +0800
Subject: [PATCH] change callout from warning to caution

---
 .../configure-liveness-readiness-startup-probes.md            | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
index e12e2684a6..0cdfd28258 100644
--- a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
+++ b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
@@ -293,9 +293,9 @@ Services.
 Readiness probes runs on the container during its whole lifecycle.
 {{< /note >}}
 
-{{< warning >}}
+{{< caution >}}
 Liveness probes *do not* wait for readiness probes to succeed. If you want to wait before executing a liveness probe you should use initialDelaySeconds or a startupProbe.
-{{< /warning >}}
+{{< /caution >}}
 
 Readiness probes are configured similarly to liveness probes. The only difference
 is that you use the `readinessProbe` field instead of the `livenessProbe` field.