Try spell linter

[hannahramadan]

Before contributing, please read our contributing guidelines and code of conduct.

Overview

Describe the changes present in the pull request

Submitter Checklist:

• Include a link to the related GitHub issue, if applicable
• Include a security review link, if applicable

Testing

The agent includes a suite of unit and functional tests which should be used to
verify your changes don't break existing functionality. These tests will run with
GitHub Actions when a pull request is made. More details on running the tests locally can be found
here for our unit tests,
and here for our functional tests.
For most contributions it is strongly recommended to add additional tests which
exercise your changes.

Reviewer Checklist

• Perform code review
• Add performance label
• Perform appropriate level of performance testing
• Confirm all checks passed
• Add version label prior to acceptance

The best way to fix this issue is to explicitly specify the permissions required by the workflow or job. In this case, the job is only checking out code and running a spelling check on markdown files, so only minimal permissions are needed—specifically, read access to repository contents. No write access is required. The permissions block can be placed either at the top/root of the workflow (to apply to all jobs) or at the job level. Since there is a single job in this workflow, either placement is fine; placing it at the root is conventional and applies strict defaults if other jobs are ever added.
To fix:

• Add a permissions: block immediately after the workflow name:, with at minimum contents: read.

---