From 194fe9953267e6049bfb7101e49c1346eab0e897 Mon Sep 17 00:00:00 2001
From: Jihoon Seo <46767780+jihoon-seo@users.noreply.github.com>
Date: Fri, 26 Mar 2021 14:59:24 +0900
Subject: [PATCH] Update concepts/storage/volumes.md

---
 content/en/docs/concepts/storage/volumes.md | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/content/en/docs/concepts/storage/volumes.md b/content/en/docs/concepts/storage/volumes.md
index 8ed91067e06..4c944b6909b 100644
--- a/content/en/docs/concepts/storage/volumes.md
+++ b/content/en/docs/concepts/storage/volumes.md
@@ -33,10 +33,9 @@ drivers, but the functionality is somewhat limited.
 Kubernetes supports many types of volumes. A {{< glossary_tooltip term_id="pod" text="Pod" >}}
 can use any number of volume types simultaneously.
 Ephemeral volume types have a lifetime of a pod, but persistent volumes exist beyond
-the lifetime of a pod. Consequently, a volume outlives any containers
-that run within the pod, and data is preserved across container restarts. When a pod
-ceases to exist, Kubernetes destroys ephemeral volumes; however, Kubernetes does not
-destroy persistent volumes.
+the lifetime of a pod. When a pod ceases to exist, Kubernetes destroys ephemeral volumes; 
+however, Kubernetes does not destroy persistent volumes. 
+For any kind of volume in a given pod, data is preserved across container restarts.
 
 At its core, a volume is just a directory, possibly with some data in it, which
 is accessible to the containers in a pod. How that directory comes to be, the