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 6060a95d47..84d2fbc29d 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
@@ -241,9 +241,9 @@ livenessProbe:
 
 Sometimes, you have to deal with legacy applications that might require
 an additional startup time on their first initialization.
-In such cases, it can be tricky to setup liveness probe parameters without
+In such cases, it can be tricky to set up liveness probe parameters without
 compromising the fast response to deadlocks that motivated such a probe.
-The trick is to setup a startup probe with the same command, HTTP or TCP
+The trick is to set up a startup probe with the same command, HTTP or TCP
 check, with a `failureThreshold * periodSeconds` long enough to cover the
 worse case startup time.