This is a Bug Report

Problem:
The page at:
https://kubernetes.io/docs/concepts/storage/volume-pvc-datasource/
states:
"The implementation of cloning, from the perspective of the Kubernetes API simply adds the ability to specify an existing unbound PVC as a dataSource during new pvc creation."

I think "unbound PVC" is incorrect as without binding, there is no volume that can be cloned.

Proposed Solution:

It seems to me that changing "unbound" to "bound" should fix the issue.

Page to Update:
https://kubernetes.io/docs/concepts/storage/volume-pvc-datasource/