Refer to foremanctl as 'deployment tool' rather than 'installer'

[aneta-petrova]

What changes are you introducing?

Changing references to foremanctl from "installer" to "deployment tool/utility".

Why are you introducing these changes? (Explanation, links to references, issues, etc.)

In foremanctl, the existing foreman-installer and foreman-maintain tools will merge into one "deployment tool". Changing the wording we use to refer to the tool seems appropriate.

Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)

N/A

Contributor checklists

• I am okay with my commits getting squashed when you merge this PR.
• I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

• Foreman 3.16/Katello 4.18 (Satellite 6.18)
• Foreman 3.15/Katello 4.17
• Foreman 3.14/Katello 4.16 (Satellite 6.17; orcharhino 7.4)
• Foreman 3.13/Katello 4.15 (EL9 only)
• Foreman 3.12/Katello 4.14 (Satellite 6.16; orcharhino 7.2 on EL9 only; orcharhino 7.3)
• Foreman 3.11/Katello 4.13 (orcharhino 6.11 on EL8 only; orcharhino 7.0 on EL8+EL9; orcharhino 7.1 with Leapp)
• Foreman 3.10/Katello 4.12
• Foreman 3.9/Katello 4.11 (Satellite 6.15; orcharhino 6.8/6.9/6.10)
• We do not accept PRs for Foreman older than 3.9.

[github-actions]

The PR preview for 4450d9e is available at theforeman-foreman-documentation-preview-pr-4436.surge.sh

The following output files are affected by this PR:

• Quickstart/index-foreman-deb.html
• Quickstart/index-foreman-el.html
• Quickstart/index-katello.html
• Quickstart/index-orcharhino.html
• Quickstart/index-satellite.html

show diff

show diff as HTML

[ekohl]

Thanks for picking up on this.

[ekohl]

@evgeni and or @ehelms can probably tell you that I'm wrong in my suggestion ;)

[evgeni]

In the other file you call it "utility", not "tool", while both refer to the same thing, I guess it's easier if the same word is used?

ACK either way.

[ekohl]

We should add a description in the About section of https://github.com/theforeman/foremanctl that we can reuse here. For now it can only deploy, but we've also been talking about merging foreman-maintain functionality into it so we may need to revisit this if/when we do.

[aneta-petrova]

I took a look at the About section but I don't think I can help with that because I don't have permissions in that repo. So for now, I'm going to go ahead with merging this PR and if the description there turns out to be significantly different from what we have in the Quickstart guide, we can sync them later.

[Lennonka]

Please, can we pick one of those words (tool/utility) and use it consistently?

[Lennonka]

Thank you!

[aneta-petrova]

Merged to "master" and cherry-picked:

516f95d..5be804a 3.16 -> 3.16