From 4aa772302740f50c0301493ddf3ab8e88df5f629 Mon Sep 17 00:00:00 2001
From: Xiang Dai <764524258@qq.com>
Date: Mon, 12 Aug 2019 20:19:12 +0800
Subject: [PATCH] Update disruptions.md (#15811)

The number of StatefulSet always start from 0, change to make docs exact.

Signed-off-by: Xiang Dai <764524258@qq.com>
---
 content/en/docs/concepts/workloads/pods/disruptions.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/en/docs/concepts/workloads/pods/disruptions.md b/content/en/docs/concepts/workloads/pods/disruptions.md
index 6ef7ac8f8b..00265e0433 100644
--- a/content/en/docs/concepts/workloads/pods/disruptions.md
+++ b/content/en/docs/concepts/workloads/pods/disruptions.md
@@ -169,8 +169,8 @@ The deployment notices that one of the pods is terminating, so it creates a repl
 called `pod-d`.  Since `node-1` is cordoned, it lands on another node.  Something has
 also created `pod-y` as a replacement for `pod-x`.
 
-(Note: for a StatefulSet, `pod-a`, which would be called something like `pod-1`, would need
-to terminate completely before its replacement, which is also called `pod-1` but has a
+(Note: for a StatefulSet, `pod-a`, which would be called something like `pod-0`, would need
+to terminate completely before its replacement, which is also called `pod-0` but has a
 different UID, could be created.  Otherwise, the example applies to a StatefulSet as well.)
 
 Now the cluster is in this state: