Re: [PATCH docs v2 09/12] ha-manager: rules: use the correct article for terms starting with HA

[David Riley <d.riley@proxmox.com>]

On 6/2/26 12:02 PM, Daniel Kral wrote:
> The correct article four any term starting with "HA" is always 'an',
> since the H is silent and therefore becomes a vowel sound.


But is it really silent? Is it not because
"Its name in English is aitch (pronounced /eɪtʃ/, plural aitches)" [0]

And therefore it should be "an HA ..."? But no hard feelings just wondering.

Otherwise it looks good to me.
Consider this:
Reviewed-by: David Riley <d.riley@proxmox.com>

[0] https://en.wikipedia.org/wiki/H

> Signed-off-by: Daniel Kral<d.kral@proxmox.com>
> ---
> changes since v1:
> - new
>
>   ha-manager.adoc | 20 ++++++++++----------
>   1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/ha-manager.adoc b/ha-manager.adoc
> index 7365ed0..d34916e 100644
> --- a/ha-manager.adoc
> +++ b/ha-manager.adoc
> @@ -719,9 +719,9 @@ on the same node.
>   Node Affinity Rules
>   ^^^^^^^^^^^^^^^^^^^
>   
> -By default, a HA resource is able to run on any cluster node, but a common
> -requirement is that a HA resource should run on a specific node. That can be
> -implemented by defining a HA node affinity rule to make the HA resource
> +By default, an HA resource is able to run on any cluster node, but a common
> +requirement is that an HA resource should run on a specific node. That can be
> +implemented by defining an HA node affinity rule to make the HA resource
>   `vm:100` prefer the node `node1`:
>   
>   ----
> @@ -730,8 +730,8 @@ implemented by defining a HA node affinity rule to make the HA resource
>   
>   By default, node affinity rules are not strict, i.e., if there is none of the
>   specified nodes available, the HA resource can also be moved to other nodes.
> -If, on the other hand, a HA resource must be restricted to the specified nodes,
> -then the node affinity rule must be set to be strict.
> +If, on the other hand, an HA resource must be restricted to the specified
> +nodes, then the node affinity rule must be set to be strict.
>   
>   In the previous example, the node affinity rule can be modified to restrict the
>   resource `vm:100` to be only on `node1`:
> @@ -823,8 +823,8 @@ separate nodes:
>   
>   Other than node affinity rules, resource affinity rules are strict by default,
>   i.e., if the constraints imposed by the resource affinity rules cannot be met
> -for a HA resource, the HA Manager will put the HA resource in recovery state in
> -case of a failover or in error state elsewhere.
> +for an HA resource, the HA Manager will put the HA resource in recovery state
> +in case of a failover or in error state elsewhere.
>   
>   The above commands created the following rules in the rules configuration file:
>   
> @@ -905,9 +905,9 @@ Currently, HA rules are checked for the following feasibility tests:
>     resources as a negative HA resources affinity rule. That is, two or more HA
>     resources cannot be kept together and separate at the same time.
>   
> -* An HA resource can only be part of a HA node affinity rule and a HA resource
> -  affinity rule at the same time, if the HA node affinity rule has a single
> -  priority class.
> +* An HA resource can only be part of an HA node affinity rule and an HA
> +  resource affinity rule at the same time, if the HA node affinity rule has a
> +  single priority class.
>   
>   * The HA resources of a positive HA resource affinity rule can only be part of
>     a single HA node affinity rule at most.