# Question about contributing small cleanups (typos, TODOs, docs) in OpenCV **URL:** \ **Category:** Uncategorized\ **Created:** [January 5, 2026, 2:18pm UTC](https://forum.opencv.org/t/question-about-contributing-small-cleanups-typos-todos-docs-in-opencv/24298 "2026-01-05T14:18:26Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![AdityaMishra3000](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.opencv.org/adityamishra3000/32/14036_2.png) [@AdityaMishra3000](https://forum.opencv.org/u/AdityaMishra3000)\ **Post date:** [January 5, 2026, 2:18pm UTC](https://forum.opencv.org/t/question-about-contributing-small-cleanups-typos-todos-docs-in-opencv/24298/1 "2026-01-05T14:18:26Z")
Hi everyone, I’m getting set up to contribute to OpenCV and started by scanning the repository for low-risk issues to understand the contribution workflow. While grepping through the tree, I noticed a few things like: - Minor spelling issues in comments and docs (`recieve`, `recieved`, `occurence`, `paramters`, etc.) - Some stale `http://` links in documentation - A number of existing `TODO` comments in core/modules code Examples include: - Comments in `3rdparty` code (OpenEXR, libpng, jasper, etc.) - Documentation files under `doc/` with old or duplicated links - TODOs scattered in `modules/ts`, `modules/core`, and Java bindings Before opening any PRs, I wanted to ask: 1. Are small fixes like spelling corrections in comments/docs welcome, or are they generally avoided unless bundled with functional changes? 2. Is it acceptable to touch `3rdparty` code for comment-only fixes, or should that be left untouched? 3. For existing `TODO`s, is there a preferred process (issue first vs direct PR) if I plan to address them? 4. Any guidance on what maintainers currently consider “useful starter contributions”? I’m mainly aiming to learn the OpenCV contribution and review process properly before tackling larger changes. Thanks for your time, and apologies if this has been covered elsewhere.