X-Git-Url: https://git.proxmox.com/?p=pve-docs.git;a=blobdiff_plain;f=ha-manager.adoc;h=cb9d26b0ed0d7436a7235909b0baf1fd23993e3a;hp=efa564607f2dcd934b838dec35bb5d97834b0095;hb=2489d6df4ac5e916ae18401310bfd1e69c993e55;hpb=7dd7a0b711a11185f94f24f905bc40595dc5a917

diff --git a/ha-manager.adoc b/ha-manager.adoc
index efa5646..cb9d26b 100644
--- a/ha-manager.adoc
+++ b/ha-manager.adoc
@@ -321,7 +321,7 @@ node, or when we restart the LRM daemon
 
 ignored::
 
-Act as the service is not managed by HA at all.
+Act as if the service were not managed by HA at all.
 Useful, when full control over the service is desired temporarily,
 without removing it from the HA configuration.
 
@@ -762,8 +762,8 @@ that they get touched by the Cluster during the short time the LRM is restarting
 After that the LRM may safely close the watchdog during a restart.
 Such a restart happens normally during a package update and, as already stated,
 an active master CRM is needed to acknowledge the requests from the LRM. If
-this is not the case the update process can take to long which, in the worst
-case, may result in a reset triggered by he watchdog.
+this is not the case the update process can take too long which, in the worst
+case, may result in a reset triggered by the watchdog.
 
 
 Node Maintenance