tree-wide: properly use {pve} instead of PVE

[pve-docs.git] / pmxcfs.adoc

diff --git a/pmxcfs.adoc b/pmxcfs.adoc
index 7cf70f9d11bd5db083e1056a0230de2cba1112dd..ca4e32701644fee7c99116c8582bb9a75e6a9efd 100644 (file)
--- a/pmxcfs.adoc
+++ b/pmxcfs.adoc
@@ -26,7 +26,7 @@ endif::manvolnum[]
 
 The Proxmox Cluster file system (``pmxcfs'') is a database-driven file
 system for storing configuration files, replicated in real time to all
-cluster nodes using `corosync`. We use this to store all PVE related
+cluster nodes using `corosync`. We use this to store all {PVE} related
 configuration files.
 
 Although the file system stores all data inside a persistent database on disk,
@@ -106,7 +106,7 @@ Files
 |`ha/resources.cfg`                     | Resources managed by high availability, and their current state
 |`nodes/<NAME>/config`                  | Node-specific configuration
 |`nodes/<NAME>/lxc/<VMID>.conf`         | VM configuration data for LXC containers
-|`nodes/<NAME>/openvz/`                 | Prior to PVE 4.0, used for container configuration data (deprecated, removed soon)
+|`nodes/<NAME>/openvz/`                 | Prior to {pve} 4.0, used for container configuration data (deprecated, removed soon)
 |`nodes/<NAME>/pve-ssl.key`             | Private SSL key for `pve-ssl.pem`
 |`nodes/<NAME>/pve-ssl.pem`             | Public SSL certificate for web server (signed by cluster CA)
 |`nodes/<NAME>/pveproxy-ssl.key`        | Private SSL key for `pveproxy-ssl.pem` (optional)