[pve-devel] [PATCH docs 1/4] some small spelling/grammar fixes

Dominik Csapak d.csapak at proxmox.com
Tue Jan 24 12:10:42 CET 2017


Signed-off-by: Dominik Csapak <d.csapak at proxmox.com>
---
the networking part is not really a spelling mistake but a copy/paste error
 ha-manager.adoc                 | 4 ++--
 pve-disk-health-monitoring.adoc | 2 +-
 pve-network.adoc                | 3 +--
 qm.adoc                         | 4 ++--
 4 files changed, 6 insertions(+), 7 deletions(-)

diff --git a/ha-manager.adoc b/ha-manager.adoc
index 47fbe7c..db67e59 100644
--- 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 99ba8aa..8ea9d5f 100644
--- 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 fd52357..45f6424 100644
--- 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 7444661..ed2ab8d 100644
--- 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.
 
-- 
2.1.4




More information about the pve-devel mailing list