X-Git-Url: https://git.proxmox.com/?p=pve-docs.git;a=blobdiff_plain;f=ha-manager.adoc;h=db67e59fbe34d491494867ed9a6e71857daae894;hp=47fbe7c717281ed1a84ec50abeed3cba2fc442bd;hb=e60ce90c622dcc96f6f86229a9f0a3caa9a8f60f;hpb=da4d13f81ea9181f6da39fb81a000dc0d7c5869b

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.