proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-06-14 16:08:40 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

some small spelling/grammar fixes

Browse Source 
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
This commit is contained in:
Dominik Csapak 2017-01-24 12:10:42 +01:00 committed by Fabian Grünbichler
parent da4d13f81e
commit e60ce90c62
4 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ha-manager.adoc
View File

@ -523,7 +523,7 @@ include::ha-groups-opts.adoc[]
[thumbnail="gui-ha-manager-add-group.png"] [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 node. Usually the resource is able to run on other nodes, so you can define
an unrestricted group with a single member: an unrestricted group with a single member:
@ -568,7 +568,7 @@ group: mygroup2
The `nofailback` options is mostly useful to avoid unwanted resource 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 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 group, you need to tell the HA manager to not move this service
instantly back by setting the `nofailback` option. instantly back by setting the `nofailback` option.

2
pve-disk-health-monitoring.adoc
View File

@ -4,7 +4,7 @@ ifdef::wiki[]
:pve-toplevel: :pve-toplevel:
endif::wiki[] 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. 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] Starting with {pve} 4.3, the package smartmontools footnote:[smartmontools homepage https://www.smartmontools.org]

3
pve-network.adoc
View File

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

4
qm.adoc
View File

@ -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 VM, because it delivers useful information such as how much memory the guest
really uses. really uses.
In general, you should leave *ballooning* enabled, but if you want to disable 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 *Ballooning* or set
balloon: 0 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. 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. 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 a VM online to another host, since the hardware is only available
on the host the VM is currently residing. on the host the VM is currently residing.