Update README documentation

[aurthitaacharya-afk]

##Changes Issue no = #895
-Updated the contribution section wording and added a thank you note.
##Purpose
-This update helps users better understand the project

Update README with small improvements .

Summary by CodeRabbit

• Documentation
  • Updated contribution section greeting in README.
  • Added acknowledgment message thanking contributors.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The README.md was edited: the contribution heading changed from "Want to Contribute? 😄" to "Do you want to Contribute? 😄", and a final line "Thank you for contributing to PictoPy!" was appended.

Changes

Cohort / File(s)	Summary
Documentation Updates README.md	Revised contribution section heading; appended a closing thank-you line

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Issue #431 resolved : docs: Added CONTRIBUTING.md, updated README.md , and included Code of Conduct.md #450 — Edits the repository README contribution text (heading/content), closely related to these documentation wording changes.

Poem

🐰 A tweak to words, a gentle plea,
“Do you want to contribute?” — come see!
A thank-you tucked at PictoPy’s end,
Inviting helpers, new friend to friend,
Hoppity cheers for every mend! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Update README documentation' is generic and overly broad; it doesn't convey the specific improvements made (contribution wording change and thank you note addition).	Consider using a more specific title like 'Update README: clarify contribution section and add thank you note' to better reflect the actual changes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

⚠️ No issue was linked in the PR description.
Please make sure to link an issue (e.g., 'Fixes #issue_number')

[github-actions]

⚠️ No issue was linked in the PR description.
Please make sure to link an issue (e.g., 'Fixes #issue_number')

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4043751 and 78f4f4f.

📒 Files selected for processing (1)

• README.md

🔇 Additional comments (1)

README.md (1)

5-5: Heading rephrasing looks good.

The change from "Want to Contribute?" to "Do you want to Contribute?" makes the section slightly more formal and welcoming. The tone shift is appropriate for the context.

[github-actions]

⚠️ No issue was linked in the PR description.
Please make sure to link an issue (e.g., 'Fixes #issue_number')

[github-actions]

⚠️ No issue was linked in the PR description.
Please make sure to link an issue (e.g., 'Fixes #issue_number')

[github-actions]

⚠️ No issue was linked in the PR description.
Please make sure to link an issue (e.g., 'Fixes #issue_number')

[github-actions]

⚠️ No issue was linked in the PR description.
Please make sure to link an issue (e.g., 'Fixes #issue_number')