diff --git a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md
index 6750af2063..36c4f758ac 100644
--- a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md
+++ b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md
@@ -235,12 +235,17 @@ livenessProbe:
 
 Sometimes, applications are temporarily unable to serve traffic.
 For example, an application might need to load large data or configuration
-files during startup. In such cases, you don't want to kill the application,
+files during startup, or depend on external services after startup.
+In such cases, you don't want to kill the application,
 but you don’t want to send it requests either. Kubernetes provides
 readiness probes to detect and mitigate these situations. A pod with containers
 reporting that they are not ready does not receive traffic through Kubernetes
 Services.
 
+{{< note >}}
+Readiness probes runs on the container during its whole lifecycle.
+{{< /note >}}
+
 Readiness probes are configured similarly to liveness probes. The only difference
 is that you use the `readinessProbe` field instead of the `livenessProbe` field.