Change "OS" to "operating system" per RHSSG

[rh-max]

What changes are you introducing?

Cherrypicking #3387 into 3.12.

If successful, please also cherrypick down to 3.5, thank you.

[github-actions]

The PR preview for 594198e is available at theforeman-foreman-documentation-preview-pr-3440.surge.sh

The following output files are affected by this PR:

• Administering_Project/index-katello.html
• Administering_Project/index-orcharhino.html
• Administering_Project/index-satellite.html
• Managing_Configurations_Ansible/index-foreman-deb.html
• Managing_Configurations_Ansible/index-foreman-el.html
• Managing_Configurations_Ansible/index-katello.html
• Managing_Configurations_Ansible/index-orcharhino.html
• Managing_Configurations_Ansible/index-satellite.html
• Managing_Content/index-katello.html
• Managing_Content/index-orcharhino.html
• Managing_Content/index-satellite.html
• Managing_Hosts/index-katello.html
• Managing_Hosts/index-orcharhino.html
• Managing_Hosts/index-satellite.html
• Planning_for_Project/index-katello.html
• Planning_for_Project/index-orcharhino.html
• Provisioning_Hosts/index-katello.html
• Provisioning_Hosts/index-orcharhino.html
• Provisioning_Hosts/index-satellite.html
• Quickstart/index-foreman-deb.html
• Quickstart/index-foreman-el.html
• Quickstart/index-katello.html
• Quickstart/index-orcharhino.html
• Quickstart/index-satellite.html
• Tuning_Performance/index-katello.html
• Tuning_Performance/index-orcharhino.html
• Tuning_Performance/index-satellite.html
• Upgrading_Project/index-foreman-el.html
• Upgrading_Project/index-katello.html
• Upgrading_Project/index-orcharhino.html

show diff

show diff as HTML

[maximiliankolb]

LGTM.

[apinnick]

Try rebasing to see whether that fixes the failed Vale check.

[Lennonka]

@apinnick The Vale error seems unrelated to changes in this PR. I've tried rerunning the Vale check, but it ends up with the same error. Care to investigate? Could there be a problem on the stable branch? Either way, I haven't seen it before.

[Lennonka]

@rh-max Unfortunately, there are conflicts again on 3.11. Since it's just a style fix, it is not necessary to propagate it to older releases if everyone agrees.

[apinnick]

@apinnick The Vale error seems unrelated to changes in this PR. I've tried rerunning the Vale check, but it ends up with the same error. Care to investigate? Could there be a problem on the stable branch? Either way, I haven't seen it before.

@Lennonka See my comment. We fixed the error in the main repo. PRs need to be rebased to pick up the fix.