summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authork8s-ci-robot <k8s-ci-robot@users.noreply.github.com>2018-03-11 23:06:10 -0700
committerGitHub <noreply@github.com>2018-03-11 23:06:10 -0700
commitb0553136518abddd4b4a5bbfb1d28e99e7d976bf (patch)
tree4297e012731af16b745abcb546e46f4de89c81fc
parent63ff2ef5dc00162d8daa6aa60b40645858e16bb4 (diff)
parent6d9e3148b6e112dd363680365b991ecaa8e0a36a (diff)
Merge pull request #1891 from TinySong/fix-typo
fix typo
-rw-r--r--contributors/design-proposals/storage/grow-volume-size.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/storage/grow-volume-size.md b/contributors/design-proposals/storage/grow-volume-size.md
index e43680bd..4fb53292 100644
--- a/contributors/design-proposals/storage/grow-volume-size.md
+++ b/contributors/design-proposals/storage/grow-volume-size.md
@@ -137,7 +137,7 @@ func (og *operationGenerator) GenerateExpandVolumeFunc(
* Depending on volume type next steps would be:
* If volume is of type that does not require file system resize, then `pvc.status.capacity` will be immediately updated to reflect new size. This would conclude the volume expand operation. Also `pvc.Status.Conditions` will be updated with `Ready: True`.
- * If volume if of type that requires file system resize then a file system resize will be performed on kubelet. Read below for steps that will be performed for file system resize.
+ * If volume is of type that requires file system resize then a file system resize will be performed on kubelet. Read below for steps that will be performed for file system resize.
* If volume plugin is of type that can not do resizing of attached volumes (such as `Cinder`) then `ExpandVolumeDevice` can return error by checking for
volume status with its own API (such as by making Openstack Cinder API call in this case). Controller will keep trying to resize the volume until it is