Add 'Severity changes' heading to security findings page

[mark-rln]

Gives the paragraph about CVE severity discrepancies and Trivy database updates its own ### Severity changes subheading (under the Findings section), so it can be linked to directly and is easier to scan.

No content changes — only the heading was added.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[gemini-code-assist]

Code Review

This pull request adds a new 'Severity changes' heading to the security and risk management documentation. The review feedback suggests adding an explicit anchor ID to this heading to ensure stable direct linking, aligning with the document's existing patterns.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[github-actions]

Overall readability score: 54.23 (🟢 +0)

File	Readability
managing-security-and-risk.md	58.03 (🟢 +0)

View detailed metrics

🟢 - Shows an increase in readability
🔴 - Shows a decrease in readability

File	Readability	FRE	GF	ARI	CLI	DCRS
managing-security-and-risk.md	58.03	36.59	9.91	12.9	12.82	6.5
	🟢 +0	🟢 +0	🟢 +0	🟢 +0	🟢 +0	🟢 +0

Averages:

	Readability	FRE	GF	ARI	CLI	DCRS
Average	54.23	43.16	10.9	12.3	12.24	8.01
	🟢 +0	🟢 +0	🟢 +0	🟢 +0	🟢 +0	🟢 +0

View metric targets

Metric	Range	Ideal score
Flesch Reading Ease	100 (very easy read) to 0 (extremely difficult read)	60
Gunning Fog	6 (very easy read) to 17 (extremely difficult read)	8 or less
Auto. Read. Index	6 (very easy read) to 14 (extremely difficult read)	8 or less
Coleman Liau Index	6 (very easy read) to 17 (extremely difficult read)	8 or less
Dale-Chall Readability	4.9 (very easy read) to 9.9 (extremely difficult read)	6.9 or less

[codacy-production]

Pull Request Overview

This pull request adds a '### Severity changes' subheading to the security findings documentation. This change enhances readability and allows users to link directly to the section explaining CVE severity classification sources.

The implementation aligns with the intended requirements and does not introduce any quality regressions or documentation structure issues. Codacy analysis indicates the changes are up to standards.

Test suggestions

• Verify the '### Severity changes' header is correctly rendered as an H3 level heading.
• Verify the content of the paragraph regarding Trivy and CVE sources remains intact and correctly associated with the new header.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify the '### Severity changes' header is correctly rendered as an H3 level heading.
2. Verify the content of the paragraph regarding Trivy and CVE sources remains intact and correctly associated with the new header.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}