Fix typos and improve clarity in README and SECURITY documentation - …

[danuw]

…linked to PR #622

Pull Request

Issue Number: #622

Summary

Addresses syntax errors spotted in #622 and others

Changes

• addresses syntax errors spotted in Fixing a few typo's ✏️ #622 and others
• addresses DCO missing on Fixing a few typo's ✏️ #622 and typos that would break building the docs

Checklist

• Local Tests Passing?
• CICD and Pipeline Tests Passing?
• Added any new Tests?
• Documentation Updates Made?
• Are there any API Changes? If yes, please describe below.
• This is not a breaking change. If it is, please describe it below.

Are there API Changes?

If yes, what are the expected API Changes? Please link to an API-Comparison
workflow with the API Diff.

Is this a breaking change?

If yes, what workflow does this break?

Anything else?

Other comments, collaborators, etc.

Please follow
GitHub's suggested syntax
to link Pull Requests to Issues via keywords

This PR Closes #622

[Copilot]

Pull Request Overview

Addresses spelling and grammatical errors in both the SECURITY documentation and the project README to improve clarity and prevent build issues.

• Fixed multiple typos and improved phrasing in SECURITY.md
• Corrected grammatical constructions and updated screenshot alt text in README.md

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
SECURITY.md	Corrected typos for consistency (e.g., “maintaned” → “maintained”), standardized phrasing, and fixed header formatting
README.md	Improved sentence structure in the intro, fixed verb agreement, and updated screenshot alt text