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

where applicable, or expand/replace where it's not a good fit or automatic
expansion doesn't work.

there are a few more in generated files, those need to be cleaned up
separately.

Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>

getting-help.adoc

@@ -27,13 +27,13 @@ Mailing Lists
 This is a fast way to communicate with the {pve} community via email.
 
 * Mailing list for users:
-  http://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user[PVE User List]
+  http://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user[{PVE} User List]
 
 {pve} is fully open source and contributions are welcome! The primary
 communication channel for developers is the:
 
 * Mailing list for developers:
-  http://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel[PVE development
+  http://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel[{PVE} development
   discussion]
 
 

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)

pve-firewall.adoc

@@ -324,7 +324,7 @@ Standard IP set `management`
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 This IP set applies only to host firewalls (not VM firewalls).  Those
-IPs are allowed to do normal management tasks (PVE GUI, VNC, SPICE,
+IPs are allowed to do normal management tasks ({PVE} GUI, VNC, SPICE,
 SSH).
 
 The local cluster network is automatically added to this IP set (alias

pve-package-repos.adoc

@@ -93,7 +93,7 @@ We recommend to configure this repository in `/etc/apt/sources.list`.
 deb http://ftp.debian.org/debian bullseye main contrib
 deb http://ftp.debian.org/debian bullseye-updates main contrib
 
-# PVE pve-no-subscription repository provided by proxmox.com,
+# Proxmox VE pve-no-subscription repository provided by proxmox.com,
 # NOT recommended for production use
 deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription
 

pvesm.adoc

@@ -67,7 +67,7 @@ data to different nodes.
 .Available storage types
 [width="100%",cols="<2d,1*m,4*d",options="header"]
 |===========================================================
-|Description    |PVE type    |Level |Shared|Snapshots|Stable
+|Description    |Plugin type |Level |Shared|Snapshots|Stable
 |ZFS (local)    |zfspool     |file  |no    |yes      |yes
 |Directory      |dir         |file  |no    |no^1^    |yes
 |BTRFS          |btrfs       |file  |no    |yes      |technology preview

pvesr.adoc

@@ -71,10 +71,10 @@ Supported Storage Types
 
 .Storage Types
 [width="100%",options="header"]
-|============================================
-|Description    |PVE type    |Snapshots|Stable
+|=============================================
+|Description    |Plugin type |Snapshots|Stable
 |ZFS (local)    |zfspool     |yes      |yes
-|============================================
+|=============================================
 
 [[pvesr_schedule_time_format]]
 Schedule Format