diff --git a/modules/storage-persistent-storage-reclaim-manual.adoc b/modules/storage-persistent-storage-reclaim-manual.adoc
new file mode 100644
index 0000000000..e6c94a049c
--- /dev/null
+++ b/modules/storage-persistent-storage-reclaim-manual.adoc
@@ -0,0 +1,26 @@
+// Module included in the following assemblies:
+//
+// * storage/understanding-persistent-storage.adoc
+
+[id="reclaim-manual_{context}"]
+= Reclaiming a PersistentVolume manually
+
+When a PersistentVolumeClaim (PVC) is deleted, the PersistentVolume (PV) still exists and is considered "released". However, the PV is not yet available for another claim because the previous claimant's data remains on the volume.
+
+.Procedure
+To manually reclaim the PV as a cluster administrator:
+
+. Delete the PV.
++
+[source,terminal]
+----
+$ oc delete <pv-name>
+----
++
+The associated storage asset in the external infrastructure, such as an AWS EBS, GCE PD, Azure Disk, or Cinder volume, still exists after the PV is deleted.
+
+. Clean up the data on the associated storage asset.
+
+. Delete the associated storage asset. Alternately, to reuse the same storage asset, create a new PV with the storage asset definition.
+
+The reclaimed PV is now available for use by another PVC.
diff --git a/storage/understanding-persistent-storage.adoc b/storage/understanding-persistent-storage.adoc
index 963d8e1be4..bd6175e2f6 100644
--- a/storage/understanding-persistent-storage.adoc
+++ b/storage/understanding-persistent-storage.adoc
@@ -8,6 +8,8 @@ include::modules/storage-persistent-storage-overview.adoc[leveloffset=+1]
 
 include::modules/storage-persistent-storage-lifecycle.adoc[leveloffset=+1]
 
+include::modules/storage-persistent-storage-reclaim-manual.adoc[leveloffset=+2]
+
 include::modules/storage-persistent-storage-reclaim.adoc[leveloffset=+2]
 
 include::modules/storage-persistent-storage-pv.adoc[leveloffset=+1]