Fix style issues related to Managing Security Compliance (Monitoring compliance)

[jberendz]

What changes are you introducing?

Remove deprecated {context} tags in section headings.

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

Addressing issues found in Issue #4214

Because this issue is broad and covers multiple sections throughout the entire Managing Security Compliance guide, PRs are broken into chapter reviews per Endeavor's guidance.

This PR relates to Section 7, Monitoring compliance

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

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.19/Katello 4.21
• Foreman 3.18/Katello 4.20 (Satellite 6.19; orcharhino 7.9)
• Foreman 3.17/Katello 4.19
• Foreman 3.16/Katello 4.18 (Satellite 6.18; orcharhino 7.6, 7.7, and 7.8)
• Foreman 3.15/Katello 4.17
• Foreman 3.14/Katello 4.16 (Satellite 6.17; orcharhino 7.4; orcharhino 7.5)
• We do not accept PRs for Foreman older than 3.14.

[github-actions]

The PR preview for 652d191 is available at theforeman-foreman-documentation-preview-pr-5147.surge.sh

The following output files are affected by this PR:

• Managing_Security_Compliance/index-foreman-el.html
• Managing_Security_Compliance/index-katello.html
• Managing_Security_Compliance/index-orcharhino.html

show diff

show diff as HTML

[maximiliankolb]

Just a general tip: if you change anchors, please go with all lowercase and dashes instead of underscores. For example:

-[id="Compliance_Email_Notifications_{context}"]
+[id="compliance-email-notifications"]

The vale check will help you with this too.

[jberendz]

Thanks @maximiliankolb . This is my first time working with Vale. Is there an extension you use to have it check your local build? I don't want to rely on finding out after I commit changes.

[maximiliankolb]

Thanks @maximiliankolb . This is my first time working with Vale. Is there an extension you use to have it check your local build? I don't want to rely on finding out after I commit changes.

To be honest, I don't use Vale locally. With experience, I have a feeling for our conventions. If I notice that Vale complains about my PR, then I usually convert it to a draft and fix issues until Vale is happy or I declare them false positives or out of scope.

But maybe @aneta-petrova can help you. It probably depends on your editor. I once had Vale running for markdown files in vim but wasn't happy with it.