fix #5429: network: override device names: include Type=ether

[pve-docs.git] / pvesr.adoc

diff --git a/pvesr.adoc b/pvesr.adoc
index e508eee813c62d6f4f28e5fc69e37b9363283dfe..9eda00838f755ab20c99f3ceb93cbe9c3c5fdcf5 100644 (file)
--- a/pvesr.adoc
+++ b/pvesr.adoc
@@ -24,7 +24,7 @@ Storage Replication
 :pve-toplevel:
 endif::manvolnum[]
 
-The `pvesr` command line tool manages the {PVE} storage replication
+The `pvesr` command-line tool manages the {PVE} storage replication
 framework. Storage replication brings redundancy for guests using
 local storage and reduces migration time.
 
@@ -46,7 +46,6 @@ but not twice to the same target node.
 Each replications bandwidth can be limited, to avoid overloading a storage
 or server.
 
-Guests with replication enabled can currently only be migrated offline.
 Only changes since the last replication (so-called `deltas`) need to be
 transferred if the guest is migrated to a node to which it already is
 replicated. This reduces the time needed significantly. The replication
@@ -72,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
@@ -122,7 +121,7 @@ and replicate to node B.
 Node A failed and can not get back online. Now you have to migrate the guest
 to Node B manually.
 
-- connect to node B over ssh or open its shell via the WebUI
+- connect to node B over ssh or open its shell via the web UI
 
 - check if that the cluster is quorate
 +
@@ -165,7 +164,7 @@ Managing Jobs
 [thumbnail="screenshot/gui-qemu-add-replication-job.png"]
 
 You can use the web GUI to create, modify, and remove replication jobs
-easily. Additionally, the command line interface (CLI) tool `pvesr` can be
+easily. Additionally, the command-line interface (CLI) tool `pvesr` can be
 used to do this.
 
 You can find the replication panel on all levels (datacenter, node, virtual
@@ -183,7 +182,7 @@ composed of the VMID in addition to a job number.
 This ID must only be specified manually if the CLI tool is used.
 
 
-Command Line Interface Examples
+Command-line Interface Examples
 -------------------------------
 
 Create a replication job which runs every 5 minutes with a limited bandwidth