update generated docs

[pve-docs.git] / ha-manager.adoc

diff --git a/ha-manager.adoc b/ha-manager.adoc
index 07a2370b4e87488aa91060bcf1e6fa5aef524386..cb9d26b0ed0d7436a7235909b0baf1fd23993e3a 100644 (file)
--- 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.
 
@@ -760,10 +760,10 @@ actions between the cluster and the local resource manager. For restarting,
 the LRM makes a request to the CRM to freeze all its services. This prevents
 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 on a update and as already stated a active master
-CRM is needed to acknowledge the requests from the LRM, if this is not the case
-the update process can be too long which, in the worst case, may result in
-a watchdog reset.
+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 too long which, in the worst
+case, may result in a reset triggered by the watchdog.
 
 
 Node Maintenance