Update 2026-03-31-sbt-security-advisory.md

Author: anatoliykmetyuk

blog/_posts/2026-03-31-sbt-security-advisory.md

@@ -52,7 +52,7 @@ Both measures follow established guidance from [OWASP](https://cheatsheetseries.
 
 The fix is available in sbt 1.12.8 and sbt 2.0.0-RC10. The full advisory is published as [GHSA-x4ff-q6h8-v7gw](https://github.com/sbt/sbt/security/advisories/GHSA-x4ff-q6h8-v7gw).
 
-## Workflow of Applying the Fix
+## Workflow of applying the fix
 
 One interesting detail to mention is that GitHub provides a [way](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability) to report a vulnerability, work on the fix and submit a PR privately to prevent the vulnerability from being publicly disclosed before the fix is ready. If you encounter a security vulnerability in a Scala project, you should do the same, reporting it to the maintainers via Security Advisory on GitHub.