fix: typo spelling grammar

[slowy07]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• [x] The toolchain has been rebuilt successfully (or no changes were made to it)
• [x] The toolchain/worker package manifests are up-to-date
• [x] Any updated packages successfully build (or no packages were changed)
• [x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• [x] All package sources are available
• [x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/tools/cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• [x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
• [x] All source files have up-to-date hashes in the *.signatures.json files
• [x] sudo make go-tidy-all and sudo make go-test-coverage pass
• [x] Documentation has been updated to match any changes to the build system
• [x] Ready to merge

---

description

fix typo spelling grammar and replace to correct words with reference from merriam webster

Does this affect the toolchain?

NO

Test Methodology

testing not include because just replace the typo

[slowy07]

ok sir, thanks @PawelWMS i will do it, but when i pull on 1.0 dev i get many changes from few contributors on my pull request, how i fix that?, or i just pull my changes ?

[PawelWMS]

ok sir, thanks @PawelWMS Pawel Winogrodzki FTE i will do it, but when i pull on 1.0 dev i get many changes from few contributors on my pull request, how i fix that?, or i just pull my changes ?

First grab the latest 1.0-dev. Since you have very few commits here, I think the easiest way would be to cherry-pick them onto a new branch created off of that clean 1.0-dev. You can also try rebasing and selecting only your commits.

[jslobodzian]

Thank you for your suggestions. The documentation changes will be accepted in an upcoming PR. The remaining code changes need to be rebased to main

[slowy07]

okay thanks sir @jslobodzian 💯