update generated docs

[pve-docs.git] / pvecm.adoc

diff --git a/pvecm.adoc b/pvecm.adoc
index 179406e27c70bac290907008d383362bd23d15d3..36d18c2e55c7ff78eeef9793d1b7252d8bc641de 100644 (file)
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -444,7 +444,7 @@ Separate On Cluster Creation
 This is possible through the 'ring0_addr' and 'bindnet0_addr' parameter of
 the 'pvecm create' command used for creating a new cluster.
 
-If you have setup a additional NIC with a static address on 10.10.10.1/25
+If you have setup an additional NIC with a static address on 10.10.10.1/25
 and want to send and receive all cluster communication over this interface
 you would execute:
 
@@ -528,7 +528,7 @@ addresses.  You may use plain IP addresses or also hostnames here. If you use
 hostnames ensure that they are resolvable from all nodes.
 
 In my example I want to switch my cluster communication to the 10.10.10.1/25
-network. So I replace all 'ring0_addr' respectively. I also set the bindetaddr
+network. So I replace all 'ring0_addr' respectively. I also set the bindnetaddr
 in the totem section of the config to an address of the new network. It can be
 any address from the subnet configured on the new network interface.
 
@@ -708,7 +708,7 @@ stopped on all nodes start it one after the other again.
 Corosync Configuration
 ----------------------
 
-The `/ect/pve/corosync.conf` file plays a central role in {pve} cluster. It
+The `/etc/pve/corosync.conf` file plays a central role in {pve} cluster. It
 controls the cluster member ship and its network.
 For reading more about it check the corosync.conf man page:
 [source,bash]
@@ -876,10 +876,10 @@ xref:pct_migration[Container Migration Chapter]
 Migration Type
 ~~~~~~~~~~~~~~
 
-The migration type defines if the migration data should be sent over a
+The migration type defines if the migration data should be sent over an
 encrypted (`secure`) channel or an unencrypted (`insecure`) one.
 Setting the migration type to insecure means that the RAM content of a
-virtual guest gets also transfered unencrypted, which can lead to
+virtual guest gets also transferred unencrypted, which can lead to
 information disclosure of critical data from inside the guest (for
 example passwords or encryption keys).