From 00abf7a80f3a97f87254b60f2108f82e57094f4b Mon Sep 17 00:00:00 2001 From: Tom Boettger Date: Tue, 8 Sep 2020 12:37:51 +0200 Subject: [PATCH] Fix false Object in persistentVolumeClaim explanation The persistentVolumeClaim explanation was contradictory. I've changed it, since PersistentVolumeClaims are an abstraction layer for PersistentVolumes, which in turn "capture[..] the details of the implementation of the storage". --- content/en/docs/concepts/storage/volumes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md index 1793a7a5f8..19d491b1b3 100644 --- a/content/en/docs/concepts/storage/volumes.md +++ b/content/en/docs/concepts/storage/volumes.md @@ -756,8 +756,8 @@ See the [NFS example](https://github.com/kubernetes/examples/tree/{{< param "git ### persistentVolumeClaim {#persistentvolumeclaim} A `persistentVolumeClaim` volume is used to mount a -[PersistentVolume](/docs/concepts/storage/persistent-volumes/) into a Pod. PersistentVolumes are a -way for users to "claim" durable storage (such as a GCE PersistentDisk or an +[PersistentVolume](/docs/concepts/storage/persistent-volumes/) into a Pod. PersistentVolumeClaims +are a way for users to "claim" durable storage (such as a GCE PersistentDisk or an iSCSI volume) without knowing the details of the particular cloud environment. See the [PersistentVolumes example](/docs/concepts/storage/persistent-volumes/) for more