Merge pull request #12930 from liangxia/reclaim_policy

Fix persistent volume reclaim policy, bug 1652782
openshift · Nov 23, 2018 · 5370fbe · 5370fbe
2 parents 5044032 + 704e3c2
commit 5370fbe
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/architecture/additional_concepts/storage.adoc b/architecture/additional_concepts/storage.adoc
@@ -123,9 +123,9 @@ to policy.
 === Reclaim volumes
 
 The reclaim policy of a `PersistentVolume` tells the cluster what to do with
-the volume after it is released. Volumes reclaim policy can either be `Retained`, `Recycled`, or `Deleted`.
+the volume after it is released. Volumes reclaim policy can either be `Retain`, `Recycle`, or `Delete`.
 
-`Retained` reclaim policy allows manual reclamation of the resource for those volume plug-ins that support it. `Deleted` reclaim policy deletes both the `PersistentVolume` object from {product-title} and the associated storage asset in external infrastructure, such as AWS EBS, GCE PD, or Cinder volume.
+`Retain` reclaim policy allows manual reclamation of the resource for those volume plug-ins that support it. `Delete` reclaim policy deletes both the `PersistentVolume` object from {product-title} and the associated storage asset in external infrastructure, such as AWS EBS, GCE PD, or Cinder volume.
 
 [NOTE]
 ====