Improve Readme Formatting and Structure

[Dippp10-ally]

Problem Statement

The current README contains important project information, but its formatting and organization can be improved to enhance readability and navigation. Inconsistent heading hierarchy, spacing, and Markdown formatting make it more difficult for new users and contributors to quickly understand the project and get started.

---

Proposed Solution

Improve the README by reorganizing its content using Markdown best practices. Suggested enhancements include:

• Add a clear and clickable Table of Contents.
• Improve the heading hierarchy and section organization.
• Standardize Markdown formatting throughout the document.
• Enhance the project overview, installation, usage, and contribution sections.
• Improve code block formatting, lists, and tables.
• Fix formatting inconsistencies, grammar, and broken links.
• Add or update badges and other relevant documentation sections where appropriate.

These changes are documentation-only and will not affect the project's functionality.

---

Alternatives Considered

Minor formatting fixes could improve readability to some extent, but a comprehensive reorganization of the README would provide a much better user experience and make the documentation easier to maintain over time.

---

Screenshots / Mockups

Not applicable. This feature request focuses on documentation improvements only.

---

GSSoC Information

• Difficulty Level: Intermediate
• Estimated Time Required: 1–2 hours

---

Additional Context

A well-structured README improves project accessibility, simplifies onboarding for new contributors, and presents the project more professionally. Following standard open-source documentation practices will make the repository easier to navigate and encourage community contributions.

[Dippp10-ally]

@GxAditya ji , do assign above issue number 13 to me also.....do assign labels called as gssoc:approved , level:intermediate, type:docs , quality:exceptional to above issue number 13 also......