From 920d558fde160d4d86ae853c785785b44608be11 Mon Sep 17 00:00:00 2001
From: Andrii Dembitskyi <andrew.dembitskiy@gmail.com>
Date: Wed, 13 Nov 2019 09:24:12 +0200
Subject: [PATCH] Fixed readiness/liveness probe example in docs

---
 docs/gitbook/tutorials/zero-downtime-deployments.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/gitbook/tutorials/zero-downtime-deployments.md b/docs/gitbook/tutorials/zero-downtime-deployments.md
index 4eb73bb4..e40d8e67 100644
--- a/docs/gitbook/tutorials/zero-downtime-deployments.md
+++ b/docs/gitbook/tutorials/zero-downtime-deployments.md
@@ -27,7 +27,7 @@ You application should expose a HTTP endpoint that Kubernetes can call to determ
 your app transitioned to a broken state from which it can't recover and needs to be restarted.
 
 ```yaml
-readinessProbe:
+livenessProbe:
   exec:
     command:
     - wget
@@ -49,7 +49,7 @@ You application should expose a HTTP endpoint that Kubernetes can call to determ
 your app is ready to receive traffic.
 
 ```yaml
-livenessProbe:
+readinessProbe:
   exec:
     command:
     - wget