From d60bc3de31fafff2981a7f80af4baa2b85ac3923 Mon Sep 17 00:00:00 2001
From: giri <32255588+gprasath@users.noreply.github.com>
Date: Fri, 19 Apr 2019 13:35:55 +0530
Subject: [PATCH] Update persistent-volumes.md (#13851)

---
 content/en/docs/concepts/storage/persistent-volumes.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/storage/persistent-volumes.md b/content/en/docs/concepts/storage/persistent-volumes.md
index cb2cbef8a3..076013be00 100644
--- a/content/en/docs/concepts/storage/persistent-volumes.md
+++ b/content/en/docs/concepts/storage/persistent-volumes.md
@@ -88,7 +88,7 @@ The purpose of the Storage Object in Use Protection feature is to ensure that Pe
 PVC is in active use by a pod when a pod object exists that is using the PVC.
 {{< /note >}}
 
-If a user deletes a PVC in active use by a pod, the PVC is not removed immediately. PVC removal is postponed until the PVC is no longer actively used by any pods, and also if admin deletes a PV that is bound to a PVC, the PV is not removed immediately. PV removal is postponed until the PV is no longer no bound to a PVC.
+If a user deletes a PVC in active use by a pod, the PVC is not removed immediately. PVC removal is postponed until the PVC is no longer actively used by any pods, and also if admin deletes a PV that is bound to a PVC, the PV is not removed immediately. PV removal is postponed until the PV is no longer bound to a PVC.
 
 You can see that a PVC is protected when the PVC's status is `Terminating` and the `Finalizers` list includes `kubernetes.io/pvc-protection`: