Added spell check

[ekenigs]

Description

Added spell check

Checklist

• [ ] If this requires a documentation change, I have created a PR that updates the mkdocs/docs directory
• [ ] If this requires it, I have updated the Readme
• [ ] If necessary, I have updated the examples
• [ ] I have verified if I need to create/update unit tests
• [ ] I have verified if I need to create/update acceptance tests
• [ ] If necessary, I have run acceptance tests on this branch in CI

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 0ecc3f607711980d10a1409f85c77d7d7f11b496

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security[bot]]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher

🚮 Removed packages: npm/husky@9.1.4, npm/lint-staged@15.2.7

View full report↗︎

[socket-security[bot]]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/lefthook@1.7.11

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

[ekenigs]

@SocketSecurity ignore npm/lefthook@1.7.11