fix(doc): format

[Sunny6889]

What does this PR do?

Why are these changes required?

This PR has been tested by:

• Unit Tests
• Manual Testing

Follow up

Extra details

Summary by CodeRabbit

• Documentation
  • Updated feature request template with clearer instructions for contributors when specifying affected system components.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 72b88c50-0a5e-4d7e-8c73-ffc84cde2a9f

📥 Commits

Reviewing files that changed from the base of the PR and between 521149d and 4370e0a.

📒 Files selected for processing (1)

• .github/ISSUE_TEMPLATE/request-a-feature.md

---

📝 Walkthrough

Walkthrough

Updated the prompt text in the "Scope of Impact" section of the feature request issue template, replacing the original phrasing with clearer wording that guides users to select affected system components.

Changes

Cohort / File(s)	Summary
Issue Template .github/ISSUE_TEMPLATE/request-a-feature.md	Updated HTML comment prompt in "Scope of Impact" section from "What parts of the system will be affected?, choose among" to "Select the system components that will be affected by this feature:" for improved clarity.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• fix(doc): modify the template title #9 — Modifies the same feature request template file, updating front-matter title.

Poem

🐰 A prompt so clear, the rabbit did cheer,
"Select components!" now guide those sincere,
The template now speaks with gentler request,
Feature requests flowing—simply the best! ✨

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix_github_template

📝 Coding Plan

• Generate coding plan for human review comments

---

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