From c05bf93558063fc4212ec8a97e0855ce2a7f4371 Mon Sep 17 00:00:00 2001 From: azEf Date: Wed, 18 Jul 2018 00:15:18 +0200 Subject: [PATCH] Fix typo in persistent-volumes.md (#9550) --- 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 7c17119f7f..c410b6578c 100644 --- a/content/en/docs/concepts/storage/persistent-volumes.md +++ b/content/en/docs/concepts/storage/persistent-volumes.md @@ -215,7 +215,7 @@ You can only resize volumes containing a file system if the file system is XFS, When a volume contains a file system, the file system is only resized when a new Pod is started using the `PersistentVolumeClaim` in ReadWrite mode. Therefore, if a pod or deployment is using a volume and -you want to expand it, you need to delete or recreate the pod after the volume has been exxpanded by the cloud provider in the controller-manager. You can check the status of resize operation by running the `kubectl describe pvc` command: +you want to expand it, you need to delete or recreate the pod after the volume has been expanded by the cloud provider in the controller-manager. You can check the status of resize operation by running the `kubectl describe pvc` command: ``` kubectl describe pvc