some small spelling/grammar fixes

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>

diff --git a/ha-manager.adoc b/ha-manager.adoc
index 47fbe7c717281ed1a84ec50abeed3cba2fc442bd..db67e59fbe34d491494867ed9a6e71857daae894 100644 (file)
--- a/ha-manager.adoc
+++ b/ha-manager.adoc
@@ -523,7 +523,7 @@ include::ha-groups-opts.adoc[]
 
 [thumbnail="gui-ha-manager-add-group.png"]
 
-A commom requirement is that a resource should run on a specific
+A common requirement is that a resource should run on a specific
 node. Usually the resource is able to run on other nodes, so you can define
 an unrestricted group with a single member:
 
@@ -568,7 +568,7 @@ group: mygroup2
 
 
 The `nofailback` options is mostly useful to avoid unwanted resource
-movements during administartion tasks. For example, if you need to
+movements during administration tasks. For example, if you need to
 migrate a service to a node which hasn't the highest priority in the
 group, you need to tell the HA manager to not move this service
 instantly back by setting the `nofailback` option.

diff --git a/pve-disk-health-monitoring.adoc b/pve-disk-health-monitoring.adoc
index 99ba8aa54feb8a7c796387e9cc4a3ba1751ceb14..8ea9d5f2f1e7df9c9eaf36e3a5b25f042722e9f1 100644 (file)
--- a/pve-disk-health-monitoring.adoc
+++ b/pve-disk-health-monitoring.adoc
@@ -4,7 +4,7 @@ ifdef::wiki[]
 :pve-toplevel:
 endif::wiki[]
 
-Altough a robust and redundant storage is recommended,
+Although a robust and redundant storage is recommended,
 it can be very helpful to monitor the health of your local disks.
 
 Starting with {pve} 4.3, the package smartmontools footnote:[smartmontools homepage https://www.smartmontools.org]

diff --git a/pve-network.adoc b/pve-network.adoc
index fd523576323917958d07c5022a7ae2777b9aa7bf..45f64249b687c52c6d52a3145aab8b602f3159a1 100644 (file)
--- a/pve-network.adoc
+++ b/pve-network.adoc
@@ -208,8 +208,7 @@ designated slave network interface. If this receiving slave fails,
 another slave takes over the MAC address of the failed receiving
 slave.
 
-* *Adaptive load balancing (balanceIEEE 802.3ad Dynamic link
-aggregation (802.3ad)(LACP):-alb):* Includes balance-tlb plus receive
+* *Adaptive load balancing (balance-alb):* Includes balance-tlb plus receive
 load balancing (rlb) for IPV4 traffic, and does not require any
 special network switch support. The receive load balancing is achieved
 by ARP negotiation. The bonding driver intercepts the ARP Replies sent

diff --git a/qm.adoc b/qm.adoc
index 7444661da56b990589d0dec0c753b8b407077a3d..ed2ab8d5d4231b5689a785bb4f26f20dddc16ad7 100644 (file)
--- a/qm.adoc
+++ b/qm.adoc
@@ -285,7 +285,7 @@ Even when using a fixed memory size, the ballooning device gets added to the
 VM, because it delivers useful information such as how much memory the guest
 really uses.
 In general, you should leave *ballooning* enabled, but if you want to disable
-it (e.g. for debugging porpuses), simply uncheck
+it (e.g. for debugging purposes), simply uncheck
 *Ballooning* or set
 
  balloon: 0
@@ -421,7 +421,7 @@ If a device is present in a VM configuration when the VM starts up,
 but the device is not present in the host, the VM can boot without problems.
 As soon as the device/port ist available in the host, it gets passed through.
 
-WARNING: Using this kind of USB passthrough, means that you cannot move
+WARNING: Using this kind of USB passthrough means that you cannot move
 a VM online to another host, since the hardware is only available
 on the host the VM is currently residing.