use pve macro more often

diff --git a/pct.adoc b/pct.adoc
index 71f05cba0243466a30f30940d24b127ff668a0fa..6a81b14c5ac30a0491474375f8e224990f4c61d0 100644 (file)
--- a/pct.adoc
+++ b/pct.adoc
@@ -273,7 +273,7 @@ new container, for example:
 
  pct create 999 local:vztmpl/debian-8.0-standard_8.0-1_amd64.tar.gz
 
-Proxmox itself ships a set of basic templates for most common
+{pve} itself ships a set of basic templates for most common
 operating systems, and you can download them using the `pveam` (short
 for {pve} Appliance Manager) command line utility. You can also
 download https://www.turnkeylinux.org/[TurnKey Linux] containers using

diff --git a/pve-admin-guide.adoc b/pve-admin-guide.adoc
index c26a6efcc26b3ebb7d0c4380395347703c32bd9b..fdd8e62337410667c3f8564f4f8d7aba74cc7b06 100644 (file)
--- a/pve-admin-guide.adoc
+++ b/pve-admin-guide.adoc
@@ -152,8 +152,8 @@ include::vzdump.1-synopsis.adoc[]
 
 :leveloffset: 0
 
-*ha-manager* - Proxmox VE HA Manager
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+*ha-manager* - {pve} HA Manager
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 :leveloffset: 1
 include::ha-manager.1-synopsis.adoc[]

diff --git a/pve-firewall.adoc b/pve-firewall.adoc
index fc74a92e5c110cd36b0027ae430f7810d0e9cbc3..ec0db307fd9b7ed7bb8434cdc2cccdbe7ee64277 100644 (file)
--- a/pve-firewall.adoc
+++ b/pve-firewall.adoc
@@ -25,7 +25,7 @@ ifndef::manvolnum[]
 include::attributes.txt[]
 endif::manvolnum[]
 
-Proxmox VE Firewall provides an easy way to protect your IT
+{pve} Firewall provides an easy way to protect your IT
 infrastructure. You can setup firewall rules for all hosts
 inside a cluster, or define rules for virtual machines and
 containers. Features like firewall macros, security groups, IP sets
@@ -547,8 +547,8 @@ corresponding link local addresses.  (See the
 <<ipfilter-section,Standard IP set `ipfilter-net*`>> section for details.)
 
 
-Ports used by Proxmox VE
-------------------------
+Ports used by {pve}
+-------------------
 
 * Web interface: 8006
 * VNC Web console: 5900-5999

diff --git a/pveam.adoc b/pveam.adoc
index e5037843dd72ac4799a7009505c37c2f4989e325..ccf0dfb16845ac3576f890025a30d14cfc1a2bf5 100644 (file)
--- a/pveam.adoc
+++ b/pveam.adoc
@@ -6,7 +6,7 @@ include::attributes.txt[]
 NAME
 ----
 
-pveam - Proxmox VE Appliance Manager
+pveam - {pve} Appliance Manager
 
 
 SYNOPSYS

diff --git a/pveceph.adoc b/pveceph.adoc
index ab29e8ae41e035a0df3cd4cf3137d67bba5f6303..b38495756f99e2da781ad5f3bea4a78e1b55d34c 100644 (file)
--- a/pveceph.adoc
+++ b/pveceph.adoc
@@ -6,7 +6,7 @@ include::attributes.txt[]
 NAME
 ----
 
-pveceph - Manage CEPH Services on Proxmox VE Nodes
+pveceph - Manage CEPH Services on {pve} Nodes
 
 SYNOPSYS
 --------

diff --git a/pvecm.adoc b/pvecm.adoc
index 84a52c58ad6fbef5652e09370a042f61c4f4d0b1..34e5520884c48353bdf1fa543871b5ebcffa9376 100644 (file)
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -6,7 +6,7 @@ include::attributes.txt[]
 NAME
 ----
 
-pvecm - Proxmox VE Cluster Manager
+pvecm - {pve} Cluster Manager
 
 SYNOPSYS
 --------
@@ -275,7 +275,7 @@ it could be difficult to restore a clean cluster state.
 If, for whatever reason, you want that this server joins the same
 cluster again, you have to
 
-* reinstall pve on it from scratch
+* reinstall {pve} on it from scratch
 
 * then join it, as explained in the previous section.
 

diff --git a/pvesubscription.adoc b/pvesubscription.adoc
index 15dae8d4a043ac76db71c5b9dfb632bcd2986163..bc6876e728bfee8113abf1096f77e56ae21658f0 100644 (file)
--- a/pvesubscription.adoc
+++ b/pvesubscription.adoc
@@ -23,7 +23,7 @@ Subscription Management
 include::attributes.txt[]
 endif::manvolnum[]
 
-This tool is used to handle pve subscriptions.
+This tool is used to handle {pve} subscriptions.
 
 ifdef::manvolnum[]
 include::pve-copyright.adoc[]