DOC-573: edits from feedback

Author: amandalindsay

docs/modules/ROOT/pages/mount-pvc.adoc

@@ -4,17 +4,17 @@ You can mount one or more Persistent Volume Claims (PVCs) directly to your Hazel
 
 == How it works
 
-- Define one or more PVCs in the persistenceVolumeClaims section of your Hazelcast custom resource (CR).
+- Define one or more PVCs in the `persistenceVolumeClaims` section of your Hazelcast custom resource (CR).
 - Each PVC will be mounted at `/data/<name>`, where `<name>` is the value of the name field in your PVC configuration.
 - Features that require persistent storage (such as diagnostics, persistence, or the CP Subsystem) can reference the PVC by specifying its name, using the appropriate field (e.g., `pvcName`).
 
 This mechanism decouples the PVC definition from feature configuration, making it easier to manage and reuse storage across different Hazelcast features.
 
-For more information, see the xref:api-ref.adoc#[API].
+For more information, see the xref:api-ref.adoc#[API]. For a tutorial on enabling persistence, see link:https://docs.hazelcast.com/hazelcast/latest/getting-started/persistence[Persist Map Entries on Disk]
 
 == Example: Configure diagnostics with a named PVC
 
-Below is an example configuration that shows how to define a PVC and use it for diagnostics logging by specifying the pvcName field. The diagnostics logs will be stored in the PVC mounted at `/data/diagnostics-pvc-volume`.
+Below is an example configuration that shows how to define a PVC and use it for diagnostics logging by specifying the `pvcName` field. The diagnostics logs will be stored in the PVC mounted at `/data/diagnostics-pvc-volume`.
 
 [source,yaml]
 ----