Typo in the word "Exercise" on the website

[rid-28]

📚 Documentation Issue

📋 Documentation Type

• 🎨 UI/UX documentation

🔍 Current State

What documentation is missing or needs improvement?
There is a spelling mistake in the user-facing website text where the word "Exercises" is misspelled as "Excercises".
This typo is visible to end users and affects readability and the professional appearance of the interface.

Target Audience:

• 👨‍🎓 New contributors
• 👩‍💻 Developers
• 👨‍🏫 Educators
• 👩‍🎓 Students
• 🌍 End users

💡 Proposed Improvements

What should be documented?

• Step-by-step instructions
• Code examples
• Screenshots/diagrams
• Video tutorials
• Interactive examples
• Troubleshooting guide
• Best practices
• Performance tips

Content Structure:

1. Identify the misspelled word in the UI text
2. Correct the spelling to "Exercises"
3. Verify the change across the affected page(s)

🎯 Participation Information

• I'm participating in Social Summer of Code (SSOC) Season 4
• I'm willing to work on this documentation

🏆 SSOC Season 4 Details (Click to expand if participating in SSOC)

SSOC Information

Difficulty Level:

• 🟢 Beginner (20 points) - Basic documentation, README updates
• 🟡 Intermediate (30 points) - Comprehensive guides, tutorials
• 🔴 Advanced (40 points) - Technical documentation, API docs

Estimated Time: [e.g., 1-2 days, 3-5 days, 1 week]

Skills Required:

• Technical writing
• Markdown
• Algorithm knowledge
• React/JavaScript (for code docs)
• Design (for diagrams/screenshots)
• Video editing (for tutorials)

Documentation Plan:

• Research Phase: [Gathering information and requirements]
• Writing Phase: [Creating content and examples]
• Review Phase: [Proofreading and technical accuracy]
• Polish Phase: [Final formatting and publication]

Mentorship:

• I can provide guidance for this documentation
• I need mentorship for this documentation
• This can be completed independently

📚 Additional Context

Success Criteria:

• Clear and concise writing
• Proper formatting and structure
• Accurate technical information
• Helpful examples and screenshots
• Accessible to target audience

✅ Checklist

• I have identified the specific documentation gap
• I have considered the target audience
• I have outlined the proposed content structure

[github-actions]

Thank you for raising this issue!

We'll review it as soon as possible. We truly appreciate your contributions! ✨

Meanwhile make sure you've visited the README.md, CONTRIBUTING.md, and CODE_OF_CONDUCT.md before creating a PR for this. Also, please do NOT create a PR until this issue has been assigned to you. 😊

[Jainvaishali2107]

#636 Typo in the word "Exercise" on the website

I’d like to work on this issue and ensure the typo is fixed correctly and consistently across the project.

🔍 Implementation Approach

Identify the exact UI component(s), page(s), or content file(s) where the word “Excercises” is currently displayed.

Correct the spelling to “Exercises” in the relevant source files.

Perform a full project-wide search to confirm that the incorrect spelling is not present in any other UI text, documentation, or reusable components.

Run the application locally to visually verify that the corrected text is rendered properly and does not impact layout or styling.

If required, add/update a small screenshot in the PR to demonstrate the fix clearly.

🧪 Testing & Verification

Manual UI verification on the affected page(s).

Ensure no regression or unintended text changes are introduced.

Validate consistency of terminology across the UI.

📦 Deliverables

Clean and minimal code changes.

Clear commit message following project conventions.

Well-documented PR explaining the fix and verification steps.

🎯 Acceptance Criteria

The typo “Excercises” is fully replaced with “Exercises”.

The correction is visible to end users.

No other UI/UX or documentation content is affected.

I’m participating in Social Summer of Code (SSOC) Season 4 and would be happy to take ownership of this issue.
Please assign this issue to me if it’s still available — I’ll ensure a quick and high-quality fix. 🚀

[Adii0906]

Hey @rid-28, you can go ahead and start working on this.
Please make sure to include before and after UI screenshots while submitting your work.
@Jainvaishali2107, thanks for raising the issue. Since we’re following a first-come, first-served approach, this one has already been taken. Feel free to look for other available issues to work on.
Thanks, and happy contributing! 🚀

[eccentriccoder01]

Thanks for the clarification @Adii0906.
That said, this specific change on its own is extremely minor and doesn’t really add any meaningful improvement to the project.

If @rid-28 or @Jainvaishali2107 would like to pair this with a slightly broader refinement (such as UI text consistency, copy cleanup, or improving the associated section), feel free to propose it, that would make the contribution more justified and valuable for the repository.

Let me know your thoughts❕