Merge pull request #63854 from lpettyjo/OCPBUGS-17558_17559

OCPBUGS-17558 & 17559: Adding NFS support to Azure File CSI

Author: lpettyjo

modules/persistent-storage-csi-azure-file-nfs.adoc

@@ -7,7 +7,7 @@
 [id="persistent-storage-csi-azure-file-nfs_{context}"]
 = NFS support
 
-{product-title} 4.14, and later, supports Azure File Container Storage Interface (CSI) Driver Operator with  Network File System (NFS) with the following caveats:
+{product-title} supports the Azure File Container Storage Interface (CSI) Driver Operator with Network File System (NFS) with the following restrictions:
 
 * Creating pods with Azure File NFS volumes that are scheduled to the control plane node causes the mount to be denied.
 +
@@ -17,8 +17,9 @@ To work around this issue: If your control plane nodes are schedulable, and the
 +
 [IMPORTANT]
 =====
-Azure File CSI with NFS does not honor the fsGroupChangePolicy requested by pods. Azure File CSI with NFS applies a default OnRootMismatch FS Group policy regardless of the policy requested by the pod.
+Azure File CSI with NFS does not honor the `fsGroupChangePolicy` requested by pods. Azure File CSI with NFS applies a default `OnRootMismatch` FS Group policy regardless of the policy requested by the pod.
 =====
+
 * The Azure File CSI Operator does not automatically create a storage class for NFS. You must create it manually. Use a file similar to the following:
 +
 [source, yaml]

storage/container_storage_interface/persistent-storage-csi-azure-file.adoc

@@ -17,7 +17,7 @@ To create CSI-provisioned PVs that mount to Azure File storage assets, {product-
 
 * The _Azure File CSI driver_ enables you to create and mount Azure File PVs. The Azure File CSI driver supports dynamic volume provisioning by allowing storage volumes to be created on-demand, eliminating the need for cluster administrators to pre-provision storage.
 
-Azure File CSI Driver Operator does not support:
+Azure File CSI Driver Operator does _not_ support:
 
 * Virtual hard disks (VHD)