Comment 8 for bug 1768308

I put a lot of thought into my suggested wording in bug 1784675 which was marked as a duplicate of this bug (which I find dubious btw). I don't want to lose that. Here it is:

--------------------------

The pertinent help in `bootstrap` for constraints is:

===

--bootstrap-constraints (= "")
    Specify bootstrap machine constraints

--constraints (= "")
    Set model constraints

If '--bootstrap-constraints' is used, its values will also apply to any
future controllers provisioned for high availability (HA).

If '--constraints' is used, its values will be set as the default
constraints for all future workload machines in the model, exactly as if
the constraints were set with `juju set-model-constraints`.

===

I'd like to suggest the following wording:

===

--bootstrap-constraints (= "")
    Set constraints for controller machines

--constraints (= "")
    Set constraints for the 'controller' and 'default' models

If '--bootstrap-constraints' is used, its values will be used as constraints
for controllers only, including any future ones provisioned for high
availability.

If '--constraints' is used, its values will be used as constraints for every
machine in the 'controller' and 'default' models. This includes controllers
as well as non-controllers.

===