motiondivision / motiondivision/motion
Fix typos in code comments (19 fixes across 15 files)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 33.7k
- Forks
- 1.4k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 14
Description
Hi! While reading the source I spotted a number of misspellings in JSDoc and
inline comments across motion-utils, motion-dom, and framer-motion. They
surface in IDE tooltips and hurt readability of the explanatory comments, so
I'd like to contribute the fixes.
What
19 misspellings across 15 files — comment/JSDoc only, no logic, types, or
behavior change (19 insertions / 19 deletions, one-to-one word swaps). A few
examples:
motion-utils/src/pipe.ts—linearily→linearlymotion-dom/src/render/VisualElement.ts—inherting→inheriting(×2)framer-motion/.../use-visual-element.ts—situtation→situationmotion-dom/.../create-projection-node.ts—calculcated/relavent/recalcualte→calculated/relevant/recalculate
Full list is in the branch (below).
Where
Ready on a branch in my fork: AlexRixten:docs/fix-comment-typos
https://github.com/motiondivision/motion/compare/main...AlexRixten:docs/fix-comment-typos
How to proceed
I tried to open a PR directly, but the repo's PR creation policy is
collaborators-only, so I can't. I'm happy to either:
- open the PR if I'm added as a collaborator, or
- have a maintainer merge the branch from the fork directly.
Either works — just let me know. Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the existing AlexRixten:docs/fix-comment-typos branch and its comparison with main; the issue lists representative files and the intended spelling changes. Verify that all 19 edits across 15 files are limited to comments or JSDoc, with no logic, types, or behavior changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100