paint.net@5.1.12: Correct shortcut name casing

[o-l-a-v]

Closes #18655.

• Use conventional PR title: <manifest-name[@version]|chore>: <general summary of the pull request>
• I have read the Contributing Guide

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: 85140b1f-5b9f-4845-ad92-336afa9ba8a5

📥 Commits

Reviewing files that changed from the base of the PR and between 6481213 and 6546c66.

📒 Files selected for processing (1)

• bucket/paint.net.json

Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review.

---

📝 Walkthrough

Walkthrough

The Paint.NET manifest changes the PaintDotNet.exe shortcut label from paint.net to Paint.NET.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 6546c

This localized manifest change corrects the displayed shortcut name from “paint.net” to “Paint.NET” without introducing actionable correctness, deployment, or runtime risk. No merge-blocking risk remains beyond normal checks.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title uses the required conventional format and clearly describes the shortcut name casing correction for paint.net version 5.1.12.
Description check	✅ Passed	The description links issue #18655 and includes both required checklist confirmations. It provides sufficient context for this small manifest change.
Linked Issues check	✅ Passed	The manifest changes the shortcut label from "paint.net" to "Paint.NET", which directly satisfies the coding objective in issue #18655 and matches the official branding requirement.
Out of Scope Changes check	✅ Passed	The pull request contains one focused manifest change related to the linked issue. No unrelated changes are present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

---

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.}