anchor.diff:  
   . Define the required options on the resulting page.
   
  -.. Select the appropriate StorageClass.
  +.. Select the appropriate storage class.
   
   .. Enter a unique name for the storage claim.
   
  
positive.code: [id="persistent-storage-csi-manila-dynamic-provisioning_{context}"]
  = Dynamically provisioning Manila CSI volumes
  
  {product-title} installs a StorageClass for each available Manila share type.
  
  The YAML files that are created are completely decoupled from Manila and from its Container Storage Interface (CSI) plug-in. As an application developer, you can dynamically provision ReadWriteMany (RWX) storage and deploy Pods with applications that safely consume the storage using YAML manifests. You can also provision other access modes, such as ReadWriteOnce (RWO).
  
  You can use the same Pod and persistent volume claim (PVC) definitions on-premise that you use with {product-title} on AWS, GCP, Azure, and other platforms, with the exception of the storage class reference in the PVC definition.
  
  .Prerequisites
  
  * {rh-openstack-first} is deployed with appropriate Manila share infrastructure so that it can be used to dynamically provision and mount volumes in {product-title}.
  
  .Procedure (UI)
  
  
negative.code: +
  [IMPORTANT]
  ====
  Use RWX if you want the persistent volume (PV) that fulfills this PVC to be mounted to multiple pods on multiple nodes in the cluster.
  ====
  
  . Define the size of the storage claim.
  