anchor.diff:  
   === Resources
   
  -Claims, like pods, can request specific quantities of a resource.  In this case, the request is for storage.  The same [resource model](./resources.md) applies to both volumes and claims.
  +Claims, like pods, can request specific quantities of a resource.  In this case, the request is for storage.  The same link:https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/design/resources.md[resource model] applies to both volumes and claims.
   
   === Claims As Volumes
   
  
positive.code: 
  A volume will be in one of the following phases:
  
  * Available -- a free resource resource that is not yet bound to a claim
  * Bound -- the volume is bound to a claim
  * Released -- the claim has been deleted, but the resource is not yet reclaimed by the cluster
  * Failed -- the volume has failed its automatic reclamation
  
negative.code: 
  A `PersistentVolume` (PV) is a piece of networked storage in the cluster that has been provisioned by an administrator.  It is a resource in the cluster just like a node is a cluster resource.   PVs are volume plugins like Volumes, but have a lifecycle independent of any individual pod that uses the PV.  This API object captures the details of the implementation of the storage, be that NFS, iSCSI, or a cloud-provider-specific storage system.
  
  A `PersistentVolumeClaim` (PVC) is a request for storage by a user.  It is similar to a pod.  Pods consume node resources and PVCs consume PV resources.  Pods can request specific levels of resources (CPU and Memory).  Claims can request specific storage capacity and access modes (e.g, can be mounted once read/write or many times read-only).
  
  == Lifecycle of a volume and claim
  
  PVs are resources in the cluster.  PVCs are requests for those resources and also act as claim checks to the resource.  The interaction between PVs and PVCs follows this lifecycle:
  
  === Provisioning
  
  