Update HA doc with corections and minor fixes
Update HA doc with corrections and fixes to typos and mistakes.
@@ -72,13 +72,13 @@ Kuryr Controller Implementation
The main issue with having multiple controllers is task division. All of the
controllers are watching the same endpoints and getting the same notifications,
but those notifications cannot be processed by multiple controllers at once,
-because we end up with a huge race conditon, where each controller creates
-Neutron resources but only on succeeds to put the annotation on the Kubernetes
+because we end up with a huge race condition, where each controller creates
+Neutron resources but only one succeeds to put the annotation on the Kubernetes
resource it is processing.
This is obviously unacceptable so as a first step we're implementing A/P HA,
-where only the leader is working on the resources and the rest waits in
-standby. This will be implemented by periodically calling the leader-elector
+where only the leader is working on the resources and the other instances wait
+as standby. This will be implemented by periodically calling the leader-elector
API to check the current leader. On leader change:
* Pod losing the leadership will stop its Watcher. Please note that it will be
