From 259e312ff2776cd8054ae4674ecd36e23cf792fa Mon Sep 17 00:00:00 2001 From: Meysam Azad Date: Tue, 15 Feb 2022 19:16:42 +0300 Subject: [PATCH] =?UTF-8?q?docs:=20remove=20redundant=20word=20?= =?UTF-8?q?=F0=9F=93=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- 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 11a5611b36..7a11939507 100644 --- a/content/en/docs/concepts/storage/persistent-volumes.md +++ b/content/en/docs/concepts/storage/persistent-volumes.md @@ -339,7 +339,7 @@ If that has happened, or you suspect that it might have, you can retry expansion size that is within the capacity limits of underlying storage provider. You can monitor status of resize operation by watching `.status.resizeStatus` and events on the PVC. Note that, -although you can a specify a lower amount of storage than what was requested previously, +although you can specify a lower amount of storage than what was requested previously, the new value must still be higher than `.status.capacity`. Kubernetes does not support shrinking a PVC to less than its current size. {{% /tab %}}